Notifications
Clear all
Topic starter
2022-01-23 5:30 pm
I've seen how using Bluetooth modules can be used for wireless (remote) downloading of Arduino MCUs, but can it be done with 433 MHz RF modules? I have two UNOs hooked up (using Dronebot tuturial) with transmitter sending data (temp and humid) via radio to the receiver. Works well. But I have 3 projects (2 UNO and one Teensy3.2) outside that I want to update remotely, eg updating codes. To do it now, I have to hook up a lap top outside to a USB cable. If I could just send the compiled code to the unit, that would work I think.
I have ESP32 and ESP8266 devices but don't want to go that route...too many changes required and Teensy circuit likely would not work.
I can't make the Bluetooth devices work with Win11. I've tried for 2 weeks and watched 20 videos.
2022-01-23 6:13 pm
Hi @queenidog,
I don't know the answer to your question, but I can see a couple of issues to consider, especially if you are just thinking of replacing the USB cable with a "wireless cable".
-------
Downloading code from PC to Arduino from Arduino IDE is clearly a 'handshaked' conversation with data going in both directions. Although the only 'real' information flow is from PC/MAC to Arduino, it relies on feedback from the Arduino to the PC/MAC to move from one step to the next.
The cheap 433MHz transmitters and receivers I have seen are unidirectional. So at the very least you would need a transmitter and receiver at each end.
-----------
I have the impression 433MHz transmissions are somewhat 'hit and miss' ... for a sensor that sends the same message several times, or one that sends an update on say room temperature every minute, loosing the odd message is not a problem.
However, missing 0.01% of a 10 kByte code update is definitely a problem. Bluetooth, Ethernet (including WiFi) and other 'sophisticated' communications systems include protocols to check for data loss and perform automatic retries.
I don't know, but I would guess the Arduino IDE assumes that it has a USB cable which will either faithfully transmit without loosing data, or fail completely ... so a simple check and report failure strategy is sufficient ... requiring the user to fix the problem and retry manually.
--------
I emphasise these are only my cynical views ... personally, I would look elsewhere for a solution, unless you can find a system that is guaranteed to be 'plug and play' in this situation.
Best wishes, Dave