-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to start mission : vehicle not ready #11986
Comments
Sir I have these components
1.pixhawk
2.gps module
3.power management board
4.lipo battery
5. One ESC
6.one brush less motor
7. Q ground control software
I don't have these comments
1.s.bus transmitter and receiver
2.telemetry system
3. Air speed sensor
Wiring connection:
throttle pin is given IO port 4 pin
Right elevator is given IO port 2 pin
Left elevator is given IO port 1pin
Frame : FIXED FLYING WING
I followed these steps
1.upload firmware
2.frame selected ( generic flying wing)
3.calibrate all sensors but air speed sensor is not calibrate so using
circuit breaker disabled this
4.power calibration completed
5 safety calibrated
I do not have a receiver and transmitter so I can run in autopilot so
COM_RC_IN_MODE was desiabled.then after you say it NAV_RC_ACT is set 0 .
Am using USB cable for connectivity computer to pixhawk so that one also
disabled using circuit breaker.
Then after you say battery checks also disabled by using circuit breaker.
Then after I given a mission plane and upload it then show the one message
is start the mission.then after I start the mission getting one more
message is unable to start mission .vehicle not ready .please resolve my
problem sir. please help me sir
…On Wed, May 8, 2019, 12:57 PM Julian Oes ***@***.***> wrote:
Closed #11986 <#11986>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11986 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AL6WXQY64N4IT46Y2Z7GPBLPUJ6E3ANCNFSM4HLPBJNQ>
.
On Wed, May 8, 2019, 12:57 PM Julian Oes ***@***.***> wrote:
Closed #11986 <#11986>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11986 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AL6WXQY64N4IT46Y2Z7GPBLPUJ6E3ANCNFSM4HLPBJNQ>
.
|
sir please help me . why not given to me reply tell me sir
On Wed, May 8, 2019 at 5:05 PM Sampath kumar Chiruthoti <
[email protected]> wrote:
… Sir I have these components
1.pixhawk
2.gps module
3.power management board
4.lipo battery
5. One ESC
6.one brush less motor
7. Q ground control software
I don't have these comments
1.s.bus transmitter and receiver
2.telemetry system
3. Air speed sensor
Wiring connection:
throttle pin is given IO port 4 pin
Right elevator is given IO port 2 pin
Left elevator is given IO port 1pin
Frame : FIXED FLYING WING
I followed these steps
1.upload firmware
2.frame selected ( generic flying wing)
3.calibrate all sensors but air speed sensor is not calibrate so using
circuit breaker disabled this
4.power calibration completed
5 safety calibrated
I do not have a receiver and transmitter so I can run in autopilot so
COM_RC_IN_MODE was desiabled.then after you say it NAV_RC_ACT is set 0 .
Am using USB cable for connectivity computer to pixhawk so that one also
disabled using circuit breaker.
Then after you say battery checks also disabled by using circuit breaker.
Then after I given a mission plane and upload it then show the one message
is start the mission.then after I start the mission getting one more
message is unable to start mission .vehicle not ready .please resolve my
problem sir. please help me sir
On Wed, May 8, 2019, 12:57 PM Julian Oes ***@***.***> wrote:
> Closed #11986 <#11986>.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#11986 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AL6WXQY64N4IT46Y2Z7GPBLPUJ6E3ANCNFSM4HLPBJNQ>
> .
>
On Wed, May 8, 2019, 12:57 PM Julian Oes ***@***.***> wrote:
> Closed #11986 <#11986>.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#11986 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AL6WXQY64N4IT46Y2Z7GPBLPUJ6E3ANCNFSM4HLPBJNQ>
> .
>
|
The issue was closed because this is a place for bug reports and feature requests - is not a place for you to post support requests. You have correctly created a discussion board post. Additional information and questions should go in that post. |
Thank you for your response, but where is the discussion this issue iam
post for it
…On Fri, May 10, 2019, 4:00 AM Hamish Willee ***@***.***> wrote:
@sampathkumarch <https://github.com/sampathkumarch>
why not given to me reply tell me sir
The issue was closed because this is a place for bug reports and feature
requests - is not a place for you to post support requests. You have
correctly created a discussion board issue. Additional information and
questions should go in that issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11986 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AL6WXQ2GZZNKQCZXF35U6ETPUSQXBANCNFSM4HLPBJNQ>
.
|
Pardon? In your top post #11986 (comment) - see https://discuss.px4.io/t/unable-to-start-mission-vehicle-not-ready/10896 |
If that isn't your post, then please create a new one. We can't help you in the defect tracker. |
Ok sir .what do I do now?
…On Fri, May 10, 2019, 8:18 AM Hamish Willee ***@***.***> wrote:
If that isn't your post, then please create a new one. We can't help you
in the defect tracker.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11986 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AL6WXQY4WK6J5R33NKGRVTTPUTPAFANCNFSM4HLPBJNQ>
.
|
Ok sir, what I do now
On Fri, May 10, 2019, 8:31 AM Sampath kumar Chiruthoti <
[email protected]> wrote:
… Ok sir .what do I do now?
On Fri, May 10, 2019, 8:18 AM Hamish Willee ***@***.***>
wrote:
> If that isn't your post, then please create a new one. We can't help you
> in the defect tracker.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#11986 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AL6WXQY4WK6J5R33NKGRVTTPUTPAFANCNFSM4HLPBJNQ>
> .
>
|
Create a post in https://discuss.px4.io with all the details of your setup - vehicle, flight controller, autopilot, autopilot version, ground station, what you have tried. Everything you can think of that might be relevant to the problem. |
The information you have put in this issue looks good, but it can't be posted here, because this is for bugs, and at the moment all we know is that you have a problem. That might be due to your setup or something else. |
https://discuss.px4.io/t/unable-to-start-mission-vehicle-not-ready/10896
The text was updated successfully, but these errors were encountered: