You need to be a member of diydrones to add comments!
This reply was deleted.
Activity
RT @breadcentric: The handy bit about racing with self-driving cars is that one can type while the car is racing.
Report from #AWSDeepRacer…
RT @chr1sa: Our Bay Area @DIYRobocars meetup is now at 2,700 members.
Next in-person events (in Oakland) are training day on July 17 and…
Videos from the ICRA autonomous racing workshop are now available: https://linklab-uva.github.io/icra-autonomous-racing/
RT @SmallpixelCar: Prepared race track for Warm Spring Raceways @wsraceways and looking forward to test my new car at RAMS RC @ramsaicar fa…
RT @f1tenth: Trying out some nasty blocking maneuvers 🏎️🤖 #f1tenth #autonomousracing https://t.co/nMTstsaogM
RT @araffin2: I will talk this Saturday from 18:00 to 19:00 Paris time for the @diyrobocars community about learning to race in hours using…
RT @a1k0n: Luckily the infeasible hairpin problem was easily reproducible in simulation and I could test the fix before bringing the car ba…
RT @a1k0n: Another problem was that I was over-constraining the car's allowed accelerations, so it didn't think it could turn as tight as i…
RT @a1k0n: Breaking the map up into two halves worked, but I had to be more careful about separating the inner track from outer. There's se…
RT @a1k0n: Here's a datalog for my fastest lap of the day. Lap timer is tiny window lower-left. https://t.co/myrlWWrKUY
RT @a1k0n: Here was my car's POV. Man this track is confusing in first-person! After the incident my camera was all scuffed up and I was af…
RT @circuitlaunch: Loved seeing so many familiar (masked) faces at Circuit Launch today for our first in person @diyrobocars in over a year…
RT @circuitlaunch: Last but not least, mystery guest @BostonDynamics Spot took to the track @diyrobocars He enjoyed the #brazilianbbq too 😂…
RT @SmallpixelCar: Today’s race @circuitlaunch for @diyrobocars with @a1k0n Was busy in the morning and did not get a chance to tune camera…
Replies
Hi! Where do you find the ICSP port?
Hello again! I know this is an old issue. But I am dealing with it now! Any final info on it?
I know this is an old issue. But I am dealing with it now! Any final info on it?
I know this is an old issue. But I am dealing with it now! Any final info on it?
Name your issue.
Hi Marcin! Thanks for the speedy responce. On one radio I cannot get the firmware to upload without it stopping in mid upload.. Then giving me alert that there is a sync proplem.
The second radio is stuck in bootloader mode ( strong red light ) and won't be recognized by either MP or 3dr config. It connects as a device in Windows xp but won't respond to commands. I got a weak red light when connected with a usb cable. I got a strong red light when connected to FTDI device..
I just got the first one above to give me a green blinking light while connected to a FTDI usb device that I just tried using for the first time. It is the HK multi wii FTDI device..
All was going smoothly.. Then wham. Out of blue I got these problems. Been a learning experience.
Shortening the CTS pin did not help either new message is can not identify radio...
Well I guess I could try a faster PC and see if that gets around the timeout issue.
Other than that I am stuck with a piece of electronic that lights up red when you plug it in.
3DR tech support got back to me this morning:
It is a known problem with the Mission Planer
They recommend to try the 3DR Radio Configurator from here:
http://vps.oborne.me/3drradioconfig.zip
But I get the same results .... sync is lost during the firmware upload.
Does anybody else have this issue or a solution?