Fairly basic question here, but we are having trouble being able to log into our still image payload via PuTTy and giving it the sudo shutdown command.
Everything else about the still image system seems to be working OK. In addition, the shutdown works just fine on our video payload, and the instructions on the operator's manual are identical for both, so that's where we are confused.
To get into the video payload we hit "load" in PuTTy on "Ubiquiti" under saved sessions. To log into the still image payload, is it the same process, but loading the "pi" saved session? When we try to do this, we get a fatal error from PuTTY saying Network error: Connection refused as the black command prompt window is opening up.
How can we troubleshoot this? Is this a problem with having to change the IP address in between logging into each payload?
Post by David MSGC on Jan 31, 2017 12:10:39 GMT -7
You need to be connected to the WiFi adhoc network being hosted by the Pi and this needs to be done per the instructions in the RFD documentation about connecting the the adhoc network. The ground station pc needs to be on a static IP address on the wifi adapter and then connect to the network using the command line commands to connect, not clicking on the wifi name in the task bar menu, it won't connect through the network settings, it has to be done with the command line. After you are connected to the adhoc network you can then use putty to ssh in to the pi.
David or somebody Help! We are trying to "properly" shutdown the still image and we are using the adhoc network instructions, but we are not able to accomplish this. When we get to typing "netsch wlan set profileparameter <014j> connectiontype=ibss connectionmode=manual" we get something to the effect of can't find file.
Is there an easier/straight forward way to shut still image off? Will it corrupt the memory or the camera if we just use the key to turn it off every time?
Post by David MSGC on Apr 20, 2017 17:19:49 GMT -7
The "netsh wlan set profileparameter...." only needs to be done once per laptop (if using windows 8 or newer, see notes on page 14 of the adhoc setup pdf.), once this initial setup is done you do not need to do it again. If you are using the laptop form the workshop all of this was done before the workshop and you should start at the point(page 17 of adhoc pdf) where you are setting the static IP for wifi adapter and connecting to the ad-hoc with "netsh wlan connect <networkName>"
Yes, if you use the key to shut it off you risk corrupting the SD card. You don't have to use the laptop provided, you can use another computer or tablet, preferably with windows 7. With windows 7 you don't have to do the initial setup, you can connect to the pi form windows 7 just like any other wifi network. You might be able to connect from an iPhone but I'm not sure if iPhone will connect to ad-hoc, android will not connect to ad-hoc. You can also use USB tethering to an android phone, but this requires changing the network settings, if you want to do it this way I can get the instructions for you.
Last Edit: Apr 20, 2017 17:31:52 GMT -7 by David MSGC
Great, thank you so much David. It makes sense, it was telling us that the particular ad-hoc already exists. We will try again next week. And just in case, and only if you have them handy please send the instructions for using the USB tethered to android phone. Thank you again, Paulo