EmonHub RPi w. Jeelink USB doesn't receive RF from EmonTxV3CM Arduino Shield RFM69CW

gerombo · 9 January 2023 06:15

Hi,

I have an Arduino Uno with EmonTx shield and RFM69CW (whip antenna). Before embarking on more ambitious projects I want to verify my soldering job and I loaded the continuous monitoring V2.10 sketch. The sketch is running ok. Console output from EmonTx CM on Shield below.

My EmonHub v2.2.6 is running on a Raspberry Pi (EmonPI SD install) with a USB Jeelink/Jeelabs v3c 433Mhz (whip antenna) running RF12demo.12 firmware.
[RF12demo.12] E i5 g210 @ 433 MHz

The EmonHub log is not showing any RF messages being received. Also during startup it shows: “WARNING MainThread Device communication error - check settings” But it does recognize the Jeelink and the configuration. See full log below.

However when I systemctl stop emonhub and connect to the Jeelink I do see RF messages being received (mix of OK and garbled messages) Even though both antennas are <50cm apart.

 sudo picocom /dev/ttyUSB0 --baud 57600 --omap crcrlf
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 57600
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : crcrlf,
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

 ? 181 249 55 178 11 178 86 249 80 123 93 48 191 252 59 160 75 222 141 16 57 (-91) 
 ? 14 230 252 211 113 243 246 75 181 252 99 103 166 75 137 196 114 229 76 222 60 (-90) 
 ? 178 21 108 229 143 253 247 248 92 229 19 174 159 249 224 249 214 36 94 88 115 (-91) 
OK 15 252 85 85 85 246 79 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 101 32 101 32 101 32 85 85 85 85 (-32) 
OK 15 255 85 85 85 243 79 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 85 101 32 101 32 101 32 85 85 85 85 (-34) 
 ? 188 255 248 61 175 43 109 126 231 198 55 118 9 211 112 30 211 138 99 92 126 (-91)

Emonhub interfacer cfg:

[interfacers]
[[JeeLink]]
    Type = EmonHubJeeInterfacer
    [[[init_settings]]]
        com_port = /dev/ttyUSB0
         com_baud = 57600      
    [[[runtimesettings]]]
        group = 210
        baseid = 5
        frequency = 433
        quiet = false

Emonhub.log:

2023-01-09 05:45:08,710 DEBUG    MainThread Signal 15 received.
2023-01-09 05:45:08,746 INFO     MainThread Exiting hub...
2023-01-09 05:45:08,771 INFO     MainThread Exit completed
2023-01-09 05:45:33,254 INFO     MainThread EmonHub emonHub (emon-pi variant) v2.2.6
2023-01-09 05:45:33,280 INFO     MainThread Opening hub...
2023-01-09 05:45:33,286 INFO     MainThread Logging level set to DEBUG
2023-01-09 05:45:33,297 INFO     MainThread Creating EmonHubJeeInterfacer 'JeeLink'
2023-01-09 05:45:33,314 DEBUG    MainThread Opening serial port: /dev/ttyUSB0 @ 57600 bits/s
2023-01-09 05:45:35,333 WARNING  MainThread Device communication error - check settings
2023-01-09 05:45:35,342 INFO     MainThread Setting JeeLink baseid: 5 (5i)
2023-01-09 05:45:36,358 INFO     MainThread Setting JeeLink frequency: 433 (4b)
2023-01-09 05:45:37,368 INFO     MainThread Setting JeeLink group: 210 (210g)
2023-01-09 05:45:38,378 INFO     MainThread Setting JeeLink quiet: 0 (0q)
2023-01-09 05:45:39,395 INFO     MainThread Setting JeeLink calibration: 230V (1p)
2023-01-09 05:45:40,411 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2023-01-09 05:45:40,437 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2023-01-09 05:45:40,456 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2023-01-09 05:45:40,461 INFO     MainThread Setting MQTT node_format_enable: 1
2023-01-09 05:45:40,466 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2023-01-09 05:45:40,476 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/

EmonTx Shield console output:

emonTx V3.4 EmonLibCM Continuous Monitoring V2.10
OpenEnergyMonitor.org
No EEPROM config
Settings:
Group 210, Node 15, Band 433 MHz

Calibration:
vCal = 268.97
assumedV = 240.00
i1Cal = 90.90
i1Lead = 4.20
i2Cal = 90.90
i2Lead = 4.20
i3Cal = 90.90
i3Lead = 4.20
i4Cal = 16.67
i4Lead = 6.00
datalog = 9.96
pulses = 1
pulse period = 100
temp_enable = 1
RF whitened
RFM69CW only Node: 15 Freq: 433MHz Group: 210
 
