Replies to This Discussion

DeveloperPermalink Reply by Michael Oborne on January 5, 2013 at 4:12pm

reinstall the device driver in device manager, should fix it

• ▶ Reply

Permalink Reply by MarioLucich on January 6, 2013 at 1:49am

have you tried looking at your restore points in windows. You might be able to get back to a state before things started to go bad for you.

 

Are other things working when plugged into the USB port?

With my xbee I was in a situatuon where I thought that I had burned it off, but thaking it through the re programming I was able to get it to work again.

 

 

Mario

• ▶ Reply

Permalink Reply by chris wilson on January 24, 2013 at 6:16pm

I had this very problem and I did figure it out!!! I've got multiple APM 2.5's they connect on a different comport, one connected ok the other will be seen via the comm port but will not connect... It drove me batty for about a week but I finally licked it... This is what you need to do plug-in the one that will not connect to mission planner go to device manager and go to the ports and you should see it listed.. Right-click it and select update driver I know I'm sure you've done this before and it didn't work but there's one step that needs to be done When it asks for automatically searching for the lower option that says that you will select it pick that one. It will auto populate drivers that Windows believes will work there will be two listed one is digitally signed With the check mark next to it and one is not. Select the driver that is not digitally signed and apply/okay it will give you an error stating it is not digitally signed. ignore it And Bam the problem is fixed as the do with windows grabbing the driver from the Arduino program versus the mission planner program they both have the same name however they are definitely different, I guarantee That is your problem do not let Windows auto select the driver for you or install it automatically manually select the driver it will list two and do not pick the one that is digitally signed If you can't sort this out drop me a p.m. I'll walk you through it

• ▶ Reply

Permalink Reply by E_Luna on January 25, 2013 at 12:29pm

dear chris wilson,

could you pass me the correct driver for the usb 3dr telemetry kit, I went to device manager and did what you suggest but the list of divers is big (around 8 drivers) and I´m not sure which one to choose.

thanks!

Ernest

• ▶ Reply

Permalink Reply by elad o on January 6, 2013 at 2:07am

run safe mode and fix it trough there everything should be fine you could also try to hook it to a different usb port rear for example

next time first driver then device unless you cancel the windows auto driver installation and use your own drivers when plugged in for the first time 

best regards

• ▶ Reply

Permalink Reply by heliboy on January 24, 2013 at 4:16pm

Hi guys. Just got brand new APM2.5. Old one (bought  10/12) runs fine but need to make second drone. Unfortunately MP refuses to connect to the new one ! Same PC connects to old one just fine. Tearing my hair out ! Strangely when I plug the older one into the USB port it shows up as Mega2560 on COM4. But when I plug in the new APM2.5 on the same physical USB port it shows up as Mega2560 but on COM8. Clues ?

 

Thanks, - Vijay

• ▶ Reply

Permalink Reply by Alexsey Novik on January 24, 2013 at 4:42pm

Just change COM port to COM8 in MP. It is dropdown near Connect button.

If it is not shows up then delete Mega in Device Manager, reboot. 

Wait untill it finish with driver installation process, then run MP.

Hope this helps, 

Alex

• ▶ Reply

Permalink Reply by chris wilson on January 24, 2013 at 6:16pm

I had this very problem and I did figure it out!!! I've got multiple APM 2.5's they connect on a different comport, one connected ok the other will be seen via the comm port but will not connect... It drove me batty for about a week but I finally licked it... This is what you need to do plug-in the one that will not connect to mission planner go to device manager and go to the ports and you should see it listed.. Right-click it and select update driver I know I'm sure you've done this before and it didn't work but there's one step that needs to be done When it asks for automatically searching for the lower option that says that you will select it pick that one. It will auto populate drivers that Windows believes will work there will be two listed one is digitally signed With the check mark next to it and one is not. Select the driver that is not digitally signed and apply/okay it will give you an error stating it is not digitally signed. ignore it And Bam the problem is fixed as the do with windows grabbing the driver from the Arduino program versus the mission planner program they both have the same name however they are definitely different, I guarantee That is your problem do not let Windows auto select the driver for you or install it automatically manually select the driver it will list two and do not pick the one that is digitally signed If you can't sort this out drop me a p.m. I'll walk you through it

• ▶ Reply

Permalink Reply by OlivierD. on January 24, 2013 at 4:41pm

I have the same problem, have been pulling my hair over it for some time now. At this point, I have tried eveything under the sun, I can no longer connect my APM via USB. I can only see it when it is powered alone and broadcasting via the 3DR radios.

And since you can`t do a firmware upgrade over the radio, well, I am stuck. I am not happy with this because I wasted a huge amount of time and now the board sits in a box. Going back to the DJI Naza for a while until the bugs get ironed out, it`s just too frustrating. And my minimOSD won`t connect either, probably a corrupt bootloader. Royal pain, not time for this right now. I hope you figure it out and if you do, please post your findings! Good luck.

• ▶ Reply

Permalink Reply by heliboy on January 24, 2013 at 5:07pm

I changed the COM port to 8. Uninstalled, rebooted. POwered off .... MP will not connect to the new APM2.5. !!! I cannot even connect using the 3DR radios. HOWEVER, the older APM2.5 works just fine. Connects with USB or 3DR radios.

Some big issue but 3DRobotics customer support is still pretty non-existent so the only hope is someone smarter than me will figure this out. Anybody else got new APM2.5's in the last few days ? Do they connect ?

- Vijay

 

• ▶ Reply

Permalink Reply by chris wilson on January 24, 2013 at 6:28pm

I battled with this same problem it has to do with windows grabbing a generic Arduino digitally signed driver for the 2560, even though it has the same name it will not work with the APM. Simply go to device manager and right click update the driver but do not let it auto select or automatically find the driver select the lower option Which is you manually telling at which driver to use the next screen should list drivers that are compatible for the APM the top one is a digitally signed want with a checkmark that Windows Picked for you automatically this one does not work even though it recognizes it and doesn't indicate a problem below that should be another driver with the same name that is not digitally signed and does not have a checkmark next to it that is the driver you want selected and apply it it will give you an error stating it is not digitally signed ignore it once you've done that Just reboot and going to mission Paner pick the appropriate comm port from the drop down and bought right and you should be in like Flynn

• ▶ Reply

Permalink Reply by heliboy on January 24, 2013 at 8:37pm

Chris:

Thanks for the response. I have two laptops running Windows 7. I tried your suggestion on both of them but  no luck. Just the same - timeout on connection. The installed driver is dated 11/15/2007 version 5.1.2600.0

My feeling is that this is the FTSI chip driver but the mega does not use the FTSI anymore so it does not work. I cannot find any other driver. Almost feel like throwing the APM in the trash.

- Vijay

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page