The Orba arrived this morning, I was able to play with it for a bit before downloading the IOS app and being told to update the firmware. I did and after it completed the Orba will no longer turn on.
Windows 10 Orba app. I received my yesterday. Played with it a bit then downloaded the Orba app. Attached the Orba via USB and opened the app. I was told to update the firmware. So I did. Now the Orba is not turning on and is not recognized by the Orba app. Now reading others have had a similar issue. I have a Mac at work and will try the iOS version tomorrow. Any help will be appreciated.
@Michael, I'm in the same situation. I don't have access to a Macintosh and I've tried every combination of plugging, re-plugging, resetting, charging, and manipulating Windows' firewall and anti-virus that has been mentioned here and a few that I thought of on my own. Nothing has worked. Like you I've fallen back to the position of "sit and wait and hope that the Artiphon guys come up with a solution in the near future."
I assume you'all tried getting Orba connected and firmware updated using your different usb ports? a 2.0? 3.0? powered? unpowered? looked for error messages within windows device manager pertaining to usb ports? i know zero about apple stuff. I;ve seen poorly designed firmware updaters fail in some ports, but not in others, and in some machines but not in others. I have an audio interface that is like that.
I have the same problem. Plugged it in to a Windows 10 machine, tried to update firmware and I how have a lovely black paper weight. I've tried everything in this forum (except a Mac - I don't have one) and nothing has worked. I submitted a ticket so, hopefully, there will be a resolution soon.
Seems like a common thread in the successful recoveries by Will and Gary above is that if you're on a Mac, do the firmware update before updating the desktop app to the newer version. Think I'll uninstall it and roll back to the older one before my Orba arrives (soon, it's with my local carrier).
Arne, is there something different with the FW updater code in the new version of the desktop app that could be causing the issue?