01-11-2017, 05:11 AM
So I've performed some tests. The behavior is very weird for me.
As I reconnected the sensor today (after one day unpowered) the LED lid up violet and the sensor seems to operate normally. With the tool I could access the settings but as tried to flash the firmware (via the button) the LED did not change to red. Also on the „Send command“ line I tried otah did not change anything. No update within vAir Output window.
The communication seems having stopped again (refer to attached log).
I’ve performed a power cycle and the sensor just did nothing not even the violet LED illuminated.
I disconnected the boards inside the sensor which changed nothing also unfortunately.
At least each time it is connected, windows recognizes the connection of the new com port.
Trying again and reconnected the sensor again, the communication worked again via the tool. -> performing otah lit up the LED in red. But the tool reported:
"Will update from: http://anker-bg.com/vlast3k/vesprino/latest.bin
ledcolor red
ledbrg 80]
[HTTP error: connection refused]
[HTTP_UPDATE_FAILED"
(refer to attached file for complete log)
Than I tried also to flash via the command line tool, disconnected to tool before (refer to attached files).
Attached
The vAir Output within the tool
The output of esptool during trying to flash
The output of esptool during trying to erase
Finally yesterday I managed to activate the debugging mode but shortly after that the sensor stopped communication and operation again. Keeping the sensor powered it seems not having recovered during night.
So my current assumption is that communication via USB is not reliable (sometimes able to communicate, sometimes not), current status is: not able to communicate. Additionally the sensor operation is not reliable also, current status is: no operation.
As my other sensor is working well with the firmware from 3rd of Jan., I do not have in mind a firmware issue currently.
I’ll try to take some logs today in the evening with debug enabled. Also I’ve the impression that the behavior could be due to temperature (locally) and will try to detail this with ice spray as yesterday after a day unpowered first it operated normally.
Any other ideas to flash the eprom or to reanimate the communication?
Btw within the linked instruction for flashing from the command line, the link to the firmware redirects to an old firmware and you’ll need to copy paste the address, just in case you’d like to correct that.
Before you send a new one maybe could you think about adding also the parts to limit the supply voltage for my sensors (4) and let me know the additional costs for these parts?
I'll continue troubleshooting this evening.
As I reconnected the sensor today (after one day unpowered) the LED lid up violet and the sensor seems to operate normally. With the tool I could access the settings but as tried to flash the firmware (via the button) the LED did not change to red. Also on the „Send command“ line I tried otah did not change anything. No update within vAir Output window.
The communication seems having stopped again (refer to attached log).
I’ve performed a power cycle and the sensor just did nothing not even the violet LED illuminated.
I disconnected the boards inside the sensor which changed nothing also unfortunately.
At least each time it is connected, windows recognizes the connection of the new com port.
Trying again and reconnected the sensor again, the communication worked again via the tool. -> performing otah lit up the LED in red. But the tool reported:
"Will update from: http://anker-bg.com/vlast3k/vesprino/latest.bin
ledcolor red
ledbrg 80]
[HTTP error: connection refused]
[HTTP_UPDATE_FAILED"
(refer to attached file for complete log)
Than I tried also to flash via the command line tool, disconnected to tool before (refer to attached files).
Attached
The vAir Output within the tool
The output of esptool during trying to flash
The output of esptool during trying to erase
Finally yesterday I managed to activate the debugging mode but shortly after that the sensor stopped communication and operation again. Keeping the sensor powered it seems not having recovered during night.
So my current assumption is that communication via USB is not reliable (sometimes able to communicate, sometimes not), current status is: not able to communicate. Additionally the sensor operation is not reliable also, current status is: no operation.
As my other sensor is working well with the firmware from 3rd of Jan., I do not have in mind a firmware issue currently.
I’ll try to take some logs today in the evening with debug enabled. Also I’ve the impression that the behavior could be due to temperature (locally) and will try to detail this with ice spray as yesterday after a day unpowered first it operated normally.
Any other ideas to flash the eprom or to reanimate the communication?
Btw within the linked instruction for flashing from the command line, the link to the firmware redirects to an old firmware and you’ll need to copy paste the address, just in case you’d like to correct that.
Before you send a new one maybe could you think about adding also the parts to limit the supply voltage for my sensors (4) and let me know the additional costs for these parts?
I'll continue troubleshooting this evening.