Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
New Functionalities in Build 2017.02.19
Hi Guys,

Looks like i am slowly going out of the firefighting mode i was in since an year, so there was finally some time for doing some cleanup and finishing some things that i started long ago. The most notable improvements i added in the last month are listed below.

Device Configuration Saving
Up to now with each start, the firmware tried to find out what sensors there are. This is useless, so now once the device discovers all sensors it stores them, and the next time it simply reuses it. Sometimes due to the nature of I2C communication some sensor is not discovered immediately - so it is possible that after the discovery some sensor is not found. In the "Settings" menu, there is a button "Rescan Sensors", which will redo the process - so you can try it

Built-In Light Sensor
All CO2/Dust monitors, shipped after July 2016 include a Built-In Light Sensor. It's idea was to cooperate with the RGB Led and control it's brightness. Yet due to the fact that while the RGB Led is on, it affects the light sensor, using it required some tricks. Also the light sensor requires 100 ms to capture the ambient light. So now you will notice how the RGB Led will blink for ~150 ms, when the device detects that the ambient light changed. To enable it, in the Settings menu press the "Rescan Sensors" button. It will clean up the internal sensor configuration and restart the device to start clean. Then also check the checkbox there "BuiltIn Light Sensor" - Enable. This is needed, since it cannot be autodetected, and some devices do not have it.
Then there will be one additional placeholder that can be used "LDR". Values are from 0-1000, and due to the different nature of the boxes i've done in the last year, they are differently transparent. So in "vEsprino" tab there is a new config setting "BrightnessOverride", which in case of built-in sensor takes values -10:10, to make it brighter or dimmer. In case of no built in sensor, the values are 0:30 and control thre brightness
Note: Sadly some time ago i noticed that during assembly one of the 2 resistors required for the LDR to work correctly is sometimes not soldered. In December i showed this to the assebly guys and we did so changes to have it more consistent. But it is possible that on some devices the LDR will not work Sad It is also not easy to fix it as the corresponding part is a 0402 resistor, that gets soldered vertically. Now i use 0603 and it is all fine.

RGB Led for CO2 or Dust levels
I've also finally integrated the RGB Led with Dust/CO2 values. In "Generic Services / RGB Led" you can select which value to display ranges are 400-3000ppm for CO2 and 0-250 ug/m3.
Currently i sweep through Green, Yellow, Red, Lila. You can press the Color Sweep button, it will simulate a sweep through the whole range and dump the value, so that you can get an impression.
Note: the LED consumes 1-40 mA (e.g. yellow and lila are two colors, so twice more than green and red), so this may have some impact on the temperature measurements. Currently devices with CDM7160 consume ~20 mA, CM1106 ~100 ma (for them there is already some temperature correction, for those sold after Dec 2016 by default), and a Dust sensor adds 30mA. For those of you with the larger boxes, the impact should be in the range of 0.2-0.4 degrees, mostly if the ambient light is bright and the color is yellow

Disabling WebSocketServer and WiFiHotspot
It is now possible from the Connection tab to disable the autostarting of the WebSocketServer (so configuration over WiFi will not be possible) and the WiFiHotspot in case of no WiFi Connection

Removed Automatic Firmware update
The automatic firmware update was needed in the first months, where i was discovering showstoppers quite often, and it was a handy feature to easily update all devices. Now that everything is stable i've removed it, and now the Config tool checks if there is a newer version and let's you know you can update

Support for the vThing CO2 Monitor (r2)
The firmware can now be finally flashed also the the previous revision of the vThing - CO2 Monitor, that i was selling from Dec 2015 until June 2016. To flash it - update using this command
And then install the newer version of the configuration utility from here

Support for the vAir CO2 Monitor (r1)
I had to stop producing the original version of the vAir-CO2 Monitor, that had a 6 RGB Led color bar and display as printing the boxes was a big PITA. So i spent some time to design a new enclosure (w/o the gray outline, which made the problem), and prepared the firmware for them. I will share more details in a dedicated post.

Regards, Vladimir

