emonTX Connectivity

Hi There,

I have an emonPi set up with 6 emonTXs, however only two of the TXs (node IDs 8 and 1) are showing up on Emoncms. The other emonTXs have node IDs of 2, 4, 6 and 7.

Any ideas?

Cheers

Gareth

glyn.hudson's picture

Re: emonTX Connectivity

Hi Gareth, 

Can you post up your emonhub.conf (view via Emonhub tab of local Emoncms)

You will need to add entries into emonhub.conf for all your node. The latest emonTx's are running firmware V2.3 and require a node decoder as follows (replace NODEID with the node ID of each node) 

[[NODEID]]
    nodename = emonTx_4
    firmware =V2_3_emonTxV3_4_DiscreteSampling
    hardware = emonTx_(NodeID_DIP_Switch1:OFF)
    [[[rx]]]
       names = power1, power2, power3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1 
       units =W,W,W,W,V,C,C,C,C,C,C,p

pb66's picture

Re: emonTX Connectivity

Assuming they are all within range, have you tried powering them up one at a time to confirm each is working individually? just in-case they are blocking each other.

If that is successful try powering them up at one second intervals rather than all together to stagger transmission and reduce blocking.

Paul

garethc's picture

Re: emonTX Connectivity

HI There,

This is what they look like. DO I need to change every reference to the firmware to 2.3?

Cheers

Gareth

[[7]]
    nodename = emonTx_7
    firmware =V1_6_emonTxV3_4_DiscreteSampling
    hardware = emonTx_(NodeID_DIP_Switch1:ON)
    [[[rx]]]
       names = power1, power2, power3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse #Firmware V1.6
       #names = power1, power2, power3, power4, Vrms, temp                                           #Firmware =<V1.4 (un-comment)
       datacode = h
       scales = 1.5,1.5,1.5,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1 #Firmware V1.6
       units =W,W,W,W,V,C,C,C,C,C,C,p                   #FirmwareV1.6
       #scales = 1,1,1,1,0.01,0.1                       #Firmware =<V1.4 (un-comment)
       #units =W,W,W,W,V,C                              #Firmware =<V1.4 (un-comment)
cne to the firmware to

 

[[7]]
    nodename = emonTx_7
    firmware =V1_6_emonTxV3_4_DiscreteSampling
    hardware = emonTx_(NodeID_DIP_Switch1:ON)
    [[[rx]]]
       names = power1, power2, power3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse #Firmware V1.6
       #names = power1, power2, power3, power4, Vrms, temp                                           #Firmware =<V1.4 (un-comment)
       datacode = h
       scales = 1.5,1.5,1.5,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1 #Firmware V1.6
       units =W,W,W,W,V,C,C,C,C,C,C,p                   #FirmwareV1.6
       #scales = 1,1,1,1,0.01,0.1                       #Firmware =<V1.4 (un-comment)
       #units =W,W,W,W,V,C                              #Firmware =<V1.4 (un-comment)
 

pb66's picture

Re: emonTX Connectivity

No, the references to the v2.3 firmware in the conf are purely aesthetical, what you type in "firmware =" appears in emoncms, in time it will be used for locating the firmware for updating/installing to nodes and to configure the other metadata.

What firmware IS running on the Tx's is important to establish what to expect in the payload as the "emon-pi" emonhub variant insists on full and accurate disclosure of every node.

The [nodes] section will need a minimum of 7 entries, one for each Tx plus the emonPi, I assume from your numbering you may also have at least another (8th) device as node 3 and the emonPi is still on it's default of node 5.

Every section in the emonhub.conf must have a unique index, in the [nodes] section it's node id. Your two nodes shown above are both [[7]] which will cause the whole config file to be unused, is that a typo?

Assuming all your Tx's are identical your emonhub.conf entries for nodes 2,4,6 & 7 should mirror 1 & 8 exactly with only the "unique" index ie [[nodeid]] different. 

If you have 6 identical emonTx's and 6 identical (except node id) entries in [nodes] and still some don't show up in emoncms, then you must try them one at a time, to establish if the issue is with specific nodes or an overall traffic issue.

The node id's you are using confirm you have changed the firmware on each, have you made other changes to the sketches?

Using " tail -f /var/log/emonhub/emonhub.log " will give you a huge insight into what is (or isn't) happening if " loglevel = DEBUG " is set in emonhub.conf.

Paul

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.