81

What I was suggesting is the default setting of the clock frequency, suitable for a Pi3, is not suitable for your Pi B+. You can fix that by changing the file and restarting your Pi.
Equally, if by default you uploaded the RFM69CW code to the RFM12Pi, uploading the correct code will correct that too.

What I don’t know the cause of, hence the solution, is why avrdude couldn’t connect to the Atmel processor on the RFM12Pi board. I’m assuming you have it in the right place in the Pi - right into the corner, as it used to work.
One thing I don’t think anyone has mentioned, but a script might do it for you, you need to stop emonHub while you’re trying to talk to the RFM12Pi. E.g:

#!/bin/bash
sudo service emonhub stop
avrdude -v -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 38400 -U flash:w:firmware/RFM69CW_RF_Demo_ATmega328/RFM12_Demo_ATmega328.cpp.hex
sudo service emonhub start

I see you posted while I was typing. I’m not an expert on the Pi, I have no idea why that file should be empty.

82

I took the lines you mentioned for the config and added them but it doesn’t seem to make a difference, although I am also no pi expert.

I have tried to stop the service and flash but same result, I also tried the script

avrdude-original: stk500_recv(): programmer is not responding
avrdude-original: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
avrdude-original: stk500_recv(): programmer is not responding
avrdude-original: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00

miniterm at differing speeds gives some output at 38400 almost like an incorrect speed, 9600 is blank

pi@emonpi:~ $ miniterm --rtscts /dev/ttyAMA0 38400
— Miniterm on /dev/ttyAMA0 38400,8,N,1 —
— Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H —
� � � � � � �
— exit —
pi@emonpi:~ $ miniterm --rtscts /dev/ttyAMA0 9600
— Miniterm on /dev/ttyAMA0 9600,8,N,1 —
— Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H —

83

pi@emonpi:~ $ vcgencmd get_config int | grep arm_freq
arm_freq=1200
arm_freq_min=600
pi@emonpi:~ $

84

Unfortunately, “programmer is not responding” is all you get - it could be due to many different faults. It may well be that your RFM12Pi has failed - and if so, it’s worth asking the shop if they can do you an 868 MHz one, or failing that, one without the RFM69CW, so that you can get an 868 MHz RFM69CW and solder it on yourself. In the absence of being able to talk to the Atmel '328P, I can’t think of another way. What you don’t want is to change everything else to 433 MHz.

85

Well thank you all for trying to get me back online, I will approach the shop, if not then I do have a brand new unused emontx in 433 so could always rebuild the emonglcd and temperature sensors if I had to.

86

Good news is the shop had 868Mhz pi boards in stock so that has just arrived.
bad news is its exactly the same.

as such I have swapped the pi, exactly the same.

stopping emonhub, checking with miniterm, exactly the same.

my only option is to blow away the sd and see what happens.
watch this space

87

So I started a fresh image and everything works
Did a full update, everything works
imported the backup I took and its all broken again.
next I will try the old hardware in a fresh image, as I suspect its still working.
Sadly 7 years of data down the toilet

88

You didn’t keep the old SD card and write a new one? :frowning_face:

89

Yes I kept the old one :slight_smile:

90

OK, there’s no need to despair. You should be able to backup the old data and restore it to the new card. I don’t know the details of how, I’m fairly sure @borpin does.

91

Next challenge !

The only device show up in inputs is my emonglcd, the emontx3 is not, although the glcd is receiving and showing data ok.

the log shows

