EmonTX v3.4 rebooting on rfm init

Hardware
1

Somewhat randomly a few weeks ago my EmonTX 3.4 decided to stop working after a number of years of working, and is now in a reboot cycle when initialising the radio module, have flashed to EmonTX3CM v2.3 in the hope that this would solve (e.g. software problem) with no success

0:59:57.934 -> emonTx V3.4 EmonLibCM Continuous Monitoring V2.30
20:59:57.934 -> OpenEnergyMonitor.org
20:59:57.934 -> Loaded EEPROM config
20:59:57.934 -> Settings:
20:59:57.934 -> Group 210, Node 15, Band 433 MHz
20:59:57.934 -> 
20:59:57.934 -> Calibration:
20:59:57.934 -> vCal = 268.97
20:59:57.934 -> assumedV = 240.00
20:59:57.934 -> i1Cal = 90.90
20:59:57.934 -> i1Lead = 4.20
20:59:57.934 -> i2Cal = 90.90
20:59:57.934 -> i2Lead = 4.20
20:59:57.934 -> i3Cal = 90.90
20:59:57.934 -> i3Lead = 4.20
20:59:57.934 -> i4Cal = 16.67
20:59:57.934 -> i4Lead = 6.00
20:59:57.934 -> datalog = 9.96
20:59:57.934 -> pulses = 1
20:59:57.934 -> pulse period = 100
20:59:57.934 -> temp_enable = 1
20:59:57.970 -> RF on
20:59:57.970 -> RFM69CW only Node: 15 Freq: 433MHz Group: 210
20:59:57.970 ->  
20:59:57.970 -> POST.....wait 10s
20:59:57.970 -> '+++' then [Enter] for config mode
21:00:16.711 -> emonTx V3.4 EmonLibCM Continuous Monitoring V2.30
21:00:16.711 -> OpenEnergyMonitor.org
21:00:16.711 -> Loaded EEPROM config
21:00:16.711 -> Settings:
21:00:16.711 -> Group 210, Node 15, Band 433 MHz
21:00:16.711 -> 
21:00:16.711 -> Calibration:
21:00:16.711 -> vCal = 268.97
21:00:16.711 -> assumedV = 240.00
21:00:16.711 -> i1Cal = 90.90
21:00:16.711 -> i1Lead = 4.20
21:00:16.711 -> i2Cal = 90.90
21:00:16.711 -> i2Lead = 4.20
21:00:16.711 -> i3Cal = 90.90
21:00:16.711 -> i3Lead = 4.20
21:00:16.711 -> i4Cal = 16.67
21:00:16.711 -> i4Lead = 6.00
21:00:16.711 -> datalog = 9.96
21:00:16.744 -> pulses = 1
21:00:16.744 -> pulse period = 100
21:00:16.744 -> temp_enable = 1
21:00:16.744 -> RF on
21:00:16.744 -> RFM69CW only Node: 15 Freq: 433MHz Group: 210
21:00:16.744 ->  
21:00:16.744 -> POST.....wait 10s
21:00:16.744 -> '+++' then [Enter] for config mode

Disabling the radio using x0, allows the TX to start logging data correctly, so I’m thinking that it’s an issue with the radio. So question to you kind and knowledgeable folks, is this a blown/failed radio module (potential dry-joint etc) - or potentially solvable in software?

Thanks,
Mike

2

I’m no expert and would defer to Mr Wall.

It smells like the radio board, but equally could be some sort of power supply issue … when the radio powers up it takes some power causing the reboot. Not sure if this is the wall wart you use or something internal failed. Try another PSU first, then I’d open it up and put a scope (or fast acting meter) on the supply pins to the atmel 328p chip to see if you can see any glitches.

Hope that helps

Oh yes, and welcome to OEM forums.

3

I’d go along with all of those, sadly. As it has worked, and then failed, and continually rebooting at startup is a reasonable sign of the RFM module not responding (so the watchdog fires and resets everything, and it has another try), then I’d be looking at the RFM first. Why it’s not responding could be a dry joint, or the RFM module itself has died. If you can’t see a suspect joint, I think send an email to The Shop [email protected] and see if they are willing to look at repairing it. Replacing the radio module isn’t likely to be successful unless you have the proper tools.

I won’t discount a power supply problem, but as it’s at start-up and not when transmitting - which is when it does draw lots of current, I’d push this down the list. But it’s worth looking at first because it’s quite easy to check.