💬 FOTA (Wireless Programming)
-
@Viciousman Thank you!
How do I create a Ethernet gateway?
Will I have to build this: https://www.mysensors.org/build/ethernet_gateway
or
Will I have to do some kind of configuration on the rpi and continue using my serial gateway?
@arraWX I find more simple to simply connect nrf24 to raspberry pi as instructed in https://www.mysensors.org/build/raspberry
But you can also build the Ethernet gateway with W5100. -
Dear all!
I have an mysensors ethernet gateway and nodes with nrf24 . I have an openhab2 controller. Could i use the above solution to program my nodes over the air through my current gateway? So i write my sketch on windows arduino and send it through my gateway to the node? Or i have to connect my computer direct to nodes over air?
-
You can use myscontroller to connect to the ethernet gateway and assign the firmware to upload for each node
-
You can use myscontroller to connect to the ethernet gateway and assign the firmware to upload for each node
-
Myscontroller works only as ethernet. Mycontroller should also work with mqtt gateway but I'm not sure about serial.
@gohan Ook! Are you talking about installing MysController on Raspberrypi (I think not)? If you are going to run it on Windows and connect to Raspi Ethernet gateway remotely then using the the same option we can remotely connect to a serially connected gateway on Raspberrypi (using a USB port) from MysController running on Windows.
Are there steps somewhere to install MysController on Raspi [some Windows pre-installer running on Debian Linux]? I remember reading some Mysensors posts here a couple of years back(!!!), but cant seem to locate it now...
-
@scalz do you have any specific reason why you use avrdudes to burn the fuses and burn bootloader separately, instead of using some board definitions matching the bootloader and using the burn bootloader method for Arduino interface ? I think that method is far more user intuitive for the average MySensors user ?
-
Using FOTA in myscontroller works only occasionally for me. Sometimes it works fine. But most often I get the following messages and nothing more happens.
The node is a sensebender micro. Gateway is rpi ethernet.
Has anyone experienced something similar? Anyone knows how to solve the problem?
EDIT: Problem solved. Reading this post I now understand that in order to get new fw into the node one has to update the sketch, refresh the repo in MysController and assign it the node.
-
Once I managed to burn the sensbender micro bootloader to the pro mini, how do I connect the external flash? Just connect it to pins D10 to D13? Is this the correct way of managing the fota in the sketch before the sleep?
@gohan I recently had some problems with fota and the sensebender sketch you refer to. In this thread @tekka suggested me to enable smart sleep. I used
smartSleep(MEASURE_INTERVAL);It seems that the smartSleep function has a "built in" MY_SMART_SLEEP_WAIT_DURATION_MS (which defaults to 500 ms). This makes the OTA_WAIT_PERIOD in the sensebender sketch redundant. I deleted it from the sketch.
FOTA now works successfully with my sensebender boards.
-
Hi guys! I burned mysbootloader but now rs485 doesn't work.. It's normal situation ? A would like to know if is possible to remote upload firmware via rs485 instead of radio. Thanks! Luca
-
I think I managed to get the flash properly wired and using myscontroller I was able to assign a FW and it started to transfer the new FW as soon as the node was available but at the end I get this failure on the node dedug
151898 OTA:FRQ:FW REQ,T=0078,V=0001,B=0316 151918 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001603 151971 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:780001001603909369058091690585FB882780F98F25 151984 OTA:FWP:RECV B=0316 151986 OTA:FRQ:FW REQ,T=0078,V=0001,B=0315 152006 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001503 152070 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:780001001503280586FB882780F99091690580FB95F9 152082 OTA:FWP:RECV B=0315 152084 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 152104 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 152586 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 152606 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 153088 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 153110 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 153589 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 153612 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 154091 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 154345 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 154593 OTA:FRQ:FW REQ,T=0078,V=0001,B=0314 154613 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=2,pt=6,l=6,sg=0,ft=0,st=OK:780001001403 155095 !OTA:FRQ:FW UPD FAIL 165586 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165597 !OTA:FWP:NO UPDATE 165849 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165859 !OTA:FWP:NO UPDATE 165873 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165883 !OTA:FWP:NO UPDATE 165896 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165906 !OTA:FWP:NO UPDATE 165918 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165931 !OTA:FWP:NO UPDATE 165943 TSF:MSG:READ,0-0-16,s=255,c=4,t=3,pt=6,l=22,sg=0:7800010014032405C550C13408F0C0E4C09364058091 165953 !OTA:FWP:NO UPDATEAfter this the node goes silent and I have to reset it to get it back. Log parser isn't helping much. Any idea where I can look ?
