Can't see the arduino TX shield readings on my emonPi!

I soldered in place an arduino tx. Then I loaded the C1234 sketch to read and send 433MHz data. However, the arduino TX shield doesn’t show up anywhere as an input node.
Please help. Been strugling all day. Soldering was performed without issues. I double cheched it with my multimeter. I eaven tested with my second arduino TX shield. Both don’t work.
Emonpi works perfectly, hence I can see the inputs from an emonTX v3 that I also have.

Which radio module do you have?
Which sketch are you trying to use? (There is no “C1234” sketch.)

Here are some things to check:
Have you set the correct frequency (433MHz) and type of radio module (RFM12B/RFM69CW)?
Does the LED on your Shield flash every 2 s?
Does the transmitted data for the shield’s NodeID correspond with the section for that NodeID in emonhub.conf (and is the NodeID different to your other Shield and your emonTx V3? - all 3 must have different NodeIDs if you use them together).

Can you post the serial output of the Arduino that’s connected emonTx Shield at startup (9600 baud).

Have you set the emonTx Shield RFM jumpers:

This is the defaut setup for Arduino Uno:

See emonTx shield build guide.

Thx for the rapid response.

@Robert.Wall I misspelled the name. It is called CT1234 here is a link: https://github.com/openenergymonitor/emonTxFirmware/tree/master/emonTxShield/Shield_CT1234

@glyn.hudson : the arduino serial monitor output:
emonTX Shield CT123 example
OpenEnergyMonitor.org
Node: 6 Freq: 433Mhz Network: 210
0 36 0 28
0 35 0 25
0 33 0 28
0 35 0 26
0 35 0 28
0 35 0 28

I have 2 CTs attached, and values look right.

@glyn.hudson regarding the setup. In the picture you posted there is the RFM69CW missing. I soldered the module based on the picture provided in the store:

And I also checked the emonHub.conf the newtworkGroup is 210 and id was 6. Here is a picture of mz HW setup:

Yes, the picture I posted was just to illustrate the jumper connections. Obviously you will need an RF module! Looking at the last photo you posted it looks like you have jumpers connected correctly and RFM69CW attached successfully.

Did you set #define RF69_COMPAT 1 on L53 in the code since you are using an RFM69CW?

I’ve just tested and the emonTx shield appeared for me on the emonPi Emoncms Inputs:

Double check the following node decoder is installed in emonhub.conf:

[[6]]
    nodename = emontxshield
    [[[rx]]]
       names = power1, power2, power3, power4, vrms
       datacode = h
       scales = 1,1,1,1,0.01
       units =W,W,W,W,V

That sketch is correct for the default emonhub.conf settings, so I think we can say that the problem is probably (but not certainly) elsewhere.

You didn’t say whether the LED flashes? The LED should flash immediately after the data is transmitted, so it is useful information to know what the LED does. The LED won’t flash if the wrong radio module is selected because the sketch will hang when it tries to set up the radio.

Glyn: Don’t some sketches have the LED turned on before the call to initialise the radio - hence the LED is on continuously if the radio setup hangs?

Correct, good point. If the radio was hanging due to incorrect #define RFM69 then the sketch would hang and not print any power values to serial. I’ve just tested this.

So I have 2 arduino tx Sheilds. I changed the value to 1 for both. Interestingly the yellow LED flashes on one board only if the value for #define RF69_COMPAT 0 is set to 0. For the other board changing it to 1 did the trick and is now visible in the inputs panel. What I don’t understand is the different behaviour on the second board. Soldering looks the same.

A new problem that I have is that on the emonPi , for the emontxarduinoshield I only see one line, rssi, and no CT1,2,3,4. I use the CT1234 sample.

It sounds like you either an RFM12B instead of RFM69CW on one of the shields or there is a fault in the solder joints, or there is a faulty module.

Progress! at least we have RF comms working. Can you post your emonhub.conf file and the output from emonhub.log. See if you can see any entries in the log file relating to node 6

Sure, here is the configuration: emonhub.conf.tar.gz (1.6 KB)
And a snippet of the log:

