Hello,
I would like to ask you to share what would be the optmal procedure for setting up PIDs. Right now I am trying to make 'road tests' of ArduPiot with the latest software (dated 22.09 I believe).
My setup is simplified a lil:
1. ArduPilot
2. ESC on OUT1
3. GPS(EM411 or MTK)
4. Servo TowerPro SG90 on OUT2 for rudder visualisation.

After I switch the battery the rudder servo travels clockwise till it cannot rotate anymore (I am working with 3rd servo now - two was eaten by Ardu ;)). While I drove the car sometimes there are small servo rotations but they are barely visible.

I have changed servo max/min position as follows:
#define max16_yaw 1800 //Servo max position
#define min16_yaw 1200 //Servo min position
It didnt give me any visible result.

What should I change next? Please help

Views: 122

Reply to This

Replies to This Discussion

Michal, I think you've got some problems you need to sort out before you turn to PID gains. Nobody else has reported that servo rotation issue, so if you're using the latest version of the code I think there's something wrong with your board. Can you check the voltage on the board and confirm that you're running ~5v?
Chris, yes I can confirm that all out-pins (vcc-ground and servo pins) have 5.09V. Maybe there shoud be some other points to measure? Forgive my ignorance...
Do the servos work properly in manual mode? (MUX off)
I got back to initial PID settings. Theres something wrong. There are two servos - one connected to Rx another to OUT2 Ardu. Here is the video what has happened during tests.



As you can see the first time both servos were working properly. After fist MUX switch second (Ardu) servo got mad...
It looks like the servo connect to the Rx is also moving sometimes after you switched the MUX. Is that correct, or were you moving that manually?
Yes I switched to/from MUX in 13,16,24,30,55,59,1:32,1:39,1:51 second. Every other switch was due to some strange behaviour/interference. The first servo stayed normal at that time.
Do I see the mux led flickering when it should be on or off solid?
Rusty

Yes, his LEDs suggest that he's got something wired wrong or hasn't cleared the Attiny fuse correctly. The above video shows what the correct behavior should be. (if you turn the volume up you can hear the narration)
I am trying to verify that I have propery flashed Attiny45. One error occurs inside AVRStudio while trying to flash Attiny45:
"ISP frequency must be 5 kHz or above when programming EEPROM or FLASH!". I folowed this tutorial. What have I done wrong?
What frequency have you set it at? 250khz is a good starting point.

Please read this tutorial for more.
OK I reflashed with Jan 26, 2009 Fail_Safe_v15.zip (hex file created from the code in AVRStudio). Tripple checked for the fuses. Nothing changed - at the beginning manual mode works fine, after the first switch to auto OUT2 servo gets mad and looks like MUX diode is switched on and off with high frequency.
Here is my setup:


I dont have any clue now...
Please confirm the following:

--CKDIV8 fuses are unchecked in both Attiny and Atmega
--Board is running at >4.7v when measured at the servo ports and the VCC and GND next to the FTDI port.
--Atmega is running the current ArduPilot code
--This behavior is also seen when the GPS is connected and locked (blue led on)

If all that is true, I'd then like to know if the MUX light flashes even when there are no servos attached.

RSS

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The third round was a reliablilty/aerial photography round for both planes and copters, which is now closed. Stay tuned for the next round, beginning soon.

A list of all T3 contests is here

 

© 2012   Created by Chris Anderson.

Badges  |  Report an Issue  |  Terms of Service