I just start with a project utilizing ardupilot quadcopters. I cannot utilize the terminal function in mission planner to do sonar tests. After I assembled the sensor, connect the apm board to mission planner and click 'connect' under terminal tab, the terminal window shows as following:
3691164950?profile=original
I didn't input anything after connect and the screen just pops up with random codes.
I use the latest v3.3 quadcopter firmware.
Another thing is that I could not monitor sonar range after I assembled the standard Max XL- EZL0 MB1240 analog sonar. In the optional hardware initialization process I see this:
3691165202?profile=originalI could not click enable for this version of firmware. I could not test sonar built-in in terminal either
Here's the latest work I've tried to fix the problem:
I downgrade the firmware to V3.01. Test sonar works in terminal for this version of firmware, but in the optional hardware initialization process I still could not click enable, nor selecting sonar type. In status bar of flight data, I always see 0 and 0 for sonar range and sonar voltage (for both versions of firmware). The sonar sensor is intact (I monitored the voltage change on Pin 3 of the sonar using oscilloscope)
If anyone who have encountered similar problem please leave a message. Thank you so much!
Minjie

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • I have the same problem after download new firmware v3.2. Runing MP 1.3.16 i will try to clear the EEPROM and start again from the beggining

    • I also had the same problem, the sonar was working .After I changed the param settings as detailed below
      http://copter.ardupilot.com/wiki/common-optional-hardware/common-ra...
      I am now getting the sonar ranging in mission planner flight data which look quite accurate, however the enable sonar is still greyed out and the copter doesn't seem to respond to obstacles. There is a post on the 3dr forum saying now fixed but fails to explain how. Typical Knuckle dragger.

      • Yes, I also get the sonar reading by changing the corresponding parameters in parameter list.

        So far I am using pixhawk controller, with lidar sensor for distance measurement. This combination works very well.

  • I have the same problem, I don't find the solution. 

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @donkey_car: Human-scale Donkey Car! Hope this makes it to a @diyrobocars race https://www.youtube.com/watch?v=ZMaf031U8jg
Jun 25
DIY Robocars via Twitter
Jun 25
DIY Robocars via Twitter
Jun 16
DIY Robocars via Twitter
RT @GrantEMoe: I won my first @diyrobocars @donkey_car virtual race! Many thanks to @chr1sa @EllerbachMaxime @tawnkramer and everyone who m…
Jun 13
DIY Robocars via Twitter
RT @gclue_akira: JetRacerで自動走行したコースを、InstantNeRFで再構築。データセットは別々に収集 #jetracer #instantNeRT https://t.co/T8zjg3MFyO
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: SPC 3.0 Now the motor also works. This car is doable. I just need to design a deck to mount my compute and sensors. http…
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: My new car SPC 3.0. https://t.co/CKtkZOxeNQ
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: High speed at @diyrobocars thanks @EdwardM26321707 for sharing the video https://t.co/o4317Y2U1S
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: Today at @RAMS_RC_Club for @diyrobocars. Used @emlid RTK GPS and @adafruit @BoschGlobal IMU. Lap time 28s https://t.co/R…
May 28
DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
More…