Upon a physical camera disconnect while video is still streaming, a crash is to be expected on all platforms. However, on Android and only with these TX-25 glasses, even quitting the app after properly closing the camera connection in software and then restarting the app makes that the camera is no longer recognized. I'm not sure if with the Raspberry Pi prototype I can stop and restart the raspivoice app without also turning off power. Since UVC cameras on Android tap into the Linux layer underneath, and Raspberry Pi is Linux-based, I would expect the same problem to crop up with the TX-25 and Raspberry Pi. However, this is not particularly relevant if a camera release only occurs when turning off the device (and the user does not unplug the camera's USB cable while raspivoice is still processing video). With The vOICe for Android one does not normally turn off the smartphone's power upon quitting the app, because a smartphone is meant to be an always-on device.mikey11 wrote:I believe the current behaviour on camera disconnect is a crash of raspivoice.
Thanks mikey11, I had never worked with a Raspberry Pi device before and naively assumed I would be accessing the device's file system via a USB cable like one accesses a smartphone. Anyway, I just managed to use PuTTY and pscp to connect to the device (having it wired to my router via an ethernet cable) and copy the rangefinder2.py and rc.local files back and forth to my PC for easy editing (I'd probably mess up the files if trying to use vi to edit). The vibration=-1 works fine now, and I'll be looking at the effects of sudo ./raspivoice -A --speak -s2 --verbose --read_frames=7 &mikey11 wrote:Peter: If you want to see the change with this, it would be a matter of editing the /etc/rc.local file on your device and adding this to the raspivoice execution line prior to the & symbol at the end of the line.
To disable the vibration on startup, you would have to edit the file /home/pi/rangefinder2.py
there is a line that says vibration=1, this should be changed to vibration=-1
Thanks for the info! I installed Xming and applied further instructions from http://www.codesynthesis.co.uk/tutorial ... sing-xming to see the Raspberry Pi desktop. I throught I could just use the line sudo ./raspivoice -A --speak -s2 --verbose --preview & in rc.local, but that does not seem to work. Has --preview processing not been implemented yet?mikey11 wrote:If you install xming on your pc, and do x11 forwarding with putty, you can get the video output of th pi on your pc. I plan on using this feature to demonstrate the device using the --preview command of raspivoice.
The Raspberry Pi desktop shows up fine, but the --preview option, when leaving out --speak, currently still gives memikey11 wrote:Then restart raspivoice with the flags of your choosing, but not the sound menu at the same time as preview.
TBH I am slightly surprised that the Foundation haven't commissioned a Windows Pi Image installer program of their own. I know they have put a lot of effort into NOOBS, and that is great and all, and most people who want to use images will have the resources to do it (like me), but I'm sure it can't be too hard to put together an official app that will: fetch an image file if needed; unzip the image (or advise that unzip software is required); write image to card (ignoring current formatting), while doing certain checks and giving appropriate warnings.mikey11 wrote:Beware:Sourceforge recently started adding spyware/crapware to items they host WITHOUT the authors consent. Some notable projects that left SF as a result are notepad++ (a darling program for coding), VLC, and the GIMP 2.
I couldn't find another host though, so...
Maybe. I got tired of each time walking to my router to which the Pi was connected via an ethernet cable, so I used that same cable to connect the Pi directly to my PC. That gave me the "Network error: Connection refused" no matter what PuTTY, local DHCP server and ethernet adapter settings I tried to get the communication going, so I finally gave up and moved the Pi back to the router and stopped the PC's DHCP server, but the "Connection refused" problem did not disappear. From what I read, the Pi is supposed to automatically deal with not using a crossover cable http://stackoverflow.com/questions/1604 ... out-router but I'm wondering now if some automatic configuration change got "stuck" in the Pi after making the direct PC connection.mikey11 wrote:If flashing the new image on the card does not work, you may have a hardware problem of some kind.