COM port in use while OTA

So I ran into an issue on the Pi using AVRDUDE and this whole ota process. I have a python application running that connnects and talks the USB xBee dongle . When I run AVRDUDE it needs to use the COM port, and my python app doesnt get any data from other sensors on the network.

I was under the assumption I can do an OTA and listen for data at the same time. It takes about 8 min or so to do a full OTA and that is no good when you have 20-30 sensors on a network. Then you lose hours worth of data just to do an OTA.

Any thoughts or work arounds?

[davidsainty]

Yeah, that's something I'd like to solve too. You can definitely do OTA concurrently with other traffic, but having two applications talking to the same XBee is the tricky bit. My own workaround is to use a separate XBee for OTA. But it sounds like you require to be able to do firmware updates from your Pi's single XBee? Your Pi's app is Java?

…

On 29/12/2016 10:51 AM, "bluebrolly" ***@***.***> wrote: So I ran into an issue on the Pi using AVRDUDE and this whole ota process. I have a python application running that connnects and talks the USB xBee dongle . When I run AVRDUDE it needs to use the COM port, and my python app doesnt get any data from other sensors on the network. I was under the assumption I can do an OTA and listen for data at the same time. It takes about 8 min or so to do a full OTA and that is no good when you have 20-30 sensors on a network. Then you lose hours worth of data just to do an OTA. Any thoughts or work arounds? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACuqIeLJAYvCxRwuZH29dXQSBihuBa14ks5rMtnPgaJpZM4LXNhG> .

The Pi app is in Python. There is only 1 hardware serial port on the Pi.