0,12,0
2016-05-16 15:16:02,667 INFO RFM2Pi Publishing: emonhub/rx/6/rssi -43
2016-05-16 15:16:02,670 DEBUG RFM2Pi 26472 adding frame to buffer => [1463411762, 6, 0, 0, 0, 12, 0, -43]
2016-05-16 15:16:02,671 DEBUG RFM2Pi 26472 Sent to channel’ : ToEmonCMS
2016-05-16 15:16:06,139 DEBUG RFM2Pi 26473 NEW FRAME : OK 5 2 0 1 0 3 0 86 94 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2016-05-16 15:16:06,144 DEBUG RFM2Pi 26473 Timestamp : 1463411766.14
2016-05-16 15:16:06,145 DEBUG RFM2Pi 26473 From Node : 5
2016-05-16 15:16:06,146 DEBUG RFM2Pi 26473 Values : [2, 1, 3, 241.5, 20.700000000000003, 0, 0, 0, 0, 0, 0]
2016-05-16 15:16:06,149 INFO RFM2Pi Publishing: emon/emonpi/power1 2
2016-05-16 15:16:06,152 INFO RFM2Pi Publishing: emon/emonpi/power2 1
2016-05-16 15:16:06,156 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 3
2016-05-16 15:16:06,159 INFO RFM2Pi Publishing: emon/emonpi/vrms 241.5
2016-05-16 15:16:06,162 INFO RFM2Pi Publishing: emon/emonpi/t1 20.7
2016-05-16 15:16:06,165 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2016-05-16 15:16:06,169 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2016-05-16 15:16:06,172 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2016-05-16 15:16:06,175 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2016-05-16 15:16:06,178 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2016-05-16 15:16:06,182 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2016-05-16 15:16:06,184 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2016-05-16 15:16:06,188 INFO RFM2Pi Publishing: emonhub/rx/5/values 2,1,3,241.5,20.7,0,0,0,0,0,0
2016-05-16 15:16:06,191 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2016-05-16 15:16:06,194 DEBUG RFM2Pi 26473 adding frame to buffer => [1463411766, 5, 2, 1, 3, 241.5, 20.700000000000003, 0, 0, 0, 0, 0, 0]
2016-05-16 15:16:06,195 DEBUG RFM2Pi 26473 Sent to channel’ : ToEmonCMS
2016-05-16 15:16:06,338 DEBUG RFM2Pi 26474 NEW FRAME : OK 6 0 0 0 0 0 0 15 0 0 0 (-42)
2016-05-16 15:16:06,341 DEBUG RFM2Pi 26474 Timestamp : 1463411766.34
2016-05-16 15:16:06,343 DEBUG RFM2Pi 26474 From Node : 6
2016-05-16 15:16:06,344 DEBUG RFM2Pi 26474 Values : [0, 0, 0, 15, 0]
2016-05-16 15:16:06,346 DEBUG RFM2Pi 26474 RSSI : -42
2016-05-16 15:16:06,348 INFO RFM2Pi Publishing: emon/emontxshield/power1 0
2016-05-16 15:16:06,351 INFO RFM2Pi Publishing: emon/emontxshield/power2 0
2016-05-16 15:16:06,354 INFO RFM2Pi Publishing: emon/emontxshield/power3 0
2016-05-16 15:16:06,357 INFO RFM2Pi Publishing: emon/emontxshield/power4 15
2016-05-16 15:16:06,359 INFO RFM2Pi Publishing: emon/emontxshield/vrms 0
2016-05-16 15:16:06,362 INFO RFM2Pi Publishing: emon/emontxshield/rssi -42
2016-05-16 15:16:06,367 INFO RFM2Pi Publishing: emonhub/rx/6/values 0,0,0,15,0
2016-05-16 15:16:06,371 INFO RFM2Pi Publishing: emonhub/rx/6/rssi -42
2016-05-16 15:16:06,377 DEBUG RFM2Pi 26474 adding frame to buffer => [1463411766, 6, 0, 0, 0, 15, 0, -42]
2016-05-16 15:16:06,379 DEBUG RFM2Pi 26474 Sent to channel’ : ToEmonCMS
2016-05-16 15:16:08,917 DEBUG RFM2Pi 26475 NEW FRAME : OK 6 0 0 0 0 0 0 12 0 0 0 (-42)
2016-05-16 15:16:08,921 DEBUG RFM2Pi 26475 Timestamp : 1463411768.92
2016-05-16 15:16:08,937 DEBUG RFM2Pi 26475 From Node : 6
2016-05-16 15:16:08,939 DEBUG RFM2Pi 26475 Values : [0, 0, 0, 12, 0]
2016-05-16 15:16:08,940 DEBUG RFM2Pi 26475 RSSI : -42
2016-05-16 15:16:08,943 INFO RFM2Pi Publishing: emon/emontxshield/power1 0
2016-05-16 15:16:08,945 INFO RFM2Pi Publishing: emon/emontxshield/power2 0
2016-05-16 15:16:08,948 INFO RFM2Pi Publishing: emon/emontxshield/power3 0
2016-05-16 15:16:08,951 INFO RFM2Pi Publishing: emon/emontxshield/power4 12
2016-05-16 15:16:08,954 INFO RFM2Pi Publishing: emon/emontxshield/vrms 0
2016-05-16 15:16:08,957 INFO RFM2Pi Publishing: emon/emontxshield/rssi -42
2016-05-16 15:16:08,961 INFO RFM2Pi Publishing: emonhub/rx/6/values 0,0,0,12,0
2016-05-16 15:16:08,963 INFO RFM2Pi Publishing: emonhub/rx/6/rssi -42
2016-05-16 15:16:08,967 DEBUG RFM2Pi 26475 adding frame to buffer => [1463411768, 6, 0, 0, 0, 12, 0, -42]
2016-05-16 15:16:08,968 DEBUG RFM2Pi 26475 Sent to channel’ : ToEmonCM

seems it gets it but it"s not displayed

I found something else. I also have the rpi 433 emonhub shield. On the emonhub I see the complete values for the txarduinoshield node. So only on the emonpi feed dashboard I don’t see the complete values.

using the latest emonSD-03May16.img

Sorin:
How to see which radio module you have.

Problem solved. I soldered some more and now both modules work. Thx for the help guys. What is still open is that emonpi sees only rssi and emonhub sees all feed node contents.

Yes, looks like power of 15W on power4 is being received (is this what you expected looking at serial O/P?) but not being displayed. Ok we’re making progress…

Could you check to see if the data is actually making it to MQTT, can you connect via SSH?

Then subscribe to MQTT shield topic:

mosquitto_sub -v -u 'emonpi' -P 'emonpimqtt2016' -t 'emon/emontxshield/#'

Alternately you could use MQTTlens Chrome Extension or any other MQTT client connected to the emonPi IP address on port 1883 with user name: emonpi and password: emonpimqtt2016

Let me know if you can see data being displayed from the shield