I've tried this new firmware, but my C02 sensor seem to be not available :
Here the debug message after boot :
--- Setup SENSORS ---]
[CM110x : 0
SI7021 : 1
Found: SI7021
TEST : 0
BME280 : 0
BMP085 : 0
PM2005 : 0
CDM7160 : 0
DS18B20 : 0
LDR : 0
TSL2561 : 0
BH1750 : 0
APDS9960 : 0

Found Sensors: SI7021,

no more Co2 sensor.

(I have the CDM7160).

Perhaps my hardware is broken and it's not because of the firmware, but how to be sure ?

If you haven't tried - can you try to press the Rescan Sensors button from the Settings menu?
and see if it will be found then ?
if you want to try to revert to the previous firmware
here is the list of old ones
Here the settings menu in app, no rescan button ?

Attached Files Thumbnail(s)
aaaahhh thanks!
i had uploaded the new version, but didn't publish it... it will take now 1 hour or so until it becomes active
so just send this set of commands

just paste the whole string
Here the result, in debug mode :

Scheduling command: @nop
Scheduling command: ##prop_jset"stored.i2c"##prop_jset"cubic.co2.missing"##prop_jset"ds18b20.port"##prop_jset"has.sensors"##restart##
Scheduling command: prop_jset"stored.i2c"
Scheduling command: prop_jset"cubic.co2.missing"
Scheduling command: prop_jset"ds18b20.port"
Scheduling command: prop_jset"has.sensors"
Scheduling command: restart
[DEBUG is: 1LED SetColor:  seq1l
LED AutoBrg: 0.99]
[LED SetColor:  seq1lnlnd
LED AutoBrg: 0.99]
[vESPrino v1.16 build20170219
IP address:
Chip ID: CFC49D]
[Found i2c bus on SDA:SCL = D5:D1 (14:5)]
[Using I2C Bus on SDA:SCA (14:5)
i2c bus storing: 0x050E]
[--- Setup PLUGINS ---
No Name

--- Setup SENSORS ---]
[CM110x : 0
Turning on CM110x Sensor]
[Trying : 12,13
Getting CO2 Sensor Software Version]
Trying : 13,12
[g CO2 Sensor Software Version
[Trying : 12,13
Getting CO2 Sensor Software Version]
Trying : 13,12
[g CO2 Sensor Software Version
[Trying : 12,13
Getting CO2 Sensor Software Version]
Trying : 13,12
[g CO2 Sensor Software Version
[ERROR: Could not locate Cubic CO2 Sensor]
[IP address: x.x.x.x in 10942 ms
LED SetColor:  seqcncncnd]
[Scheduling command: wss_start

WebSockets Server started on wss://x.x.x.x:8266
Open to configure device online]
[ready >
SI7021 : 0
Found: SI7021
TEST : 0
BME280 : 0]
[BMP085 : 0]
[PM2005 : 0]
[CDM7160 : 0]
[DS18B20 : 0
DS18B20: searching on port: D1]
[DS18B20: searching on port: D5]
[DS18B20: searching on port: D6
DS18B20: searching on port: D7]
[DS18B20 is on: missing
LDR : 0
Found: LDR
TSL2561 : 0]
[BH1750 : 0]
[APDS9960 : 0]
[Found Sensors: SI7021,LDR,

--- Setup DESTINATIONS ---
[Heap At setup end: 30400
Device initialized.
Scheduling command: @sendNow
Check time from google]
[SI7021 : 78ms
LDR : 0ms

Should I try to open the box to check it ? It seems that the CDM7160 stay unavailable ..

Hmmm but wasnt it working befoee you updated?
Since few week the CO2 sensor seems to have some problems.
I'm not sure it's because of a new version of the firmware but perhaps.
Here you can find a view of my check of the sensor. The problem seems to be from the january 31.

My last chance is to try with a firmware version before this date ... or if you have an other idea ?

Attached Files Thumbnail(s)
aahhh, you can try with an earlier version, and also try opening it and check if some wire isn't gone loose. i use some jumper wires to wire up everything, so try pushing them a bit in/out

Forum Jump:

Users browsing this thread: 1 Guest(s)