You should NOT be able to change Node ID. Node ID is for mesh networking and firmware 2.x. We do not want to use mesh networks and if Node ID is changeable you have the wrong firmware and need to be using firmware 1.x All these settings were confirmed and tested on all radios distributed in July, if no-one has changed any settings the settings on all the radios should be correct. The errors with file names being goofy is all almost always from the radios not being paired, ssh over serial turned on, or mavlink/rts/cts enabled.
Is it possible to change the "Node ID"? The settings to change Node ID are grayed out and set at 2 for both our ground station and payload. Could this be a possible error source? (RFDs communicate, SSH over serial disabled, payload signal in 3DRRadio is not a square wave, etc.) This thread is relating to our "GUI Connection Error" thread for RFD900 image transmission.
The baud rate should be at 38400 on both radios Your screenshot has it at 57600
Last Edit: Apr 22, 2017 9:24:35 GMT -7 by David MSGC
We get the blinking light occasionally. Power cycling does not help, and our RFD settings are different than the ones posted above (image below), but when we change them they just go back to their previous settings. We are also unable to do a signal strength test- nothing comes up on the graph and we only get a popup saying "Ensure you disconnect properly to eave the radio in a good state." Turning the payload off and back on helps.
We have deleted all previous photos from the RFD Ground Station folder, so we won't get duplicate names, but the program still isn't working- it still freezes up and the Anaconda terminal says "Waiting for Acknowledge."
The powerpoints say we are supposed to use putty for this payload to safely disconnect the pi camera so it won't corrupt the SD card, however, we are unable to do so when the program freezes. On the occasion that the photo program does work, we are able to use putty to safely disconnect.
I'm not sure why all these issues are popping up- do you think this is definitely an RFD problem, or might there be something wrong with the software or the laptop itself?
Last Edit: Apr 25, 2017 19:40:16 GMT -7 by deniseund
Post by David MSGC on Apr 27, 2017 20:53:09 GMT -7
Anaconda and the RFD program communicate over serial, putty and logging into the pi is done over wifi using ssh, they are independent of each other, one should not effect the other. In the screen shot provided in the last post there is not a radio connected or the settings have not been read from a radio. When reading the settings on a radio make sure any other program that access that serial port is closed, ie python RFD program. Then make sure the baud rate is set to 38400 and click "read settings", then the current settings should be displayed, once all settings have been set to what they are in the screen shot provided in the RFD_resources folder the click "write settings." Then just to verify the settings are what you think they are click on "read settings" to see what the settings are actually set to.
Post by undballooning on Jun 1, 2017 17:43:25 GMT -7
We checked the RFD settings and our ground station RFD did not have the correct settings, so we changed them. However, we are still getting an error- once we launch the RFD900_PC.py program, the raspberry pi connects with the ground station laptop, but when we try to request an image, the program freezes and we get stuck in an infinite "waiting for acknowledge" loop and are unable to unfreeze the program.