27-02-2017, 10:07
(This post was last modified: 27-02-2017, 10:19 by Palmyweather.)
Well great news, I think the problem is solved. It was in fact the Arduino Nano chip itself which was causing this problem it would seem.
Last night I plugged the original Arduino Nano from the original 3.11 TX board, still with the older TX software running on it, into the new transmitter board 3.12. It went all night without a hitch. Today I have reprogrammed the original Arduino Nano with the new software and so far tonight (2 hours in) there are no high spike readings.
I wonder what could have caused the the Arduino Nano I initially used in the TX 3.12 board (one I was keeping as a spare part) to become unhappy and give this sort of issue? I would have hoped that one Arduno would perform similar to the next, especially when you buy them from the same supplier. Must make a note to not use my spare Nano in future for any weather projects.
Thank you for your help and suggestions,
PalmyWeather
Last night I plugged the original Arduino Nano from the original 3.11 TX board, still with the older TX software running on it, into the new transmitter board 3.12. It went all night without a hitch. Today I have reprogrammed the original Arduino Nano with the new software and so far tonight (2 hours in) there are no high spike readings.
I wonder what could have caused the the Arduino Nano I initially used in the TX 3.12 board (one I was keeping as a spare part) to become unhappy and give this sort of issue? I would have hoped that one Arduno would perform similar to the next, especially when you buy them from the same supplier. Must make a note to not use my spare Nano in future for any weather projects.
Thank you for your help and suggestions,
PalmyWeather