Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Help getting started
#1
Received my 2 monitors yesterday (shipping to the Netherlands). After connecting the monitor that's based on the 1102 sensor, I could update the WiFi settings and the latest firmware was automatically updated. Very smooth! I did have some issues though getting the monitor to update values to ThingSpeak.

When I tried the other monitor, with the 7160 sensor (+ temp/hum/press), it immediately started to update all 4 values to ThingSpeak (with a different API, of course).

Here's a dump of the output after connecting the 1102 monitor: I'm not an expert on this, do you notice anything that explains why this monitor won't show the "Raw CO2" values like the 7160 monitor?

Many thanks!
Etienne

Code:
Searching for v.Air Trying : COM7

.  . [È$l]
[,4ð]
[¤$r[ùxIÒ]
[ú]
[…]
[Heap Heap at start: 34872]
[No I2C Devices found

vESPrino]

vESPrino found on : COM7
[OK
ready >]
[OK

vESPrino v1.16 build20160925]
[IP address: 0.0.0.0
Chip ID: CFC413]
[ready >.]
[OK
---vESPrinoCFG_start---
isMigrated=1
rf.CO2=136
rf.PM25=137
rf.PM10=138
rf.TEMP=140
rf.HUM=141
rf.PRES=142
rf.GEN=143
send.interval=120
wifi.ssid=[SSID that I entered]
wifi.p1=[password]
tsKey=[thingspeak API]
custom_url_arr0=#http://api.thingspeak.com/update?key=[Correct API]&field1=%CO2%
---vESPrinoCFG_end---
ready >]
[.]
[.

--- Setup PLUGINS ---
Setup plugin: Neopixel
Setup plugin: TimerManager

--- Setup SENSORS ---
Setup sensor: TEST
Setup sensor: CO2]
[CO2 Sensor SW Ver: BS V3.029 0i
CM1102 Dual Beam NDIR sensor
CO2 now: 550
Setup sensor: SI7021
Setup sensor: BME280
Setup sensor: PM2005
Setup sensor: CDM7160

--- Setup DESTINATIONS ---
Setup Destination: CustomHTTP
Setup Destination: SerialDump
Setup Destination: MQTT
Setup Destination: RFX10
Heap At setup end: 32144
Waiting for WiFi ready >.]
[.]
[.]
[.]
[IP address: 192.168.xxx.xxx in 13306 ms
GOT IP]
[fg: 20160925, fc: 0, bn:20160925
ready >
--- DestHanlder: sendValue ---]
[CustomHTTPDest::process
CustomHTTPDest::invoke = http://api.thingspeak.com/update?key=[Correct API]&field1=%CO2%]
[Response Code: 500
CLOSED]
[SerialDumpDest::process
MQTTDest::process
RFDest::process
ready >]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[OK
ready >]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[OK
ready >]
[--- DestHanlder: sendValue ---]
[CustomHTTPDest::process
CustomHTTPDest::invoke = http://api.thingspeak.com/update?key=[Correct API]&field1=860.00]
[Response Code: 200
CLOSED]
[SerialDumpDest::process
CO2    : 860.00
MQTTDest::process
RFDest::process
ready >]
[--- DestHanlder: sendValue ---]
[ready >]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[OK
ready >]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[OK
ready >]
[--- DestHanlder: sendValue ---]
[CustomHTTPDest::process
CustomHTTPDest::invoke = http://api.thingspeak.com/update?key=[Correct API]&field1=860.00]
[Response Code: 200
CLOSED]
[SerialDumpDest::process
CO2    : 860.00
MQTTDest::process
RFDest::process]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[OK
ready >]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
[--- DestHanlder: sendValue ---]
Reply
#2
Hi Etienne,


I am glad that it seems to be working well.
The raw CO2 is rather a debug message that has to go away.
In general the CDM reads CO2, but it takes a minute until some internal averaging logic kicks in, and until then - the raw CO2 value is not taken int account (but i dumped it for debugging)
the CM1102 sensor works in a way that in the first 2 minutes it reports 550 ppm (i do not know why they choose this value Smile) ), and then it starts to report the correct values.

What were your issues with TS? I am currently reworking the configuration tool and writing (finally) some docs, so i could add this details there

Regards, Vladimir
Reply
#3
Hi Vladimir,

The CDM-based monitor works perfectly: it uploads the values to TS after I entered the API in the configuration tool.
The CM1102-based monitor does not upload any values though, after configuring it in the same way as the CDM (but of course with a different API). It's connected to the WiFi using the configuration tool (confirmed the connection on my router), but on the TS site it shows 0 values were received.

Does the code I pasted in my 1st post from the CM1102 look OK?
Thank you very much!

Regards,
Etienne
Reply
#4
ahhh i saw in the log that the reqeust to TS is being done but i did not understand that you do not get anything...
if you try to invoke the same url from a browser - does it work ?
try to send a command (from the input field at the bottom)
debug
it will the dump a bit more details, and especially the response from TS, it is the number of entries in the channel
Reply
#5
OK. I have my gadget (a CDM 7160), but I seem to be missing the 'basic info' page. There was nothing in the parcel with a clue. I found this website/forum with a bit of duckduckgoing.

Plugging into USB gives me

[710364.564061] usb 4-1: new full-speed USB device number 16 using uhci_hcd
[710364.725618] usb 4-1: New USB device found, idVendor=1a86, idProduct=7523
[710364.725623] usb 4-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[710364.725626] usb 4-1: Product: USB2.0-Serial
[710366.251065] usbcore: registered new interface driver ch341
[710366.251095] usbserial: USB Serial support registered for ch341-uart
[710366.251126] ch341 4-1:1.0: ch341-uart converter detected
[710366.263793] usb 4-1: ch341-uart converter now attached to ttyUSB0

And I can connect with screen but I don't know what speed I should be using. Does it say somewhere? At 115200 I see nothing, but no wrong-speed garbage either. Is the protocol documented somewhere?

If I press the button a green LED shows whilst it is held. Still nothing on serial port.

Where is the 'how to use you gadget' page? I did look around the http://vair-monitor.com site and found out about vesprino, but nothing on how to use the vair-monitor. control methods, data out methods, power (does it have a battery, does it need to be USB-powered permanently? - I assume yes), what do the LED colours mean (it was faint purple when I first powered it up).

Clues welcome.
Reply
#6
(11-18-2016, 02:59 AM)Wookey Wrote: ...

Clues welcome.
I am sorry for the confusion, and that you needed to spend so much time searching this.
It is true that i am a bit lagging with documentation. 
If you go to http://vair-monitor.com/ - there is a big blue button [Setup Instructions] - that leads to this page: http://vair-monitor.com/device-types/
With details about driver installation (in case you need them) and the Chrome app used to setup the device.

I assume your "Internal Spam Filter" that protect you from this typical page template has filtered it out :Smile will think how i can improve it to avoid confusion, maybe i can also add a button on the top right as well.

About the LED and colors - they are still to be defined (there is one forum topic to discuss ideas about it (linked from the page above))
About the power - it has to be powered with 5V usb, there is no battery in this model

If you have other problems - do not hesitate to ask Smile
Reply
#7
Cheers for the quick response.
I did see that but I kind of ignored it as I don't use Chrome. Hadn't realised it was the only way to configure things.
Seems to work fine with Chromium.
And via that I discover: https://github.com/vlast3k/simple-co2-monitor-fw and https://github.com/vlast3k/vESPrino which seems to contain useful info.

Anyway my gadget seems to work, so I'll sort out getting HTTP or MQTT working
Reply
#8
Great Smile
Yeah.. i dream about the time when i will have sorted out all the initial startup glitches and consolidate all information on one place Smile
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)