Unfortunately the firmware is not seeing the sensor (see output below) - any suggestions?
I also purchased an optical sensor - this has RJ45 connector that i have removed to reveal black, red and blue cables. Which terminals should each wire be connected on the emontx v3.2?
In short - no. That sketch works for me, did you get the temperature sensor from the OEM Shop?
You did get the terminals correct? (from the PCB legend).
Does it work if you transfer the red wire to terminal 2 (3.3 V)?
Here’s what I see, with no sensors other than the DS18B20 and blank lines deleted:
emonTx V3.2 Discrete Sampling V2.00
OpenEnergyMonitor.org
POST.....wait 10s
CT 1 Calibration: 90.90
CT 2 Calibration: 90.90
CT 3 Calibration: 90.90
CT 4 Calibration: 16.60
RMS Voltage on AC-AC Adapter input is: ~1V
AC-AC NOT detected - Apparent Pwr measure enabled
Assuming VRMS: 230V
Assuming pwr from batt / 5V USB - pwr save enabled
CT 1 detected
Detected 1 DS18B20..using this for temperature reading
RFM12B Initiated:
Node: 10 Freq: 433Mhz Network: 210
CT1 CT2 CT3 CT4 VRMS/BATT PULSE Temperature 1-1
19107 0 0 0 0 0 0
4500 0 0 0 0 0 210
1062 0 0 0 0 0 210
249 0 0 0 0 0 210
[etc]
For the optical pulse detector, the wire colours are (from Pulse counting — OpenEnergyMonitor 0.0.1 documentation - emonTH V2): red (3.3V power), black (GND) and blue (pulse) wires.
The 3.3 V power on your emonTx V3 is terminal 2, GND is 3, the pulse input 4.
Note the optical sensor output isn’t a pulse, it’s just the light level (over a very limited range, so mostly close to 0 V or 3.3 V). So you can check that with a multimeter and daylight. There’s a circuit diagram here: First try with EmonPi - Pulsecount stuck at 1 - #16 by Robert.Wall
I was assuming that you had not changed the sketch in any way - is that correct?
If so, I can’t think it can be anything other than either your V3.2 had developed a fault or has always been faulty (and obviously you had no means of knowing), or it’s a faulty sensor. Time to email the shop: [email protected]