-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
picast_start exits without error after outputting forever processing file line #35
Comments
This is often a naming error. ln -s /usr/bin/nodejs /usr/bin/node |
Thanks dieguillo, |
Same issue here. |
I'm also experiencing the same issue: pi@raspberrypi: |
+1; Same Issue. Just installed last night. |
Had the same issue and running |
@JbIPS nope, that didn't fix the problem for me! |
@JbIPS Thanks mate, i'm just starting to digg more into this stuff and your command (npm i express) solved it for me, unforunatly i have no idea what i did :-D ;-) |
It install the 'express' library which is needed for picast to work. Don't know why it isn't install by default. Have fun 😀 |
Hello to all, Thanks |
After installing express by |
same : install of express module was required with raspbian jessie |
Raspberry Pi Zero V1.3 (the one with the camera), install took at least 6 hours (went to bed after that point so I don't know how much longer it took) but I assumed it worked however doing:
cd ~/PiCAST
sh picast_start.sh
it outputs the expected Starting PiCAST3...
waits a few seconds then outputs:
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: picast.js
then just quits with no error.
I tried adding --minUptime 10000 --spinSleepTime 10000 in the picast_start.sh file but it still says they're not set (with and without the --).
The text was updated successfully, but these errors were encountered: