Hi Robert I have compiled and uploaded new firmware,… ( and it actually appears to be working ).
Well If I look in emonhub, it reports CT’s 1-12, (which has to be a plus.)
My only ( known ) problem is the CTs do not show up in emonPiCMS, and only only have 1-6 CTs listed,… which are not being updated,…
But the data is being broadcast on USB as follows;-
2024-04-17 12:59:56,661 DEBUG MQTT Publishing: emon/emonpi_5/t4 0
2024-04-17 12:59:56,662 DEBUG MQTT Publishing: emon/emonpi_5/t5 0
2024-04-17 12:59:56,663 DEBUG MQTT Publishing: emon/emonpi_5/t6 0
2024-04-17 12:59:56,664 DEBUG MQTT Publishing: emon/emonpi_5/pulsecount 0
2024-04-17 12:59:56,697 DEBUG USB0 Analog in = 0
2024-04-17 12:59:56,800 DEBUG USB0 Ch 1 I=3.230 W=699 VA=775 Wh=65 pf=0.9010
2024-04-17 12:59:56,903 DEBUG USB0 Ch 2 I=0.113 W=4 VA=27 Wh=0 pf=0.1322
2024-04-17 12:59:57,005 DEBUG USB0 Ch 3 I=0.108 W=8 VA=26 Wh=0 pf=0.2958
2024-04-17 12:59:57,108 DEBUG USB0 Ch 4 I=0.088 W=3 VA=21 Wh=0 pf=0.1361
2024-04-17 12:59:57,211 DEBUG USB0 Ch 5 I=1.968 W=445 VA=473 Wh=36 pf=0.9413
2024-04-17 12:59:57,315 DEBUG USB0 Ch 6 I=1.192 W=173 VA=286 Wh=18 pf=0.6040
2024-04-17 12:59:57,418 DEBUG USB0 Ch 7 I=0.022 W=0 VA=5 Wh=0 pf=0.0016
2024-04-17 12:59:57,521 DEBUG USB0 Ch 8 I=0.022 W=0 VA=5 Wh=0 pf=-0.0401
2024-04-17 12:59:57,624 DEBUG USB0 Ch 9 I=0.009 W=0 VA=2 Wh=0 pf=-0.0429
2024-04-17 12:59:57,728 DEBUG USB0 Ch 10 I=0.009 W=0 VA=2 Wh=0 pf=-0.0277
2024-04-17 12:59:57,831 DEBUG USB0 Ch 11 I=0.008 W=0 VA=2 Wh=0 pf=-0.0393
2024-04-17 12:59:57,934 DEBUG USB0 Ch 12 I=0.009 W=0 VA=2 Wh=0 pf=-0.0890
2024-04-17 13:00:01,557 DEBUG EmonPi2 735 NEW FRAME : OK 5 162 2 81 0 243 2 38 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2024-04-17 13:00:01,559 DEBUG EmonPi2 735 Timestamp : 1713355201.557728
2024-04-17 13:00:01,559 DEBUG EmonPi2 735 From Node : 5
2024-04-17 13:00:01,559 DEBUG EmonPi2 735 Values : [674, 81, 755, 235.9, 0, 0, 0, 0, 0, 0, 0]
2024-04-17 13:00:01,560 DEBUG EmonPi2 735 Sent to channel(start)' : ToEmonCMS
2024-04-17 13:00:01,560 DEBUG EmonPi2 735 Sent to channel(end)' : ToEmonCMS
2024-04-17 13:00:01,792 DEBUG MQTT Publishing: emon/emonpi_5/power1 674
2024-04-17 13:00:01,793 DEBUG MQTT Publishing: emon/emonpi_5/power2 81
2024-04-17 13:00:01,794 DEBUG MQTT Publishing: emon/emonpi_5/power1pluspower2 755
2024-04-17 13:00:01,795 DEBUG MQTT Publishing: emon/emonpi_5/vrms 235.9
2024-04-17 13:00:01,796 DEBUG MQTT Publishing: emon/emonpi_5/t1 0
2024-04-17 13:00:01,797 DEBUG MQTT Publishing: emon/emonpi_5/t2 0
2024-04-17 13:00:01,798 DEBUG MQTT Publishing: emon/emonpi_5/t3 0
2024-04-17 13:00:01,799 DEBUG MQTT Publishing: emon/emonpi_5/t4 0
2024-04-17 13:00:01,800 DEBUG MQTT Publishing: emon/emonpi_5/t5 0
2024-04-17 13:00:01,800 DEBUG MQTT Publishing: emon/emonpi_5/t6 0
2024-04-17 13:00:01,801 DEBUG MQTT Publishing: emon/emonpi_5/pulsecount 0
2024-04-17 13:00:01,964 DEBUG EmonPi2 736 NEW FRAME : OK 24 182 0 0 0 204 1 26 0 1 0 0 0 (-62)
2024-04-17 13:00:01,965 DEBUG EmonPi2 736 Timestamp : 1713355201.964103
2024-04-17 13:00:01,965 DEBUG EmonPi2 736 From Node : 24
I thourght for a while I was on to something,… now I have come across a brick wall in that avdude does not want to play ball with the command that had previously workd??
avrdude -C/opt/openenergymonitor/EmonScripts/update/avrdude.conf -v -pavr128db48 -carduino -D -P/dev/ttyUSB1 -b115200 -Uflash:w:$targetfile:i