2020-07-23 17:32:54,072 INFO     MainThread Opening hub...
2020-07-23 17:32:54,073 INFO     MainThread Logging level set to DEBUG
2020-07-23 17:32:54,073 INFO     MainThread Creating EmonHubJeeInterfacer 'RFM2Pi' 
2020-07-23 17:32:54,075 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2020-07-23 17:32:56,081 INFO     MainThread RFM2Pi device firmware version: [RF12demo.14]
2020-07-23 17:32:56,082 INFO     MainThread RFM2Pi device current settings:  E i5 g212 @ 868 MHz q1
2020-07-23 17:32:56,083 INFO     MainThread Setting RFM2Pi calibration: 230V (1p)
2020-07-23 17:32:57,085 DEBUG    MainThread Setting RFM2Pi interval: 300
2020-07-23 17:32:57,086 DEBUG    MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2020-07-23 17:32:57,087 DEBUG    MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2020-07-23 17:32:57,089 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT' 
2020-07-23 17:32:57,091 DEBUG    RFM2Pi     acknowledged command: > 1p
2020-07-23 17:32:57,093 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2020-07-23 17:32:57,094 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2020-07-23 17:32:57,095 INFO     MainThread Setting MQTT node_format_enable: 1
2020-07-23 17:32:57,095 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2020-07-23 17:32:57,096 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/
2020-07-23 17:32:57,097 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg' 
2020-07-23 17:32:57,099 DEBUG    MainThread Setting emoncmsorg pubchannels: ['ToRFM12']
2020-07-23 17:32:57,099 DEBUG    MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2020-07-23 17:32:57,100 WARNING  MainThread Setting emoncmsorg apikey: obscured
2020-07-23 17:32:57,100 INFO     MainThread Setting emoncmsorg url: https://emoncms.org
2020-07-23 17:32:57,101 INFO     MainThread Setting emoncmsorg senddata: 1
2020-07-23 17:32:57,102 INFO     MainThread Setting emoncmsorg sendstatus: 1
2020-07-23 17:32:57,193 DEBUG    RFM2Pi     RFM2Pi broadcasting time: 17:32
2020-07-23 17:32:57,402 DEBUG    RFM2Pi     acknowledged command: <nn> i     - set node ID (standard node ids are 1..30)
2020-07-23 17:32:57,508 DEBUG    RFM2Pi     acknowledged command: <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
2020-07-23 17:32:57,614 DEBUG    RFM2Pi     acknowledged command: <nnnn> o   - change frequency offset within the band (default 1600)
2020-07-23 17:32:57,826 DEBUG    RFM2Pi     acknowledged command: <nnn> g    - set network group (RFM12 only allows 212, 0 = any)
2020-07-23 17:32:57,932 DEBUG    RFM2Pi     acknowledged command: <n> c      - set collect mode (advanced, normally 0)
2020-07-23 17:32:58,155 DEBUG    RFM2Pi     acknowledged command: ...,<nn> a - send data packet to node <nn>, request ack
2020-07-23 17:32:58,265 DEBUG    RFM2Pi     acknowledged command: ...,<nn> s - send data packet to node <nn>, no ack
2020-07-23 17:32:58,371 DEBUG    RFM2Pi     acknowledged command: <n> q      - set quiet mode (1 = don't report bad packets)
2020-07-23 17:32:58,478 DEBUG    RFM2Pi     acknowledged command: <n> x      - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2020-07-23 17:32:58,585 DEBUG    RFM2Pi     acknowledged command: <nnn> y    - enable signal strength trace mode, default:0 (disabled)
2020-07-23 17:32:58,692 DEBUG    RFM2Pi     acknowledged command: sample interval <nnn> secs/100 (0.01s-2.5s) eg 10y=0.1s
2020-07-23 17:32:59,015 DEBUG    RFM2Pi     acknowledged command: <hchi>,<hclo>,<addr>,<cmd> f     - FS20 command (868 MHz)
2020-07-23 17:32:59,121 DEBUG    RFM2Pi     acknowledged command: <addr>,<dev>,<on> k              - KAKU command (433 MHz)
2020-07-23 17:32:59,327 DEBUG    RFM2Pi     device settings updated: E i5 g212 @ 868 MHz q1
2020-07-23 17:32:59,430 DEBUG    RFM2Pi     acknowledged command: > 0,17,32,0,0s
2020-07-23 17:32:59,532 DEBUG    RFM2Pi     confirmed sent packet size: -> 4 b
2020-07-23 17:33:04,779 DEBUG    RFM2Pi     7 NEW FRAME : OK 9 155 254 243 0 0 0 90 1 103 92 82 3 (-78)
2020-07-23 17:33:04,780 WARNING  RFM2Pi     7 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:33:16,467 DEBUG    RFM2Pi     8 NEW FRAME : OK 9 159 254 237 0 0 0 106 1 176 92 82 3 (-78)
2020-07-23 17:33:16,469 WARNING  RFM2Pi     8 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:33:23,924 DEBUG    RFM2Pi     9 NEW FRAME : OK 20 178 9 (-80)
2020-07-23 17:33:23,926 DEBUG    RFM2Pi     9 Timestamp : 1595522003.9242392
2020-07-23 17:33:23,926 DEBUG    RFM2Pi     9 From Node : 20
2020-07-23 17:33:23,927 DEBUG    RFM2Pi     9    Values : [248.20000000000002]
2020-07-23 17:33:23,928 DEBUG    RFM2Pi     9      RSSI : -80
2020-07-23 17:33:23,928 DEBUG    RFM2Pi     9 Sent to channel(start)' : ToEmonCMS
2020-07-23 17:33:23,929 DEBUG    RFM2Pi     9 Sent to channel(end)' : ToEmonCMS
2020-07-23 17:33:24,227 INFO     MQTT       Connecting to MQTT Server
2020-07-23 17:33:24,327 DEBUG    emoncmsorg Buffer size: 1
2020-07-23 17:33:24,332 INFO     MQTT       connection status: Connection successful
2020-07-23 17:33:24,333 DEBUG    MQTT       CONACK => Return code: 0
2020-07-23 17:33:24,435 INFO     MQTT       on_subscribe
2020-07-23 17:33:28,277 DEBUG    RFM2Pi     10 NEW FRAME : OK 9 155 254 244 0 0 0 112 1 211 92 82 3 (-78)
2020-07-23 17:33:28,295 WARNING  RFM2Pi     10 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:33:39,984 DEBUG    RFM2Pi     11 NEW FRAME : OK 9 120 254 241 0 0 0 99 1 220 92 82 3 (-78)
2020-07-23 17:33:39,985 WARNING  RFM2Pi     11 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:33:51,673 DEBUG    RFM2Pi     12 NEW FRAME : OK 9 150 254 246 0 0 0 113 1 48 93 82 3 (-78)
2020-07-23 17:33:51,675 WARNING  RFM2Pi     12 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:33:53,901 DEBUG    RFM2Pi     13 NEW FRAME : OK 20 172 9 (-79)
2020-07-23 17:33:53,902 DEBUG    RFM2Pi     13 Timestamp : 1595522033.9008791
2020-07-23 17:33:53,903 DEBUG    RFM2Pi     13 From Node : 20
2020-07-23 17:33:53,903 DEBUG    RFM2Pi     13    Values : [247.60000000000002]
2020-07-23 17:33:53,904 DEBUG    RFM2Pi     13      RSSI : -79
2020-07-23 17:33:53,904 DEBUG    RFM2Pi     13 Sent to channel(start)' : ToEmonCMS
2020-07-23 17:33:53,905 DEBUG    RFM2Pi     13 Sent to channel(end)' : ToEmonCMS
2020-07-23 17:33:53,956 DEBUG    MQTT       Publishing: emon/emonth2/temperature 247.60000000000002
2020-07-23 17:33:53,958 DEBUG    MQTT       Publishing: emon/emonth2/rssi -79
2020-07-23 17:33:53,959 INFO     MQTT       Publishing: emonhub/rx/20/values 247.60000000000002,-79
2020-07-23 17:33:54,358 DEBUG    emoncmsorg Buffer size: 1
2020-07-23 17:34:03,477 DEBUG    RFM2Pi     14 NEW FRAME : OK 9 113 254 247 0 0 0 122 1 34 93 82 3 (-79)
2020-07-23 17:34:03,478 WARNING  RFM2Pi     14 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:34:15,164 DEBUG    RFM2Pi     15 NEW FRAME : OK 9 106 254 3 1 0 0 127 1 11 93 82 3 (-78)
2020-07-23 17:34:15,165 WARNING  RFM2Pi     15 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']
2020-07-23 17:34:24,031 DEBUG    RFM2Pi     16 NEW FRAME : OK 20 172 9 (-79)
2020-07-23 17:34:24,033 DEBUG    RFM2Pi     16 Timestamp : 1595522064.0314724
2020-07-23 17:34:24,033 DEBUG    RFM2Pi     16 From Node : 20
2020-07-23 17:34:24,034 DEBUG    RFM2Pi     16    Values : [247.60000000000002]
2020-07-23 17:34:24,035 DEBUG    RFM2Pi     16      RSSI : -79
2020-07-23 17:34:24,035 DEBUG    RFM2Pi     16 Sent to channel(start)' : ToEmonCMS
2020-07-23 17:34:24,036 DEBUG    RFM2Pi     16 Sent to channel(end)' : ToEmonCMS
2020-07-23 17:34:24,081 DEBUG    MQTT       Publishing: emon/emonth2/temperature 247.60000000000002
2020-07-23 17:34:24,083 DEBUG    MQTT       Publishing: emon/emonth2/rssi -79
2020-07-23 17:34:24,084 INFO     MQTT       Publishing: emonhub/rx/20/values 247.60000000000002,-79
2020-07-23 17:34:24,378 DEBUG    emoncmsorg Buffer size: 1
2020-07-23 17:34:26,963 DEBUG    RFM2Pi     17 NEW FRAME : OK 9 110 254 7 1 0 0 111 1 240 92 82 3 (-78)
2020-07-23 17:34:26,964 WARNING  RFM2Pi     17 RX data length: 12 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']

Edit - formatted text. BT, Moderator

92

That is telling me that the entry in emonhub.conf for Node 9 doesn’t match the data that’s being sent. Is Node 9 the missing emonTx? If so, which sketch is it running? - OR Can you put the old SD card in your computer and look in the old emonhub.conf? (Get the right one - there are several, it’s likely to be the one with the latest date) and copy the entry for Node 9 from that?

93

Thank you Robert, I used this entry, which seems to work.

[[9]]
nodename = emontx2
[[[rx]]]
names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
datacode = h
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

1 Like
94

All this noise can be removed by just deleting or commenting out the “230V” calibration line in emonhub.conf as it is not used by the RFM2Pi’s.

Rather than creating an emonpi interfacer based on the jeeinterfacer, the jeeinterfacer was modified to suit the emonpi and the true “jee” devices (based on JeeLib protocol) have to deal with emonpi specific stuff. So when emonhub tries to set your RFM2Pi to non-US mode

emonhub tells us the command was politely acknowledged by the RFM2Pi

But then the RFM2Pi spits out the whole table of VALID commands since 1p is not understood, because there is no AC voltage selection on an RFM2Pi or any other Jee device for that matter. What you see in the log is emonhub acknowledging all the content from the RFM2Pi on the serial port.

95

That suggests there is an issue with the restored settings for emonhub although you need to expand on all broken. Is it just the feeds do not appear?

https://guide.openenergymonitor.org/setup/update/

Go to section 3.