USA Vcal active: 130.00
POST.....wait 10s
'+++' then [Enter] for config mode
CT1 detected, i1Cal:90.90
CT2 detected, i2Cal:90.90
Temperature Sensors found = 0 of 3
Temperature measurement is enabled.

AC present 

MSG:1,Vrms:68.40,P1:0,P2:0,E1:0,E2:0,pulse:0
,I1:0.44,I2:0.44,I3:0.00,I4:0.00,pf1:0.0021,pf2:-0.0044,pf3:0.0000,pf4:0.0000
MSG:2,Vrms:68.45,P1:0,P2:0,E1:0,E2:0,pulse:0
,I1:0.29,I2:0.30,I3:0.00,I4:0.00,pf1:0.0124,pf2:0.0027,pf3:0.0000,pf4:0.0000
MSG:3,Vrms:68.45,P1:0,P2:0,E1:0,E2:0,pulse:0
,I1:0.29,I2:0.29,I3:0.00,I4:0.00,pf1:0.0013,pf2:-0.0063,pf3:0.0000,pf4:0.0000

Any troubleshooting tips that could point me in the right direction would be appreciated.

borpin · 9 January 2023 15:31

@TrystanLea - possibly one for you?

TrystanLea · 9 January 2023 17:46

Hello @gerombo, The RFM69CW baud rate should be 38400 I think?

 com_baud = 38400

gerombo · 9 January 2023 18:13

Thanks. I would be surprised if I’d be getting much human readable output in picocom at all if the baudrate was wrong, but I can give it a try.

TrystanLea · 9 January 2023 19:01

Ah I misunderstood the hardware that you have. Could you try:

Type = EmonHubOEMInterfacer

I note there’s an error:

MainThread Device communication error - check settings

the OEM interfacer may give some better clues as to what the issue is

gerombo · 10 January 2023 03:44

thanks @TrystanLea

TrystanLea:

Could you try:
Type = EmonHubOEMInterfacer
I note there’s an error:
MainThread Device communication error - check settings
the OEM interfacer may give some better clues as to what the issue is

after changing the interfacer type in emonhub.conf the output became less verbose. No error but also no other details about JeeLink device and no RF messages either:

2023-01-10 03:14:23,722 INFO     MainThread EmonHub emonHub (emon-pi variant) v2.2.6
2023-01-10 03:14:23,738 INFO     MainThread Opening hub...
2023-01-10 03:14:23,743 INFO     MainThread Logging level set to DEBUG
2023-01-10 03:14:23,755 INFO     MainThread Creating EmonHubOEMInterfacer 'JeeLink'
2023-01-10 03:14:23,775 DEBUG    MainThread Opening serial port: /dev/ttyUSB0 @ 57600 bits/s
2023-01-10 03:14:23,795 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2023-01-10 03:14:23,825 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2023-01-10 03:14:23,830 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2023-01-10 03:14:23,845 INFO     MainThread Setting MQTT node_format_enable: 1
2023-01-10 03:14:23,849 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2023-01-10 03:14:23,859 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/

Btw the “Device communication error” only shows up when I stop and start emonhub service. It doesn’t show up when I do a Raspberry Pi reboot (with EmonHubJeeInterfacer type).

2023-01-10 03:07:05,542 INFO     MainThread EmonHub emonHub (emon-pi variant) v2.2.6
2023-01-10 03:07:05,560 INFO     MainThread Opening hub...
2023-01-10 03:07:05,564 INFO     MainThread Logging level set to DEBUG
2023-01-10 03:07:05,589 INFO     MainThread Creating EmonHubJeeInterfacer 'JeeLink'
2023-01-10 03:07:05,620 DEBUG    MainThread Opening serial port: /dev/ttyUSB0 @ 57600 bits/s
2023-01-10 03:07:07,670 INFO     MainThread JeeLink device firmware version: [RF12demo.12]
2023-01-10 03:07:07,695 INFO     MainThread JeeLink device current settings:  E i5 g210 @ 433 MHz
2023-01-10 03:07:07,716 INFO     MainThread Setting JeeLink quiet: 0 (0q)
2023-01-10 03:07:08,736 INFO     MainThread Setting JeeLink calibration: 230V (1p)
2023-01-10 03:07:09,750 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2023-01-10 03:07:09,787 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2023-01-10 03:07:09,796 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2023-01-10 03:07:09,799 INFO     MainThread Setting MQTT node_format_enable: 1
2023-01-10 03:07:09,802 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2023-01-10 03:07:09,835 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/
2023-01-10 03:08:59,799 INFO     MainThread Setting JeeLink quiet: 0 (0q)
2023-01-10 03:09:00,816 INFO     MainThread Setting JeeLink calibration: 230V (1p)

gerombo · 30 January 2023 12:57

I didn’t find the root cause of this.
The RF of the arduino shield works fine with a RPi emonhub with RFM69.