Thread Tools
Mar 22, 2016, 06:08 PM
Registered User
Thread OP
Question

Throttle stick is not working but others do


Hi,

I'm working with:
- Board Multiwii 328p
- Radiolink AT10
- Receiver R10D

I have configured config.h:
#define QUADX
#define MINTHROTTLE 1150
#define MAXTHROTTLE 1850
#define MINCOMMAND 900
#define I2C_SPEED 400000L
#define FREEIMUv035_BMP
#define ALLOW_ARM_DISARM_VIA_TX_YAW

After binding the radiolinks at10 with my receiver I have connected via USB my labtop with the board and in MultiWiiConf I can see how stitches YAW, PITCH and ROLL work perfectly but the THROTTLE one remains static at 1500.

I have switched the wire from pin1 with the one in pin3 and this test has certified that my radiolink throttle stitch work perfectly.

Any help will be welcome!
Sign up now
to remove ads between posts
Mar 22, 2016, 09:03 PM
Registered User
Do you need to define the mid throttle as well?

Worth a try as I am still new to all this!
Mar 23, 2016, 07:47 AM
Team AlienWarpSquad
None of the #defines you posted is the problem.

Moving the RX throttle output to a different WMC input is a GOOD test and proves the TX/RX works.

So the problem is the connection to the MWC. So either you have the wrong pin or this pin is disabled or bad for some reason.

Do you have the correct Board??
#define FREEIMUv035_BMP

Post link to the EXACT board if you want verification.

Also picture of your board with RX connections.
Mar 23, 2016, 05:15 PM
Registered User
Thread OP
Hi,

I have tried connecting the throttel stitch (channel 3) in radiolink at10 and receiver R10D to pin 1 (throttle) and does not work. Later I have tried to connect it to pin 3 (pitch) and the throttle stitch have moved perfectly. Hence the RX/TX looks correct.

Thanks a lot for your assistance!
Mar 23, 2016, 08:06 PM
Registered User
Channel mapping order correct? ie TAER1234 or whatever...
Mar 24, 2016, 07:19 AM
Team AlienWarpSquad
Quote:
Originally Posted by Ari33
Channel mapping order correct? ie TAER1234 or whatever...
The OP is using MultiWii NOT CF and does NOT have Channel MAP.

Still same guess:

Do you have the correct Board??
#define FREEIMUv035_BMP


Post a LINK to the MWC board you actually have.
Mar 24, 2016, 02:12 PM
Registered User
Thread OP
Hi,

My board is Board Multiwii 328p you can find here:

https://www.hobbyking.com/hobbyking/s...Comp_Port.html

I have tried with
#define FREEIMUv035_BMP
and
#define HK_MultiWii_328P

And throttle does not work in both configurations.

Regarding to order:
Roll: channel 1
Pitch: channel 2
Throttle: channel 3
Yaw: channel 4

Thanks a lot,
Mar 24, 2016, 02:19 PM
Registered User
Thread OP
Hi,

My board is the following:
https://www.hobbyking.com/hobbyking/s...Comp_Port.html

I have tried both with:
#define FREEIMUv035_BMP
and
#define HK_MultiWii_328P

And throttle stitch does not work in both configurations.

Regarding the mapping order:

Roll: channel 1
Pitch: channel 2
Throttle: channel 3
Yaw: channel 4

Thanks a lot.
Mar 24, 2016, 05:05 PM
Registered User
Quote:
Originally Posted by waltr
The OP is using MultiWii NOT CF and does NOT have Channel MAP.
I see, ok, thanks Waltr... please excuse my relative newbness!

Mar 24, 2016, 08:12 PM
Team AlienWarpSquad
Quote:
Originally Posted by osegarra
Hi,

My board is the following:
https://www.hobbyking.com/hobbyking/s...Comp_Port.html

I have tried both with:
#define FREEIMUv035_BMP
and
#define HK_MultiWii_328P

And throttle stitch does not work in both configurations.

Regarding the mapping order:

Roll: channel 1
Pitch: channel 2
Throttle: channel 3
Yaw: channel 4

Thanks a lot.
According the the config.h in the "Files" on HK's product page you should use #define HK_MultiWii_328P
You did find these and opened/read each one, right?
https://www.hobbyking.com/hobbyking/s...Comp_Port.html

Did you try a different RX channel into the throttle pin (THR) of the MWC?
If this doesn't work then it is possible you have a board with a bad processor pin or soldering.
You can try examining the processor's pins to see if they are properly soldered or return it for refund or exchange.


Quick Reply
Message:

Thread Tools