06-11-2015, 20:10
Hi, Palmyweather
We already have something that can be used for that purpose.
The TX_LED on the RX board!
This led blinks every time the RX unit sends a packet of data to the Wireless Display units, but as those packets are broadcasted as soon as they are received from the external TX unit, the info from this LED, can be used to monitor if you are receiving data.
In the absence of incoming data from an external TX unit, this LED blinks only once a minute, otherwise, when the RX unit is receiving data from a TX unit, this LED should blink almost every 5 seconds.
If you mount this LED in the front panel of the RX case, you have a good visual information about incomming data from the external TX unit. In the picture below, the red led is the TX_LED, and the blue one is the COM_LED.
This way I always know when I'm receiving data from outside, and when I have connections to Cumulus (COM_LED blinks).
![[Image: RX_GreyBox_05.jpg]](http://www.meteocercal.info/forum/images/01forum_img/RX_GreyBox_05.jpg)
We have very little memory available on a Nano, this leads me to take some options. This is one of them.
Of course you can change the code to meet your requirements, but do it very wisely, after compiling, you should always have at least 380 bytes of free memory for variables, or the system will become very unstable (stack corruption).
It may seem that a lot of global variables used could be made local (as recommended by general Arduino programming good practices), and with it freeing more variable memory space, but in this case, is a false solution.
If you gonna change something, also be in mind that execution time of each routine is important, execution should be keeped in the loop code, as many time as possible. Symptoms of not doing this, is poor reception, and lots of data packets lost.
Write to the LCD the less data as you can, and not very often, it is slow.
We already have something that can be used for that purpose.
The TX_LED on the RX board!
This led blinks every time the RX unit sends a packet of data to the Wireless Display units, but as those packets are broadcasted as soon as they are received from the external TX unit, the info from this LED, can be used to monitor if you are receiving data.
In the absence of incoming data from an external TX unit, this LED blinks only once a minute, otherwise, when the RX unit is receiving data from a TX unit, this LED should blink almost every 5 seconds.
If you mount this LED in the front panel of the RX case, you have a good visual information about incomming data from the external TX unit. In the picture below, the red led is the TX_LED, and the blue one is the COM_LED.
This way I always know when I'm receiving data from outside, and when I have connections to Cumulus (COM_LED blinks).
We have very little memory available on a Nano, this leads me to take some options. This is one of them.
Of course you can change the code to meet your requirements, but do it very wisely, after compiling, you should always have at least 380 bytes of free memory for variables, or the system will become very unstable (stack corruption).
It may seem that a lot of global variables used could be made local (as recommended by general Arduino programming good practices), and with it freeing more variable memory space, but in this case, is a false solution.
If you gonna change something, also be in mind that execution time of each routine is important, execution should be keeped in the loop code, as many time as possible. Symptoms of not doing this, is poor reception, and lots of data packets lost.
Write to the LCD the less data as you can, and not very often, it is slow.