Sensor Shield Firmware
vicatcu
Is anyone out there able to load the latest firmware from GitHub (github.com/wickeddevice/aqe_sensor_interface_shield) onto their Sensor Shield and report back on results?
Regards,
Vic
Paul Erkkila
--
You received this message because you are subscribed to the Google Groups "#AirQualityEgg" group.
To unsubscribe from this group and stop receiving emails from it, send an email to airqualityeg...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mark Tebbutt
Hi Vic.
I updated my egg to the latest firmware about 2 hours ago now. The NO2 output is very stable now but the update seems to have broken the CO sensor output which seems to be locked at 37597 ppb. My COSM feed is https://cosm.com/feeds/107106
Cheers,
Mark.T
Mark Tebbutt
I had to update the firmware again as the NO2 and CO sensor output froze. I used the Reflashing the AQE Shield steps on this link http://airqualityegg.wikispaces.com/Reflashing+the+AQE+Shield but it resulted in the sensors to freezing. Once I included the extra 3 commands below the shield updated correctly with regular updates from the NO2 & CO sensors.
avrdude -p t88 -c avrispmkII -P usb -u -U efuse:w:0xff:m
avrdude -p t88 -c avrispmkII -P usb -u -U hfuse:w:0xdf:m
avrdude -p t88 -c avrispmkII -P usb -u -U lfuse:w:0xee:m
However once I placed the senor egg outside around today 15:30 GMT the NO2 values started to ramp up to the now 0 ohm reading. CO2 values also seem far higher than prior to the firmware update. So on the face of it looks like the firmware fix still needs some work.
Andrew Lindsay
I've tried it using the hex file on github to try to resolve the -1 and maxed out NO2 readings.
It seemed to program ok using USBTiny but it will only read temp and humidity now, not the other sensors on the shield. No leds on the shield flash anymore. Seems its not working as it should.
I also tried resetting the fuses as detailed in a previous response, still nothing.
Any ideas?
Andrew
Victor Aprea
Andrew, what did you use to reprogram the device?
Vic
Andrew Lindsay
Its a 1.5 board with the ATiny88. Neither of the LEDs flash anymore, even when powered on.
Is the hex image compiled for the 88 or 48? That was the next thing, to download the source and setup the project in Eclipse and re-build it myself.
Cheers
Andrew
Victor Aprea
Paul Erkkila
vicatcu
At least one person resolved a similar situation by re-downloading the binaries from Git Hub. If you're just doing "pull" on a local repository you may be out of sync for some reason. If you're doing that make sure you do something like:
git pull origin master
Regards,
Vic
Andrew Lindsay
Just seen there was an update in past few minutes so took that and it seems to be doing something now. CO reading has a massively negative value and NO2 has massive positive value.
Looking for the remote sketch now.
Andrew
Victor Aprea
Andrew,
You have to update all your boards to use the latest firmware.
Regards,
Vic
Victor Aprea
And I haven't had a chance to upload binaries for the Nanodes yet, but you should be able to program them with the arduino IDE. Remember to update the libraries in your arduino installation if you do that though.
Regards,
Vic
Victor Aprea
vicatcu
I think all the software and binaries are all uploaded to Git Hub for what I'm calling the 2.0 baseline. I'm running a fully-loaded test Egg right now at https://cosm.com/feeds/102199. If you are comfortable reloading software on your units I'd encourage you to help build confidence by giving the latest firmware it a try. Again, this update requires each of the programmable boards in the system to be brought up to the latest version. I'll be watching the feed for any anomalies, but I expect this is the release we'll start shipping with. I also hope to post some reprogramming instructions this weekend.
Cheers,
Vic
Andrew Lindsay
I notice there is an extra feed on cosm for the 2 gas sensors, but the values are static, looks like a reference value. I'll see how it goes, but at present the NO2 reading is negative.
My feed is at https://cosm.com/feeds/103209
Cheers
Andrew
Victor Aprea
Andrew
Victor Aprea
Andrew Lindsay
Thanks
Andrew
Mark Tebbutt
I updated the remote and base to version 2 firmware and the senor shield to the latest version. I also place the no2 sensor in the CO sensor socket for 90 seconds to de-oxidise it.
Everything seemed find when the remote eggs was indoors but within a 20 minutes of placing the sensor outside the NO2 values started to ramp up and have now flipped to -2147483648 ppb. https://cosm.com/feeds/107106
I did substitute the US supplied power supplied with UK plug Strontronics 9V 550mA (5W) power supplies a few weeks after I received the eggs in the mail. Is 5W sufficient to power the remote egg and sensor heaters etc? http://shop.openenergymonitor.com/9v-550ma-plug-in-power-supply-uk-plug/
Cheers,
Mark.T Chorley UK.
Victor Aprea
Mark Tebbutt
Please could you explain to me why my last post was deleted and by whom? Censorship?
Mark.T
Victor Aprea
Mark Tebbutt
I entered a post Monday evening about my egg NO2 sensor working fine inside house but NO2 raw dropping to zero once placed outside after temperature drops below 13/14C. I will re post the full post tomorrow when I have a little more time.
See the attached PNG screenshot showing where my message has been deleted.
Mark.T
Victor Aprea
Mark.T
Bob Holmstrom
I just re-updated 104509 with all sensors. I updated the shield and the dust sensor - VOC and O3 were working before the re-update. Sensor moved from my wine cellar (very boring data) to the main section of the house at a return air grill for the heating system where there should be more activity. All sensors seem to be operating at the moment.
Note: There was an error on the first operation in the load.sh file for both the shield and the dust sensor. Here is the output from AVRDUDE for the dust sensor - all other operations completed without error:
Bob
bob-holmstroms-imac:aqe_dust_addon-master bobholmstrom$ avrdude -p t88 -c avrispmkII -P usb -u -U efuse:w:0xff:m
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e9311
avrdude: reading input file "0xff"
avrdude: writing efuse (1 bytes):
Writing | | 0% 0.00s ***failed;
Writing | ################################################## | 100% 0.06s
avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0xff:
avrdude: load data efuse data from input file 0xff:
avrdude: input file 0xff contains 1 bytes
avrdude: reading on-chip efuse data:
Reading | ################################################## | 100% 0.00s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0xff != 0x07
avrdude: verification error; content mismatch
avrdude done. Thank you.
Mark Tebbutt
I mounted the remote sensor egg back outside this evening around 17:00 BST. The outside temperature was around 11C. However I checked egg output again around 22:00 BST and found the NO2 sensor has flipped to 0 ohms at about 20:45BST which happens to be around the same time the temperature dropped from 10C to 9C.
I have created a PNG screenshot of the graph traces since Xively limits the graphs to around 6 hours now. Which I must say is severely limiting the usefulness of the AQE. The link to the PNG file is https://docs.google.com/file/d/0B-TArhxXUn3gME94UkdFbE1OdEU/edit?usp=sharing. I could not attach the PNG file to this post as the file is bigger than 2000 pixels.
A couple of days later on a slightly warmer day the NO2 level occasionally reverted to normal for a short period before dropping to 0 again. You can the pattern on this this screenshot https://docs.google.com/file/d/0B-TArhxXUn3gZjBiemNQREh3NDQ/edit?usp=sharing
So it seems the NO2 sensor is affected by temperatures below 10C. I doubt this could be a partial dry joint could it?
Victor Aprea
Mark Tebbutt
I think you may have missed that the NO2_r0.... value is present on both screenshots just the graph isn't expanded to save space on the said screenshots. If you click on the 100% button on the Google Drive menu the screenshot will zoom in to 100%. The screenshots are a composite of several screenshots using the snipping tool and an image editor.
I have flashed the eggs twice and the shield once (using the AVR programmer I bought especially to do so) to the latest firmware. All the sensors report version 32 firmware via the xively feed / graphs.
You can check my egg feed for yourself on https://xively.com/feeds/107106/?from_cosm=true.
I would really like to get this issue sorted out as I am due to take part in a NO2 calibration experiment with Andrew and 2 others from the UK using a NO2 diffusion tube as a reference starting on the 7th of June.
Thus would it possible to ship out a known working shield & NO2 sensor via DHL etc so that it will arrive at my home in the UK on Wednesday / Thursday and I will send the defective shield back to you via normal priority mail. I am happy to pay for the difference in express shipping?
Kind regards,
Mark Tebbutt.
Victor Aprea
Gavin
> Hey all,
>
> Is anyone out there able to load the latest firmware from GitHub (github.com/wickeddevice/aqe_sensor_interface_shield) onto their Sensor Shield and report back on results?
>
> Regards,
> Vic
Hi
Is there an EASY (I'm not a Linux person) to follow update process, along with the parts I need or is there anyone in the UK I can post my Egg parts to to be flashed up.
I don;'t mind either process but as I said it needs to be easy to follow for a non linux person.
I have the NO2 sensor issue -1 Ohms and my Base egg locks up for a while every so ofter, sometimes it recovers, other times I need to power cycle it. The lockup sometime freezes with a random colour on the LED (Seen Blue, Green Yellow and Magenta at lockup time at maybe 50% brightness, or others nothing till I review my readings.
Gavin
Any options for a UK person to do the update?
Paul Erkkila
Gavin
> Otherwise you would have another feed per sensor named something like NO2_r0_.
Silly question but once I flashed my NO and CO sensors the R0 reads -1 Ohms. Should I have reloaded some calibration value back to it?
Victor Aprea
Not a silly question, sounds like you didn't write the eeprom. Are you using the load scripts from GitHub?
Vic
Gavin
> Not a silly question, sounds like you didn't write the eeprom. Are you using the load scripts from GitHub?
>
> Vic
>
I followed your videos :)
Actually I Flashed the main board, then followed http://airqualityegg.wikispaces.com/Reflashing+the+AQE+Shield to so the shields.
What step may I have missed?
I still have to flash the Dust sensor so will have to go into the garden anyway soon (rain permitting)...
Gavin
My message had been deleted, Maybe I forgot to hit send and the draft has vanished.
Dust and "main" boards reflashed but now they are awol, both eggs have been reset and power cycled. The Dust sensor is still reported as at firmware 16 as there's been no updates at all, so something's gone wrong in the flashing, Will re-do it tonight.
The VOC and 03 are still reporting so part of the main board is OK, just not the NO, CO, and Dust sensors.
Actually I may bring the remote egg indoors so I can monitor them without having to look really dubious crouching by a garden wall with a laptop.
Gavin
OK, Status of play...
I have an Egg, with add on Dust, VOC and O3 sensors. Prior to installing the VOC and Dust sensors it was working fine.
VOC and O3 are at Firmware 32 so had to reflash the old bits up. I have a AVRISP programmer not a AVRISP2. BUT if I set the line to be AVRISP I get an error of avrdude: stk500_getsync(): not in sync: resp=0x00
Flashed the mainboard (marked V1.5) up to 32 and all was well, but either missed or failed on the eep step and so the sensors were reporting but the values were screwy.
So before I stared I put the FTDI cable on the base egg and noticed that the NO/CO/Dust sensors were not reporting back at all to there's the fault.
Reflashed them again...
Starting with the main board. Ran railroad.exe, got the flashing LED's and then did the upgrade and EEP flash.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:railroad.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "railroad.hex"
avrdude: input file railroad.hex auto detected as Intel Hex
avrdude: writing flash (1542 bytes):
Writing | ################################################## | 100% 3.51s
avrdude: 1542 bytes of flash written
avrdude: verifying flash memory against railroad.hex:
avrdude: load data flash data from input file railroad.hex:
avrdude: input file railroad.hex auto detected as Intel Hex
avrdude: input file railroad.hex contains 1542 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 2.98s
avrdude: verifying ...
avrdude: 1542 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:aqe_sensor_interface_shield
.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "aqe_sensor_interface_shield.hex"
avrdude: input file aqe_sensor_interface_shield.hex auto detected as Intel Hex
avrdude: writing flash (3986 bytes):
Writing | ################################################## | 100% 9.02s
avrdude: 3986 bytes of flash written
avrdude: verifying flash memory against aqe_sensor_interface_shield.hex:
avrdude: load data flash data from input file aqe_sensor_interface_shield.hex:
avrdude: input file aqe_sensor_interface_shield.hex auto detected as Intel Hex
avrdude: input file aqe_sensor_interface_shield.hex contains 3986 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 7.66s
avrdude: verifying ...
avrdude: 3986 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:aqe_sensor_interface_shield
.eep
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "aqe_sensor_interface_shield.eep"
avrdude: input file aqe_sensor_interface_shield.eep auto detected as Intel Hex
avrdude: writing flash (8 bytes):
Writing | ################################################## | 100% 0.03s
avrdude: 8 bytes of flash written
avrdude: verifying flash memory against aqe_sensor_interface_shield.eep:
avrdude: load data flash data from input file aqe_sensor_interface_shield.eep:
avrdude: input file aqe_sensor_interface_shield.eep auto detected as Intel Hex
avrdude: input file aqe_sensor_interface_shield.eep contains 8 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.03s
avrdude: verifying ...
avrdude: 8 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
Repeated with the Dust sensor.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:railroad.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "railroad.hex"
avrdude: input file railroad.hex auto detected as Intel Hex
avrdude: writing flash (1542 bytes):
Writing | ################################################## | 100% 3.49s
avrdude: 1542 bytes of flash written
avrdude: verifying flash memory against railroad.hex:
avrdude: load data flash data from input file railroad.hex:
avrdude: input file railroad.hex auto detected as Intel Hex
avrdude: input file railroad.hex contains 1542 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 2.98s
avrdude: verifying ...
avrdude: 1542 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:aqe_sensor_interface_shield
.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "aqe_sensor_interface_shield.hex"
avrdude: input file aqe_sensor_interface_shield.hex auto detected as Intel Hex
avrdude: writing flash (3986 bytes):
Writing | ################################################## | 100% 9.02s
avrdude: 3986 bytes of flash written
avrdude: verifying flash memory against aqe_sensor_interface_shield.hex:
avrdude: load data flash data from input file aqe_sensor_interface_shield.hex:
avrdude: input file aqe_sensor_interface_shield.hex auto detected as Intel Hex
avrdude: input file aqe_sensor_interface_shield.hex contains 3986 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 7.64s
avrdude: verifying ...
avrdude: 3986 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
C:\Users\Gavin\Desktop\egg\Air-Quality-Egg-master\aqe_sensor_interface_shield-ma
ster>avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:aqe_sensor_interface_shield
.eep
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.06s
avrdude: Device signature = 0x1e9311
avrdude: erasing chip
avrdude: reading input file "aqe_sensor_interface_shield.eep"
avrdude: input file aqe_sensor_interface_shield.eep auto detected as Intel Hex
avrdude: writing flash (8 bytes):
Writing | ################################################## | 100% 0.03s
avrdude: 8 bytes of flash written
avrdude: verifying flash memory against aqe_sensor_interface_shield.eep:
avrdude: load data flash data from input file aqe_sensor_interface_shield.eep:
avrdude: input file aqe_sensor_interface_shield.eep auto detected as Intel Hex
avrdude: input file aqe_sensor_interface_shield.eep contains 8 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.03s
avrdude: verifying ...
avrdude: 8 bytes of flash verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
No Errors so all seems well. Looks similar to the screenshots on the flashing site,
However the log form thr FTDI cable still shows it's not seeing the main board.
I can only assume it's the AVRISP at fault somehow but the railroad.hex file correctly flashes the LED's.
Any thoughts?
Stack: 230
[Air Quality Egg - Base Egg - v2.01]
Unit Address: 00_04_A3_8C_1B_AC
Pairing complete
Egg Serial #: 00:04:a3:8c:1b:ac
IP: 192.168.2.195
GW: 192.168.2.1
DNS: 192.168.2.1
Stack: 150
SRV: 64.94.18.121
Previously provisioned
Packet Received @ 95381
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 0
Sensor Type: Temperature
Sensor Units: deg C
Sensor Value: 28
Sensor Type: Temperature
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 100680
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 1
Sensor Type: Humidity
Sensor Units: %
Sensor Value: 1
Sensor Type: Humidity
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 105763
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_raw
Sensor Units: ohms
Sensor Value: 16341
Sensor Type: O3_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 110780
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_r0
Sensor Units: ohms
Sensor Value: 11000
Sensor Type: O3_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 115928
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3
Sensor Units: ppb
Sensor Value: 211
Sensor Type: O3
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 121036
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_raw
Sensor Units: ohms
Sensor Value: 132183
Sensor Type: VOC_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 126053
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_r0
Sensor Units: ohms
Sensor Value: 1500012
Sensor Type: VOC_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 131159
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC
Sensor Units: ppm
Sensor Value: 16
Sensor Type: VOC
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 215390
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 0
Sensor Type: Temperature
Sensor Units: deg C
Sensor Value: 27
Sensor Type: Temperature
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 220689
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 1
Sensor Type: Humidity
Sensor Units: %
Sensor Value: 1
Sensor Type: Humidity
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 225771
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_raw
Sensor Units: ohms
Sensor Value: 22452
Sensor Type: O3_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 230789
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_r0
Sensor Units: ohms
Sensor Value: 11000
Sensor Type: O3_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 235935
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3
Sensor Units: ppb
Sensor Value: 211
Sensor Type: O3
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 241044
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_raw
Sensor Units: ohms
Sensor Value: 106864
Sensor Type: VOC_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 246062
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_r0
Sensor Units: ohms
Sensor Value: 1500012
Sensor Type: VOC_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 251167
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC
Sensor Units: ppm
Sensor Value: 16
Sensor Type: VOC
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 335400
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 0
Sensor Type: Temperature
Sensor Units: deg C
Sensor Value: 26
Sensor Type: Temperature
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 340700
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_8C_28_8D
Sensor Index: 1
Sensor Type: Humidity
Sensor Units: %
Sensor Value: 1
Sensor Type: Humidity
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 345782
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_raw
Sensor Units: ohms
Sensor Value: 21240
Sensor Type: O3_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 350798
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3_r0
Sensor Units: ohms
Sensor Value: 11000
Sensor Type: O3_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 355943
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_2A_47
Sensor Index: 0
Sensor Type: O3
Sensor Units: ppb
Sensor Value: 199
Sensor Type: O3
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 361052
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_raw
Sensor Units: ohms
Sensor Value: 102988
Sensor Type: VOC_raw
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 366069
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC_r0
Sensor Units: ohms
Sensor Value: 1500012
Sensor Type: VOC_r0
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Packet Received @ 371175
Packet Type: 33
Remote Firmware Version: 32
Remote Station Address: 00_04_A3_8C_28_8D
Source Sensor Address: 00_04_A3_AC_11_13
Sensor Index: 0
Sensor Type: VOC
Sensor Units: ppm
Sensor Value: 16
Sensor Type: VOC
Preparing stash
Sending data to Cosm
Data sent
>>> RESPONSE RECEIVED ---
Gavin
> Me again...
Thinking about it, the NO/CO sensors upgraded to FW 32 by this method before the eep file mistake, so I know the upgrade should work....
Gavin
> Me again...
Possibly I'm talking to myself...
Working on a hunch (the sensors went to FW32 right) I reflashed them with the HEX file, but stopped before the eep file flashing.
The sensors are now seen and working. However I've still not got the Dust sensor reporting in after the flashing, and I realised I rather stupidly flashed my VOC sensor instead of the Dust sensor so that's not working now either.
Now I've also realised I've stupidly uploaded the wrong code to the Dust and VOC shields, they need Vic's Dust and VOC Hex files, not the same one as the master shield file and I can push the eep to them. but anyone know why the first EEP causes my CO and NO files to fail?
The EEP file was from the WickedDevice/aqe_sensor_interface_shield area on GitHub?
Out most of the weekend so any answers will be tried on Sundar morning or Late Sun evening..
Gavin
OK, All sensors up and reporting after reflashing them all, but the reflashed CO, NO, Dust and VOC all have a R0 of -1 so are basically reporting wrong values.
However I'm stuck how I get the EEP file on to them.
Flashing the hex I use the line
avrdude -p t88 -c avrisp2 -e -P usb -U flash:w:aqe_sensor_interface_shield.hex
Adding the EEP I use the line
avrdude -c avrisp2 -p t88 -e -P usb -U eeprom:w:aqe_sensor_interface_shield.eep
As taken form the Wiki Space entry. As far as I can work out what I'm doing is wiping out the .HEX file when I load the EEP and so then the sensor doesn't s work as the microchip doesn't know what to do.
Am I missing some option or using the wrong command to load the EEProm?
HELP!!!, what am I doing worong?
David Gobbett
I am at a similar point in reprogramming my wired AQE. I am using a $3
USBasp programmer. After roughly creating a 10 to 6 pin adaptor for the
programmer, I managed to flash with the aqe_sensor_interface_shield.hex
file. However, the next/final step on the page
http://airqualityegg.wikispaces.com/Reflashing+the+AQE+Shield is to flash
the EEPROM with the aqe_sensor_interface_shield.eep file. After I do that, I
get no LEDs working even after repowering the shield and/or pressing the
reset button. Although I've not connected the unit to the network to test
it, it is clearly not behaving as expected - no LEDs flash at any stage
whatsoever. It seems OK again if I reflash with the .hex file.
It is unclear to me whether this final step is the same as programming the
nanode using the FTDI cable which I have previously done successfully. Can
someone please confirm this? And can someone please explain in simple
language what the differences are between these things?
Regards
David
David Gobbett
Instead of using AVRDUDE, I used a program called ProgISP (version 1.72) which the kind eBay seller of my USBASP device sent me. This allowed me to load both the flash and eeprom files in a single operation. After doing that, the LEDs were behaving as expected, so I plugged in the AQE to my router, and data was getting to Xively from all sensors! And what's more, all sensors are showing version 32 (except for humidity and temperature which show version 34).
However, there are still a lot of decimal places on the data on Xively https://xively.com/feeds/115550 Furthermore, I don't really know what reasonable values for CO and NO2 are but they seem to be in the same league as a couple of others I found on Xively.
Regards
David
-----Original Message-----
From: Gavin [mailto:rcmode...@gmail.com]
Sent: Monday, 19 August 2013 6:30 PM
To: airqua...@googlegroups.com
Cc: da...@cycad.id.au
Subject: Re: [#AirQualityEgg] Re: Sensor Shield Firmware
Hi
The key part is probably the -U field needs to be EEPROM not FLASH
avrdude -p t88 -c avrisp2 -e -P COM5 -U flash:w:aqe_sensor_interface_shield
.hex
avrdude -p t88 -c avrisp2 -e -P COM5 -U eeprom:w:aqe_sensor_interface_shield
.eep
Gavin
Tried that, I can't even work out how to use the program... I suspect it's not seeing the fact my programmer is on COM4 as all I get is errors and most toe ht program is in Chinese.
Gavin
Well ProgISP didn't work, I suspect it's not compatable with my programmer as I get a chip read error, or I've got something wrong somewhere. Will keep trying but it's not hopefull. The AVRDUDE works with the same wiring so it's probably not compatible.
Vicatcu: Any other suggestions how I get the eeprom programmed? I know I could send it to you, but when the next update comes along I'll be in the same boat, and I'm reluctant to buy another programmer as the AVRISP should be capable, and can program the HEX codes just not the EEP part for some reason.
May try AVRStudio next...
Gavin
The wikispaces line looks like it's wrong, Using
avrdude -c avrisp2 -p t88 -P COM5 -U eeprom:w:aqe_sensor_interface_shield.eep
worked for me. Basically taking out the -e so the chip was not erased worked for me, it had just been erased to put the Hex value on, and the -e on the eep file erased the hex code.
Added a note into the Wikipage entry for others to follow.