emonSD-10Nov22 (Stable) and EmonTX V34

Hardware emonTx
1

Hi Everyone.

I recently used a emonSD-10Nov22 (Stable) image hoping to connect to a EmonTX v34.

I have set up a device in a local Emoncms illustrated below.

image
image1438×810 66.7 KB

I have loaded the emonTx_3Phase_PLL.ino into the EmonTX with the following configuration.
image

image
image698×192 10.3 KB

I have flashed RFM69PI radio module successfully with RFM69 JeeLib Classic firmware as illustrated below.

image
image1844×1056 140 KB

The following is my EmonHub configuration [interfacers]

    ### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
    [[EmonPi2]]
        Type = EmonHubOEMInterfacer
        [[[init_settings]]]
            com_port = /dev/ttyAMA0
            com_baud = 38400
        [[[runtimesettings]]]
            pubchannels = ToEmonCMS
            subchannels = ToRFM12
           frequency = 433
            group = 210
            baseid = 11                              # emonPi / emonBase nodeID
           #quiet = true                            # Report incomplete RF packets (no implemented on emonPi)
        calibration = 230V                      # (UK/EU: 230V, US: 110V)

The following is the [nodes[ section of the EmonHub configuration

[nodes]  
  [[11]]
        nodename = emonTx_three_phase
        firmware = three_phase
        hardware = emonTx V3.2/V3.4/Shield
    [[[rx]]]
        names = power1, power2, power3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulsecount
        datacodes = h, h, h, h, h, h, h, h, h, h, h, L
        scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
        units =W,W,W,W,V,C,C,C,C,C,C,p

The following is the log of EmonHub

image
image1920×1373 276 KB

Will someone kindly advice as to why I am not receiving packets from the EmonTX.

Thanks and Regards.

2

For future reference, when posting code or output, please put 3 ‘backticks’ (normally found at the top left of the keyboard) on a line of their own before the code, and 3 more backticks also on a line of their own after the code:

```
code
```

If it is something like php you can add a language identifier after the first 3 backticks: ```php or even ```text if you don’t want any language markup applied.

3

Thanks. Will do.

4

If you got your emonTx V3.4 3-phase sketch from Github, I think it’s likely you will have a LowPowerLabs version - which is not compatible with the “Classic” Jeelib receiver software, which I think you’ve loaded into the radio receiver of your emonPi2. If this is the case, you can either load my original 3-phase sketch into your emonTx V3.4, or you can restore the LPL software into your emonPi2. I don’t know what changes have been made to my sketch since it was put on Github. I’m afraid I can only support versions up to and including 2.0.1. (Jeelib ‘Classic’ or Jeelib ‘Native’ radio formats).

5

Thanks @Robert.Wall for your assistance.

I seem to be in the right direction because there now appears to be proper communication between the RFM69Pi and the EmonTX unit.

2024-01-07 18:31:10,471 DEBUG    EmonPi2    28 NEW FRAME : OK 11 5 0 5 0 4 0 0 0 79 45 184 11 184 11 184 11 184 11 184 11 184 11 0 0 0 0 (-62)
2024-01-07 18:31:10,474 DEBUG    EmonPi2    28 Timestamp : 1704652270.470965
2024-01-07 18:31:10,475 DEBUG    EmonPi2    28 From Node : 11
2024-01-07 18:31:10,476 DEBUG    EmonPi2    28    Values : [5, 5, 4, 0, 115.99000000000001, 30, 30, 30, 30, 30, 30, 0]
2024-01-07 18:31:10,477 DEBUG    EmonPi2    28      RSSI : -62
2024-01-07 18:31:10,478 DEBUG    EmonPi2    28 Sent to channel(start)' : T
2024-01-07 18:31:10,479 DEBUG    EmonPi2    28 Sent to channel(end)' : T
2024-01-07 18:31:10,480 DEBUG    EmonPi2    28 Sent to channel(start)' : o
2024-01-07 18:31:10,481 DEBUG    EmonPi2    28 Sent to channel(end)' : o
2024-01-07 18:31:10,482 DEBUG    EmonPi2    28 Sent to channel(start)' : E
2024-01-07 18:31:10,483 DEBUG    EmonPi2    28 Sent to channel(end)' : E
2024-01-07 18:31:10,484 DEBUG    EmonPi2    28 Sent to channel(start)' : m
2024-01-07 18:31:10,485 DEBUG    EmonPi2    28 Sent to channel(end)' : m
2024-01-07 18:31:10,486 DEBUG    EmonPi2    28 Sent to channel(start)' : o
2024-01-07 18:31:10,486 DEBUG    EmonPi2    28 Sent to channel(end)' : o
2024-01-07 18:31:10,487 DEBUG    EmonPi2    28 Sent to channel(start)' : n
2024-01-07 18:31:10,488 DEBUG    EmonPi2    28 Sent to channel(end)' : n
2024-01-07 18:31:10,489 DEBUG    EmonPi2    28 Sent to channel(start)' : C
2024-01-07 18:31:10,490 DEBUG    EmonPi2    28 Sent to channel(end)' : C
2024-01-07 18:31:10,491 DEBUG    EmonPi2    28 Sent to channel(start)' : M
2024-01-07 18:31:10,492 DEBUG    EmonPi2    28 Sent to channel(end)' : M
2024-01-07 18:31:10,493 DEBUG    EmonPi2    28 Sent to channel(start)' : S
2024-01-07 18:31:10,494 DEBUG    EmonPi2    28 Sent to channel(end)' : S
2024-01-07 18:31:20,439 DEBUG    EmonPi2    29 NEW FRAME : OK 11 2 0 5 0 3 0 0 0 66 45 184 11 184 11 184 11 184 11 184 11 184 11 0 0 0 0 (-65)
2024-01-07 18:31:20,441 DEBUG    EmonPi2    29 Timestamp : 1704652280.438797
2024-01-07 18:31:20,442 DEBUG    EmonPi2    29 From Node : 11
2024-01-07 18:31:20,443 DEBUG    EmonPi2    29    Values : [2, 5, 3, 0, 115.86, 30, 30, 30, 30, 30, 30, 0]
2024-01-07 18:31:20,444 DEBUG    EmonPi2    29      RSSI : -65
2024-01-07 18:31:20,445 DEBUG    EmonPi2    29 Sent to channel(start)' : T
2024-01-07 18:31:20,446 DEBUG    EmonPi2    29 Sent to channel(end)' : T
2024-01-07 18:31:20,447 DEBUG    EmonPi2    29 Sent to channel(start)' : o
2024-01-07 18:31:20,448 DEBUG    EmonPi2    29 Sent to channel(end)' : o
2024-01-07 18:31:20,449 DEBUG    EmonPi2    29 Sent to channel(start)' : E
2024-01-07 18:31:20,450 DEBUG    EmonPi2    29 Sent to channel(end)' : E
2024-01-07 18:31:20,451 DEBUG    EmonPi2    29 Sent to channel(start)' : m
2024-01-07 18:31:20,451 DEBUG    EmonPi2    29 Sent to channel(end)' : m
2024-01-07 18:31:20,452 DEBUG    EmonPi2    29 Sent to channel(start)' : o
2024-01-07 18:31:20,453 DEBUG    EmonPi2    29 Sent to channel(end)' : o
2024-01-07 18:31:20,454 DEBUG    EmonPi2    29 Sent to channel(start)' : n
2024-01-07 18:31:20,455 DEBUG    EmonPi2    29 Sent to channel(end)' : n
2024-01-07 18:31:20,456 DEBUG    EmonPi2    29 Sent to channel(start)' : C
2024-01-07 18:31:20,456 DEBUG    EmonPi2    29 Sent to channel(end)' : C
2024-01-07 18:31:20,457 DEBUG    EmonPi2    29 Sent to channel(start)' : M
2024-01-07 18:31:20,458 DEBUG    EmonPi2    29 Sent to channel(end)' : M
2024-01-07 18:31:20,459 DEBUG    EmonPi2    29 Sent to channel(start)' : S
2024-01-07 18:31:20,460 DEBUG    EmonPi2    29 Sent to channel(end)' : S

I have yet to figure out how to have these values parsed and posted to the local Emoncms.

Thanks once again.

6

The route is via emonhub.conf. If you have the snip of emonhub.conf which you posted above in your copy of emonhub.conf, then the values should be appearing on the Inputs page of emonCMS.

The actual data is
OK 11 2 0 5 0 3 0 0 0 66 45 184 11 184 11 184 11 184 11 184 11 184 11 0 0 0 0 (-65)
11 is the NodeID, (-65) is the received signal strength (good) and in between are bytes (in decimal) which are parsed according to this:
datacodes = h, h, h, h, h, h, h, h, h, h, h, L
h being 2 bytes signed integer and L an unsigned long.
(It is all in the emonHub documentation.) There are 26 bytes in your data, and it is expecting 26, that is clearly all happening as it should, so I don’t see a good reason why it is not working.

7

The presence of the following [nodes] settings in the configuration file results in unexpected outputs appearing in the logs.

[nodes]
[[11]]
    nodename = emonTx_3
    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

The following is the log output when the above is present. For some reason I get help as if a “?” was sent to the RF69Pi

2024-01-07 19:04:12,170 INFO     MainThread EmonHub v2.5.2
2024-01-07 19:04:12,171 INFO     MainThread Opening hub...
2024-01-07 19:04:12,171 INFO     MainThread Running as user: pi
2024-01-07 19:04:12,172 INFO     MainThread Logging level set to DEBUG
2024-01-07 19:04:12,173 INFO     MainThread Creating EmonHubOEMInterfacer 'EmonPi2'
2024-01-07 19:04:12,174 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2024-01-07 19:04:12,176 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2024-01-07 19:04:12,178 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2024-01-07 19:04:12,178 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2024-01-07 19:04:12,179 INFO     MainThread Setting MQTT node_format_enable: 0
2024-01-07 19:04:12,179 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2024-01-07 19:04:12,180 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/
2024-01-07 19:04:12,180 INFO     MainThread Setting MQTT node_JSON_enable: 0
2024-01-07 19:04:12,181 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
2024-01-07 19:04:12,183 DEBUG    MainThread Setting emoncmsorg interval: 30
2024-01-07 19:04:12,184 DEBUG    MainThread Setting emoncmsorg pubchannels: ['ToRFM12']
2024-01-07 19:04:12,184 DEBUG    MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2024-01-07 19:04:12,185 INFO     MainThread Setting emoncmsorg apikey: set
2024-01-07 19:04:12,185 INFO     MainThread Setting emoncmsorg url: http://192.168.68.111
2024-01-07 19:04:12,186 INFO     MainThread Setting emoncmsorg senddata: 1
2024-01-07 19:04:12,186 INFO     MainThread Setting emoncmsorg sendstatus: 0
2024-01-07 19:04:12,187 INFO     MainThread Setting emoncmsorg sendnames: 1
2024-01-07 19:04:12,187 INFO     MainThread Setting emoncmsorg compress: 0
2024-01-07 19:04:12,189 DEBUG    MainThread Automatic configuration of nodes enabled
2024-01-07 19:04:21,114 DEBUG    EmonPi2    ---------------------------------------------------------------------
2024-01-07 19:04:21,119 DEBUG    EmonPi2    Config format: old
2024-01-07 19:04:21,129 DEBUG    EmonPi2    CONFIG SET:group        cmd:210g            reply:[RF12demo.14] K i11 g210 @ 433 MHz q1
2024-01-07 19:04:21,131 DEBUG    EmonPi2    CONFIG SET:frequency    cmd:433b            reply:> 210g
2024-01-07 19:04:21,208 DEBUG    EmonPi2    CONFIG SET:baseid       cmd:11i             reply:K i11 g210 @ 433 MHz q1
2024-01-07 19:04:21,209 DEBUG    EmonPi2    ---------------------------------------------------------------------
2024-01-07 19:04:21,310 DEBUG    EmonPi2    > 433b
2024-01-07 19:04:21,411 DEBUG    EmonPi2    > 11i
2024-01-07 19:04:21,513 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1
2024-01-07 19:04:31,076 DEBUG    EmonPi2    5 NEW FRAME : OK 11 6 0 5 0 3 0 0 0 254 44 184 11 184 11 184 11 184 11 184 11 184 11 0 0 0 0 (-58)
2024-01-07 19:04:31,079 DEBUG    EmonPi2    5 Timestamp : 1704654271.076376
2024-01-07 19:04:31,080 DEBUG    EmonPi2    5 From Node : 11
2024-01-07 19:04:31,080 DEBUG    EmonPi2    5    Values : [6, 5, 3, 0, 115.18, 300, 300, 300, 300, 300, 300, 0]
2024-01-07 19:04:31,081 DEBUG    EmonPi2    5      RSSI : -58
2024-01-07 19:04:31,082 DEBUG    EmonPi2    5 Sent to channel(start)' : T
2024-01-07 19:04:31,083 DEBUG    EmonPi2    5 Sent to channel(end)' : T
2024-01-07 19:04:31,083 DEBUG    EmonPi2    5 Sent to channel(start)' : o
2024-01-07 19:04:31,084 DEBUG    EmonPi2    5 Sent to channel(end)' : o
2024-01-07 19:04:31,085 DEBUG    EmonPi2    5 Sent to channel(start)' : E
2024-01-07 19:04:31,085 DEBUG    EmonPi2    5 Sent to channel(end)' : E
2024-01-07 19:04:31,086 DEBUG    EmonPi2    5 Sent to channel(start)' : m
2024-01-07 19:04:31,087 DEBUG    EmonPi2    5 Sent to channel(end)' : m
2024-01-07 19:04:31,087 DEBUG    EmonPi2    5 Sent to channel(start)' : o
2024-01-07 19:04:31,088 DEBUG    EmonPi2    5 Sent to channel(end)' : o
2024-01-07 19:04:31,089 DEBUG    EmonPi2    5 Sent to channel(start)' : n
2024-01-07 19:04:31,089 DEBUG    EmonPi2    5 Sent to channel(end)' : n
2024-01-07 19:04:31,090 DEBUG    EmonPi2    5 Sent to channel(start)' : C
2024-01-07 19:04:31,091 DEBUG    EmonPi2    5 Sent to channel(end)' : C
2024-01-07 19:04:31,091 DEBUG    EmonPi2    5 Sent to channel(start)' : M
2024-01-07 19:04:31,092 DEBUG    EmonPi2    5 Sent to channel(end)' : M
2024-01-07 19:04:31,093 DEBUG    EmonPi2    5 Sent to channel(start)' : S
2024-01-07 19:04:31,093 DEBUG    EmonPi2    5 Sent to channel(end)' : S
2024-01-07 19:04:31,295 DEBUG    EmonPi2    5 sent TX packet: T11,6,0,5,0,3,0,0,0,115,0,44,1,44,1,44,1,44,1,44,1,44,1,0,0,
2024-01-07 19:04:31,297 DEBUG    EmonPi2    5 sent TX packet: T11,6,0,5,0,3,0,0,0,115,0,44,1,44,1,44,1,44,1,44,1,44,1,0,0,
2024-01-07 19:04:31,299 DEBUG    EmonPi2    5 sent TX packet: T11,6,0,5,0,3,0,0,0,115,0,44,1,44,1,44,1,44,1,44,1,44,1,0,0,
2024-01-07 19:04:31,301 DEBUG    EmonPi2    5 sent TX packet: T11,6,0,5,0,3,0,0,0,115,0,44,1,44,1,44,1,44,1,44,1,44,1,0,0,
2024-01-07 19:04:31,504 DEBUG    EmonPi2    Available commands:
2024-01-07 19:04:31,607 DEBUG    EmonPi2    <nn> i     - set node ID (standard node ids are 1..30)
2024-01-07 19:04:31,710 DEBUG    EmonPi2    <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
2024-01-07 19:04:31,815 DEBUG    EmonPi2    <nnnn> o   - change frequency offset within the band (default 1600)
2024-01-07 19:04:31,919 DEBUG    EmonPi2    96..3903 is the range supported by the RFM12B
2024-01-07 19:04:32,024 DEBUG    EmonPi2    <nnn> g    - set network group (RFM12 only allows 212, 0 = any)
2024-01-07 19:04:32,129 DEBUG    EmonPi2    <n> c      - set collect mode (advanced, normally 0)
2024-01-07 19:04:32,236 DEBUG    EmonPi2    t          - broadcast max-size test packet, request ack
2024-01-07 19:04:32,341 DEBUG    EmonPi2    ...,<nn> a - send data packet to node <nn>, request ack
2024-01-07 19:04:32,448 DEBUG    EmonPi2    ...,<nn> s - send data packet to node <nn>, no ack
2024-01-07 19:04:32,555 DEBUG    EmonPi2    <n> q      - set quiet mode (1 = don't report bad packets)
2024-01-07 19:04:32,664 DEBUG    EmonPi2    <n> x      - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2024-01-07 19:04:32,772 DEBUG    EmonPi2    <nnn> y    - enable signal strength trace mode, default:0 (disabled)
2024-01-07 19:04:32,879 DEBUG    EmonPi2    sample interval <nnn> secs/100 (0.01s-2.5s) eg 10y=0.1s
2024-01-07 19:04:32,987 DEBUG    EmonPi2    123 z      - total power down, needs a reset to start up again
2024-01-07 19:04:33,092 DEBUG    EmonPi2    Remote control commands:
2024-01-07 19:04:33,198 DEBUG    EmonPi2    <hchi>,<hclo>,<addr>,<cmd> f     - FS20 command (868 MHz)
2024-01-07 19:04:33,307 DEBUG    EmonPi2    <addr>,<dev>,<on> k              - KAKU command (433 MHz)
2024-01-07 19:04:33,412 DEBUG    EmonPi2    Current configuration:
2024-01-07 19:04:33,516 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1
2024-01-07 19:04:33,720 DEBUG    EmonPi2    Available commands:
2024-01-07 19:04:33,827 DEBUG    EmonPi2    <nn> i     - set node ID (standard node ids are 1..30)
2024-01-07 19:04:33,933 DEBUG    EmonPi2    <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
2024-01-07 19:04:34,040 DEBUG    EmonPi2    <nnnn> o   - change frequency offset within the band (default 1600)
2024-01-07 19:04:34,148 DEBUG    EmonPi2    96..3903 is the range supported by the RFM12B
2024-01-07 19:04:34,254 DEBUG    EmonPi2    <nnn> g    - set network group (RFM12 only allows 212, 0 = any)
2024-01-07 19:04:34,361 DEBUG    EmonPi2    <n> c      - set collect mode (advanced, normally 0)
2024-01-07 19:04:34,467 DEBUG    EmonPi2    t          - broadcast max-size test packet, request ack
2024-01-07 19:04:34,573 DEBUG    EmonPi2    ...,<nn> a - send data packet to node <nn>, request ack
2024-01-07 19:04:34,679 DEBUG    EmonPi2    ...,<nn> s - send data packet to node <nn>, no ack
2024-01-07 19:04:34,785 DEBUG    EmonPi2    <n> q      - set quiet mode (1 = don't report bad packets)
2024-01-07 19:04:34,893 DEBUG    EmonPi2    <n> x      - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2024-01-07 19:04:35,001 DEBUG    EmonPi2    <nnn> y    - enable signal strength trace mode, default:0 (disabled)
2024-01-07 19:04:35,108 DEBUG    EmonPi2    sample interval <nnn> secs/100 (0.01s-2.5s) eg 10y=0.1s
2024-01-07 19:04:35,214 DEBUG    EmonPi2    123 z      - total power down, needs a reset to start up again
2024-01-07 19:04:35,318 DEBUG    EmonPi2    Remote control commands:
2024-01-07 19:04:35,425 DEBUG    EmonPi2    <hchi>,<hclo>,<addr>,<cmd> f     - FS20 command (868 MHz)
2024-01-07 19:04:35,531 DEBUG    EmonPi2    <addr>,<dev>,<on> k              - KAKU command (433 MHz)
2024-01-07 19:04:35,634 DEBUG    EmonPi2    Current configuration:
2024-01-07 19:04:35,738 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1

And so far no new input values have appeared in Emoncms.

8

How is your emonTx connected to the emonPI? Do you have both the USB cable to program & configure it, and is the radio turned on? I think it is, but check. When you have programmed and configured the emonTx, you no longer need the serial connection to the USB port, the data should be sent only by radio.

If you use “Serial monitor” and send the ‘?’ command, you should see the command to turn the radio on - it should be ‘w1’. Send this, followed by ‘s’ for save and (separately) ‘x’ for exit.

You can then unplug the programmer and the USB cable.

I see you’ve opened a new topic, so to prevent confusion, I’m locking this.