Autonomous Arming of UGV

I'm making a UGV using arduino and pixhawk. I want it to arm with the help of a range finder's readings. I'm actually going to air drop the UGV to a particular point and then as soon as it hits the ground, the rangefinder will give a particular reading, using which I want the UGV to get armed and then execute the mission according to the planned path.
It'd be really helpful if I can get a code for the same.

Drop the jargon, and explain in simple terms what you want to do, with what you want to do it.

So basically I want a code which would take the readings of range finder (Distance sensor) as an input and then run the arming program (to arm the motors ) and push that code to pixhawk (controller) and then pixhawk would be having the path already written on it , with the help of which the ugv would further continue with the plan.
Hope it's clearer now.

Glossary
UGV: Uncrewed Ground Vehicle
Pixhawk : open source flight controller system

2 Likes

Thanks for the info.

And tell the forum how much of the code you have written so far.

Not exactly jargon-free, is it?

What code?
Push how?

The one that takes readings from an unnamed range finder?

Assume we know nothing of the exotic things you talk about, you would probably be close to right.

Can you arm and make the pickaxe do what you want with just a digital signal?

Can you produce a digital signal from the range finder (and code if needed) that means “time to fly” or whatever?

In other words, can you divide your project into two pieces with only a simple digital logic signal between them?

Get the two separate parts working, then… you are done.

Have you written anything for the range finder or used any example code that you might have found for it?

This sounds trivially simple, what am I missing?

Besides the make and model of the range finder, that is.

Oh, and welcome to the community.

a7

T̶h̶e̶ ̶w̶o̶r̶d̶ ̶"̶a̶r̶m̶"̶ ̶i̶s̶ ̶n̶o̶t̶ ̶a̶p̶p̶r̶o̶p̶r̶i̶a̶t̶e̶ ̶i̶n̶ ̶t̶h̶i̶s̶ ̶c̶o̶n̶t̶e̶x̶t̶.̶ ̶E̶n̶a̶b̶l̶e̶ ̶o̶r̶ ̶a̶c̶t̶i̶v̶a̶t̶e̶ ̶i̶s̶ ̶m̶o̶r̶e̶ ̶c̶o̶r̶r̶e̶c̶t̶ ̶t̶o̶ ̶a̶ ̶d̶r̶o̶n̶e̶ ̶c̶o̶m̶p̶l̶e̶t̶i̶n̶g̶ ̶a̶ ̶m̶i̶s̶s̶i̶o̶n̶.̶ ̶W̶h̶e̶r̶e̶a̶s̶ ̶a̶r̶m̶ ̶i̶m̶p̶l̶i̶e̶s̶ ̶a̶ ̶w̶e̶a̶p̶o̶n̶ ̶o̶f̶ ̶s̶o̶m̶e̶ ̶t̶y̶p̶e̶.̶ ̶W̶e̶a̶p̶o̶n̶s̶ ̶b̶e̶i̶n̶g̶ ̶a̶ ̶t̶o̶p̶i̶c̶ ̶t̶h̶a̶t̶ ̶i̶s̶ ̶n̶o̶t̶ ̶l̶i̶k̶e̶l̶y̶ ̶t̶o̶ ̶g̶a̶r̶n̶e̶r̶ ̶a̶ ̶l̶o̶t̶ ̶o̶f̶ ̶h̶e̶l̶p̶ ̶h̶e̶r̶e̶,̶ ̶i̶m̶o̶.̶

Context. The word “arm” in r/c world means to enable the motors to spin.

In some flight modes, arming immediately makes the propellers spin.

In no flight mode does a disarmed vehicle spin any motors.

There are specific and deliberate impediments to ending up with a wild snarling beast of a vehicle, a quadcopter, for example.

If your throttle is up, a quadcopter will not arm. It will not arm until the throttle is down AND you ask it again to do.

It might not arm if it is at a disadvantageous angle WRT horizontal.

It might not arm for who knows why, which would explain the 10^6 hits you get googling “my quadcopter won’t arm”. :expressionless:

Despite the safety features, ppl still manage to damage themselves, we all have stories.

I might look different had not a battery connector failed and stopped the show that was about to be put on…

I should not miss this opportunity to say never work on anything with the propellers installed, unless the tests depend on having propellers attached.

a7

1 Like

Struck from the record. Thanks you for the info.

Might that be zero? Just curious!

Which Distance sensor are you using? Can you tell us a bit more on how you plan to send code to the Pixhawk (means which interface will you use)?

I don't think anyone could give you the code, we may help you to find & resolve out errors in your own program or help you find the correct libraries and tutorials to follow (the internet is filled with lots of garbage tutorials, trust me).

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.