I just got my PlayUAVOSD, did the first connect to the config tool and told me to update the firmware. It was doing its thing but apparently it didn't finish successfully. I am not getting a blinking orange light on D4 and cannot longer connect to the config tool. What to do?
No result found
Hi, seems your issue is similar to this topic?
Mostly it is caused by the USB, especially with the laptop. The current is low in the USB cable which causes bad communication. You may try another USB cable(the cable with android mobile phone) or change to a desktop PC. A powered USB hub would be useful if you are using laptop.
Ok...good...I'm not the only one.
http://fpvlab.com/forums/showt ... 42828
Exactly same thing just happened to me.
Upgraded to latest firmware, and that's it.
Comm port still recognized.
But the OSD app no longer talks to it.
The link you posted above, it seems to be only for users not able to connect to the config tool initially.
The problem specified here, is directly related to the latest firmware update.
So that means, it initially connect just fine.
If the led blink quickly, it means the board is running bootloader. So it not bricked yet:-). I could not reproduce this issue on my PC and laptop with latest CT and firmware. I put the V220.127.116.11 CT and corresponding firmware into a zip file. Please try this Config Tool to see if it works.
"But sure that ONLY playuav is connected (and not pixhawk/apm) during this process." as macfly1202 suggested.
I tried the zip file you provided, but it had the same result.
1) Everything is disconnected from the unit.
2) I plug in the USB cable. Red light is on steady. The Orange light is blinking fast.
3) Comm port in Windows device manager shows "PX4 FMU (COM19)"
4) In the Config tool I select port "COM19).
5) If I click on "Read Params" result = "operation failed!" popup window.
6) If I click on "Firmware Update" result = "Error opening com port" popup window.
I tried this on different comm ports and on different PCs. Same result.
Also the fact that the red light is not blinking, as you specified, suggests in not in boot loader mode?
additionally if I power it up normally with Video to LCD.
Its just a blank screen. (grey/white)
Have you tried another USB cable? If LED D4 blinks quickly, it means that the board is still running bootloader. Maybe the OSD app is broken or not on the board. If the LED D3 blinks like heartbeat, it means the board is running OSD firmware. Anyway, we can upload the OSD firmware to the board as long as we have bootloader.
Hi, is it still not working with the latest CT and Firmware? I have checked the codes, there is nothing special for the firmware update compared with the previous version.
You can try updating the firmware using "Load the custom Firmware...". The latest firmware download here
I have tried everything with no success. Last error that I got was "The semaphore timeout has expired"
I've never see that error message.
At what point does it come up?
Did you check my procedure on FPVLAB?
And you used config tool v18.104.22.168 from Tom's zip?
yes I did follow your procedure from FPVLAB. It started erasing, and then uploading then I got that error.
Does the uploading progress bar complete to 100%? Please make sure there is no other device especially pixhawk connect to PC when you setup PlayuavOSD board.
BTW, I have searched the whole project and could find the error message "The semaphore timeout has expired" you mentioned. A screenshot would be helpful.
that errors seems to be related to the usb port. No is doesn't complete to 100%.
attached is a screenshot. For a pc which drivers do we need installed? I tried with a Windows 7 and it doesn't load the correct driver for the board.
Where is the config tool located on your PC?
Try to move the entire Config Tool directory to the C: drive, root.
The error you are getting could be related to path names that are too long.
The files being on a USB or network folder (that are having reading issues).
Or folder permissions issue.
Also when you run the "OSD_Config.exe" file, right-click on it first and "choose run as administrator"
Remove any external plugged in USB devices besides PlayOSD (mouse you an keep).
Specially if you have a Bluetooth dongle, or wifi dongle. Unplug them for now.
Also temporarily disable any internal Bluetooth devices.
(you can do this with your Fuctions keys on. The FKeys should have a RadioTower pic, you can use to disable. Eg F2, F10. You have to check yours, there is no standard.
I would even go as far as unplugging and LAN cables and turning off WIFI.
Just to eliminate those items for this test
Anyway...it seems what you are experiencing is an internal Windows error.
ANd PlayUAV is just passing on the description through Windows API libraries.
Hope that helps.
good news.. doing it from a Windows 7 physical machine rather than a virtual machine worked. I am up and running again. Thanks for all the help!