EmonTH 2 not connecting

gmaui · 2017-07-24T14:21:31.378Z

Hi Simsala

You are right. After removing batteries on id 23 I continue to receive data .
Instead if I remove batt on id 24 data stops.

Do you have any idea when your fix will be released?
THX

Simsala · 2017-07-24T14:39:29.893Z

Do you have a USB-to-serial programmer? With that, you can simply set your own NodeID (enter the config menu with +++ or you can upload the fixed version: emonth2/src.ino at 40dc513436a3885b876366952029d367c6c5f2be · elias-rexometer/emonth2 · GitHub

Robert.Wall · 2017-07-24T14:43:09.203Z

If you have a programmer, you can edit the sketch and have it working immediately.

Move the line that initialises the radio:

rf12_initialize(nodeID, RF_freq, networkGroup); // Initialize RFM

down a few lines so that it is below the DIP switches. ( if ((DIP1 == ... etc )

gmaui · 2017-07-24T14:45:46.177Z

Yes, I have one. Great to know that nodeid can be changed on sw.Thanks a lot Simsala.
Could you tell me how to connect the usb-serial programmer to the 6 pins on the emonth board ?
Thanks again

gmaui · 2017-07-24T14:50:35.249Z

HI Robert
I definitively will do that if changing the nodeID on the config menu fails.
Thanks a lot

gmaui · 2017-07-24T14:55:48.362Z

I am wondering how my two emonth sensors worked so far.
The currently installed firmware should uses 23 as initialized value for nodeID. but I have 23 and 24 working.

Robert.Wall · 2017-07-24T14:58:44.401Z

gmaui:

if changing the nodeID on the config menu fails.

It will fail, because you will still have two items transmitting using the same Node ID, and that’s not allowed (each will add to the same data stream, making your data wrong). The config file tells emonHub how to interpret the data it gets, by looking at the NodeID that comes with the data, and comparing that with the list of configurations in the config file. It doesn’t allocate the Node ID to the data.

gmaui · 2017-07-24T15:06:32.532Z

not the emonhub config file but the config setting on eeprom of the emonth which are read in the firmware

Robert.Wall · 2017-07-24T15:57:57.925Z

Yes, that should work.

Robert.Wall · 2017-07-24T16:20:43.406Z

gmaui:

Could you tell me how to connect the usb-serial programmer to the 6 pins on the emonth board ?

You plug it in! The GND pin is labelled on both.

gmaui · 2017-07-24T18:33:55.678Z

Everything is fine now.

Summary :

first emonth I bought had nodeID 23 (as requested)
second emonth I bought has nodeID 24 (as requested)
third emonth did not get switch setting (it was correct set to 25) due to error in the firmware; it reported 23
I flashed latest firmware (with Simsala fix) and it got nodeID 25 as per switch setting
BTW, I had to modified my usb-serial programmer (not bought at OEM) to be used with emonth both for flashing and for serial monitoring

Simsala, Robert thanks for your time and support.
Best regards

lgheorghe · 2018-01-10T20:15:47.648Z

Hi,
I have a similar situation with a brand new emonth 2 sensor - my firs one. I am not receiving anything from the sensor in emonhub.
The emonth has been ordered with nodeid 23.
The batteries are ok - I measured the voltage for both and it’s around 3V.
When I insert the batteries, there is no green led turning on - I tried inserting the batteries without any lights on.
Emonhub config looks ok - it has an entry for nodeid 23.
Emonpi has been updated and restarted.
The sensor is placed at 2 meters from the emonpi.

Does anyone have some ideas on how to troubleshoot the issue?

Thank you,
Liviu

Robert.Wall · 2018-01-10T21:43:42.654Z

lgheorghe:

When I insert the batteries, there is no green led turning on - I tried inserting the batteries without any lights on.

The LED is turned on by the very first action in the sketch.
Do you have a programmer? If yes, you could connect that and check if there is any output. If there is, then say what you see. You should see (at 115200 Baud) something like

OpenEnergyMonitor.org
emonTH FW: V3.2

and then some more about the radio and the sensor(s) fitted/connected.

But I suspect your emonTH is faulty.

If you see nothing, or you do not have a programmer, email the shop and include a link to this thread.

lgheorghe · 2018-01-11T06:59:19.420Z

I have a programmer, but it’s not the one you from the shop so I cannot connect it directly to the board.
Can you tell me what pins should I connect and their positions on the board - I imagine at a minimum Tx/Rx and GND.
I tried to find them on the board schematics, but couldn’t find the labes.
Thank you,
Liviu

Robert.Wall · 2018-01-11T09:37:10.087Z

You must connect your RXD to RXI, your TXD to TXO, your RTS to DTR, and of course GND to GND.
GND is the end nearest the USB connector.

(The crossover Rx-Tx & Tx-Rx happens on the emonTH PCB, and DTR is the reset line that puts the processor into programming mode.)

lgheorghe · 2018-01-11T11:02:13.228Z

Is it mandatory to have the RTS connected to DTR in order to see the output on a terminal?
The reason I’m asking is that my programmer doesn’t have a RTS pin and I want to be sure that connecting Tx/Rx and GND is enough for the task.

pb66 · 2018-01-11T11:11:24.481Z

lgheorghe:

Is it mandatory to have the RTS connected to DTR in order to see the output on a terminal?

No, all you need connected to just read the serial output is the Rx and ground, to then write to the serial port you will also need Tx connected and in addition to that you will need to connect the reset line only if you are uploading new firmware.

Gwil · 2018-01-11T11:32:41.665Z

Hi Liviu, You have a faulty emonTH board; I’m very sorry about that. Could you please email the shop the shop or PM me with your order details and we will get a replacement sent out to you as soon as possible. Is it just the one emonTH that is faulty, or both?

lgheorghe · 2018-01-11T17:12:23.867Z

Connected the programmer, Tx/Rx/GND, power cycled the board and there is no output on a terminal @115200.
It seems the board is dead.
Thank you for your help in troubleshooting this issue.

glyn.hudson · 2018-01-11T17:51:10.532Z

Bad batch of emonTH's emonTH

As seen here: EmonTH 2 not connecting - #22 by pb66, we have had a bad batch of emonTH units. It is a power supply issue between the battery and the board - with a programmer the board works fine. Tell-tale sign is that all these boards happen be be green in colour. Will only affect people who have ordered in late December or this year. Please direct anyone affected to email the shop (support@openenergymonitor.zendesk.com) or PM me. Thanks! Update: not all green PCB emonTH’s are affected only a…