We're currently having trouble using the groundstation software to request an image from the still image payload. We've noticed that the RFDs seem to be connected, and we can successfully run a connection test to the still image payload, but when we request an image, the groundstation terminal says the there is an error receiving the image size. We think that this may be connected to our errors, as this is where our system first diverges from documentation.
For reference, we are using updated versions of all software and are using version 1.5 of RFD900ModemTools. Any help wouild be greatly appreciated!
Post by Trevor MSGC on Aug 2, 2017 10:17:53 GMT -7
The incorrect image size being received is a known issue. However, you should still be receiving a picture. The only thing that is known to consistently not work when the image size is incorrect is the progress bar. How far away are you testing?
We are testing indoors with a distance of about 6 feet from the antennae to the still image payload. Here is a collection of images of our errors along with a picture of our setup: imgur.com/gallery/8u2ci
We noticed that in the still image pi's image log directory, directories have been created with time stamps of previous still image tests (in june), yet none have been created when we have turned on the pi many times in the past week. Could there be a problem with the Real Time Clock piece, and could this be the source of issues?
If so, would this impact our ability to use the RFD as a GPS? I think we wouldn't mind losing the ability to receive still images
Post by Austin MnSGC on Aug 3, 2017 6:40:06 GMT -7
From your images, the system is timing out after enough attempts to receive a piece of the image. This won't directly effect your ability to do RFD tracking, but it may indicate something is wrong with your radios, in which case you won't be able to use RFD tracking. You should make sure that you can get information through the radios, and then try tracking with them.
From the picture you posted, it looks like you are getting the ENOSPC error on the Pi side. The only way to get rid of the error we have found so far is by power cycling the Pi. The error happens (sometimes) when you first turn on the pi and thus it will not enable the camera so you wont be able to get a picture even if you have a connection between the radios because there wont be a picture, however, it should not affect your ability to track with the GPS as long as you have communication between the radios.