You need to be a member of diydrones to add comments!
This reply was deleted.
Activity
RT @Heavy02011: @diyrobocars : A Home-brew computer club* for Connected Autonomous Driving on Jan 23rd, 2021 https://www.meetup.com/Connected-Autonomous-Driving/events/275728684/ #Meetu…
RT @Heavy02011: @diyrobocars Autonomous Driving Assembly at #rC3. join us at https://rc3.world/rc3/assembly/diyrobocars-f1tenth/ @f1tenth @DAVGtech @DWalmroth…
RT @chr1sa: New car designs coming for our next @DIYRobocars @donkey_car virtual race on the 23rd. Choose any one you want at race time
Le…
RT @RoboticMasters: Thanks to @EllerbachMaxime and the Sydney Uni Capstone Students the @donkey_car @diyrobocars simulator is getting a ma…
An interesting line-following simulator to use with with your robocars:
https://github.com/ron-grant/LFS
An improved version of the @IntelAIResearch OpenBot:
https://diyrobocars.com/2020/12/14/an-improved-version-of-the-intel-openbot/
Replies
Hi
Another way to solve the problem is to upload the code(049) to apm with Arduino. It works for me for both hexa and quad.
Best regards
Arnt-Inge
There is a report in the Issue Tracker of a small bug with changing PIDs via MAVlink in the latest version when your CLI switch is in Flight Mode. You can change them with the switch in CLI mode in the meantime until the bug is fixed. Thanks to Olivier Adler for the catch/fix.
I have the exact same problem. Are you using xbee?
I had this the other day, I changed the USB cable and the problem went away.