asdf5329 / brushless-gimbal Goto Github PK

What steps will reproduce the problem?
1. Trying to update to new firmware ( BruGi_049B_r161 )
2.
3.

When error shows up this is highlighted in script: {"accTimeConstant",  INT16, 
&config.accTimeConstant,  &initIMU},

What version of the product are you using? On what operating system?

I have the RC Timer Brushless Gimbal Controller using it with Windows 7. 

Please provide any additional information below.

Some assistance on how to get around this problem so I am able to connect to 
the GUI and start programming my gimbal controller. 

Hi,

 Just assembled one and can't manage to upload the code. 
Using USBasp v2.
What version bootloader should I use? Arduino seems uploading it OK, but then I 
go for firmware seems that USB doesn't do Reset then needed or so.
Any ideas?
Can you please provide step by step flashing guide? 
What fuses should be set?
Thanks!

What steps will reproduce the problem?
1. Turn on controller, have the gyros calibrate
2. move the gimbal around for 10-15 seconds


What is the expected output? What do you see instead?

the zero position changes on the gimbal. The roll and pitch position seem to 
drift away from 0

What version of the product are you using? On what operating system?

r61, on windows 7

What steps will reproduce the problem?
1. Save settings to file
2. Change settings, save, save to eeprom
3. Load settings from file

What is the expected output? What do you see instead?
Expect that settings are written to file and restored correctly.  Settings are 
not restored correctly.

What version of the product are you using? On what operating system?
049 r161. Win7x64. I have not seen this work to date.

Please provide any additional information below.

What steps will reproduce the problem?
1. Setting -90 on RC-min and 45 on RC-max
2. Turning RC pitch from min to max and recentering knob to the middle 
position. 

What is the expected output?
The camera returns to the correct level position.
Proper silent and smooth motor movement.

What do you see instead?
the camera returns to the middle position between the RC-min and RC-max.
So about 22,5° facing down.
The motors produce a continuous background "noise" with glitches and moves 
sometimes with small shots. I think that it's not a wrong PID setting, because 
I have tried all possible values...

What version of the product are you using?
Martinez V3 board.
BETA Version 049 r61 incl. GUI (GUI is not up-to-date).

On what operating system?
Windows 7 - 64.

What steps will reproduce the problem?
1. Pitch the gimbal towards the floor and pitch points above horizon a few 
degrees
2. Ptich the gimbal towards the sky and the camera points below the horizon
3.

What is the expected output? What do you see instead?
I see the Chart function showing values that I would expect it to correct for.  
When I pitch the entire gimbal towards the floor (exercising the pitch function 
about 45 degrees) I get numbers on the chart of -7.00 then it starts to settle 
back down slowly to about 2..

When I point the gimbal down 45 degrees the chart function shows about 10 
degrees and does not really correct for it.

What version of the product are you using? On what operating system?
version 48

Please provide any additional information below.
I am using a 3s lipo with flight  14 pole GBM3508 motors.
My settings are as follows
Iacc=0.1
P=15.0
D=2.0
Poles=14
max PWM=100
Rcmin -45
Rcmax 45

applied wiki syntax to this page

What steps will reproduce the problem?
1. Tilting camera more than 60 degrees down
2. Pitching the frame +/- 60 degrees

What is the expected output? 

The expected output is 90 degree view down with gimbal working as normal

What do you see instead?

As soon as the IMU passes 60 degrees the roll axis jitters and the camera 
looses stabilization and horizon


What version of the product are you using? 

048 

On what operating system?

Windows 7 Ultra 

Please provide any additional information below.

What steps will reproduce the problem?
1. Use any value other than 0 for MPU LPF


What is the expected output? What do you see instead?

I have constant noise introduced into my system from the motors by what seems 
to be perpetual updating or noise from the loop.  This introduces the tiniest 
vibrations (if you can call them vibrations).  It is not a constant frequency 
vibration, but more like adjustments of noise from the MPU.  I would expect the 
system to find a point where it detects level, and stop adjustments.  
Using a filter on the MPU, I would expect this noise to be "smoothed out" so 
that the system would not be so fast to adjust minor numbers.  When increasing 
the MPU LPF to any number but 0, the gimbal begins to randomly jump around on x 
and y axis.  It gets worse as the numbers increase.  Around 3, the gimbal is 
making completely random movements up to 45 degrees on each axis.  It is 
uncontrollable. 
I realize the feature is "experimental", and I request that this feature gain 
more importance.  I feel it is a valuable feature that can isolate the system 
from other vibration interference as well as smooth out noise in the system.
Thank you!

What version of the product are you using? On what operating system?
r169
Win7 x64

Please provide any additional information below.
Witespy Martinez v3
RCTimer 2212 on roll
iPpower GBM2208 on pitch
GoPro Hero2

What steps will reproduce the problem?
1. Flash new FW BruGi? v50 r207
2. Connect 3s LiPo battery
3. After initialization motors start to twitching

What is the expected output? What do you see instead?
I thought, after flash new firmware, that after initialization proces my 
brushless gimbal start to work properly. But instead the motors start to 
twitching horribly.

What version of the product are you using? On what operating system?
BGC firmware: BruGi v50 r207, Windows 8.1

Please provide any additional information below.

PS: Sorry for my english :)

What steps will reproduce the problem?
1. trying to "save to file"
2. trying to "load from file"
3.

What is the expected output? What do you see instead?
expected to have it save to a folder on desktop
instead got a error message popup

What version of the product are you using? On what operating system?
Brugi_50_r202
win7

had the same issue with r200 but not r198 or earlier...

Downloaded and flashed board and tried running the GUI. Won't connect. I 
understand the GUI has not been updated but unusable as it stands. Will wait 
for GUI update.

It just a question.

Motor 1 channel have some voltage,  even all PID & PWN% are 0.
I tried so many firmware version, also the same.
motor 2 channel is fine and I can configure correctly.
But I have no idea what should I do.
I using black color board which is writing brushlessgimbal.de(I think is same 
as 
 martinez baord). And I am very sure that hardware setup/balancing/ and cable connection 
 are correct. I tried almost 3 days. 
I am very appreciate if someone know this issue and advise how to solve this 
problem.

What steps will reproduce the problem?
1. Read home page for this source code, which says "This is an OPEN SOURCE 
Project. Commercial Use of this Project has to be arranged with us in advance. 
With Downloading our Software and/or Hardware files, you accept this 
condition." 

2. Read first sentence of last paragraph of section 10 of the GPL V3, which 
says "You may not impose any further restrictions on the exercise of the rights 
granted or affirmed under this License."

3. Realize that the home page contains a clause which violates section 10.

What is the expected output? What do you see instead?
That the software distribution not violate the terms of the GPL.

What version of the product are you using? On what operating system?
Applies to any.

Please provide any additional information below.
Of particular interest is Section 7, the first paragraph under the numbered 
list, which says "All other non-permissive additional terms are considered 
“further restrictions” within the meaning of section 10. If the Program as 
you received it, or any part of it, contains a notice stating that it is 
governed by this License along with a term that is a further restriction, you 
may remove that term."

So trying to apply an extra restriction to the distribution of this source 
under the GPL is a violation of the GPL, and the GPL itself allows anyone who 
receives it to redistribute the source without that restriction, which means 
they can ignore it by distributing it to themselves without that restriction.

Adding that restriction to the distribution may also mean the GPL isn't 
enforceable, but you'd have to ask a lawyer about that. It certainly violates 
the spirit of the GPL.

What steps will reproduce the problem?
1. Open BLG tool
2. Connect 
3. activate scope by pressing button "Activate Waveform View"

What is the expected output? What do you see instead?
Works as implemented - this is no bug

What version of the product are you using? On what operating system?
BruGi_050_r207, Windows 7

Please provide any additional information below.
The scope shows only the accelerometer sensor signal values. I had a problem 
with an IMU, the accelerometer worked fine but the gimbal was impossible to 
tune. I had to connect the sensor to a MultiWii flight controller to find out 
that the gyro was malfunctioning. As the gyro signal display was not 
implemented in the BLG tool I was not able to detect the source of the problem. 
I guess the implementation would not be too complex, so here is my suggestion:
- Extend the "Waveform" frame  
- Add two checkboxes in the extended frame, one "Acceleration" and one 
"Gyroscope".
Use case 1 - no checbox activated, pressing the button "Activate Waveform View" 
no signal is displayed
Use case 2 - checkbox "Gyroscope" activated, pressing the button "Activate 
Waveform View" displays the gyro signal for Pitch and for Roll
Use case 3 - checkbox "Acceleration" activated, pressing the button "Activate 
Waveform View" displays the acceleration signal for Pitch and for Roll 
Use case 4 - both checkboxes active, pressing the button "Activate Waveform 
View" displays all four signals for accelaration Pitch/Roll and gyroscope 
Pitch/Roll

Items used...
SPECS...
Martinez v3 Board (FPV Community)
Firmware 48
RCTimer Gimbal
2212 Motors
Yes, the sensor is UPSIDE DOWN. (Seeing I am on v48)
GoPro Hero2
All Balanced without power

Settings Screenshot attached.


What steps will reproduce the problem?
1. Set Board to use A1 Pitch with the radio
2. Power up systems and Radio
3. Pitch the gimbal down say 45 degrees
4. Pick up gimbal and hold at level and rotate left and right with your hips to 
make a curve.


What is the expected output? What do you see instead?

Would expect gimbal to stay level even when tilted down.  Gimbal instead ROLLS 
out of level.  

If you have the pitch at level, no issue.  It gets worse the more it is pitched.


What version of the product are you using? On what operating system?

version .48.


Please provide any additional information below.

The issue is if you TILT down to look down even a little, you can no longer do 
a level yaw (rotate) with the coptor. When the gimbal is tiled down and you 
rotate the gimbal tries to adjust for the rotation and seeing it is at an angle 
looking down, it then totally move off level. 

Maybe one of the programmers needs to account for this as it might not have 
been thought of.
----------------

I have played with this a few hours this morning and can find no way to correct 
for this issue. 

You can see this issue if you have your board hooked into the board to be able 
to tilt the camera down to look down some. You do not even need to go far. So 
tilt it down, pick up the coptor, and just rotate back and fourth with your 
hips keeping the level. You will see the gimbal will ROLL out of level with 
each back and fourth movement. 

If you move the coptor side to side with your arms, not using your hips, it 
stays level. Moving your hips gives it an arc like if you were turning the 
coptor using yaw. So if you use your yaw to keep something in the shot as you 
move around it, you will go right off level. (It does NOT happen if you have 
the gimbal level and not tilted down.)

You can see the issue in this video when trying to video a 350Z Roadster.  You 
will note it goes out of level when you try to yaw (rotate) the quadcoptor.

http://youtu.be/WBE70aZ3Fpw

Here's an Idea

Up to now there is not much of a wiki on here, after building a gimball myself 
and (still) having trouble tuning it I think It would be good to update/create 
a wiki and PID tuning guide.

Should include:

- information on making the conections corectly For the hardware.
- How to upload the firmware via Arduino
- How to Open and use the GUI
- Basic Settings and a PID tuning guide.

Anything else?

I know this may seem like basic stuff but it is all helpfull to the people who 
are unsure. I know that having a source of info would of made it a lot easyer 
for me!

I am willing to Write the content and add photos ect.... What I need is more 
info On pid tuning and basic settings. And the ok from the developers to write 
a wiki. :)

[email protected]

What steps will reproduce the problem?
1. Version 0.49 r69 firmware
2. Martinez brushless gimbal control board


What is the expected output? What do you see instead?

GUI should be able to read values but instead it gets stuck at PAR:Reading 
Values or something along those lines.

The board can no longer have firmware uploaded to it by arduino, gets the error 
"avrdude: stk500_getsync(): not in sync: resp=0x00"


What version of the product are you using? On what operating system?

Windows 7, 64bit, with driver fix (here 
http://www.rcgroups.com/forums/showthread.php?t=1872416)

Firmware version 0.49 r69


Please provide any additional information below.

Was working fine on 0.49 r45, uploaded to 0.49 r69 without problem, but shortly 
after the board would no longer communicate with the GUI.

Many others are having this issue as well (see posts on these last couple of 
pages http://www.rcgroups.com/forums/showthread.php?t=1829058&page=149)

Work fine with default settings (5 min. setup including firmware upload), RC 
pitch and roll now working fine too. EXCELLENT!
But i cannot find new 049 GUI in package I use old 048 for settings.

video of new firmware (no post stabilization!):
http://youtu.be/kkYhTtRc0Jc


Thank's Master! :)

In 049r179 I can change the rc-channel in ppm-mode with the GUI-tool (v49r178) 
to channel number 9 for pitch and it works very well. After saving to flash an 
restart the gimbal the channel number is set to 3.
I made a downgrade to Version v49r174 and the PPM-mode with rc-channel number 9 
works.

Updated software and using BruGi 49B-r77.
When I open the brushless gimbal tool no ports are found to connect to the 
arduino.
I'm running a mac.
Any help? Thanks

What steps will reproduce the problem?
1. Operating Pitch 

What is the expected output? What do you see instead?
-No matter what Gain I put the Pitch control in GUI 48 it stays at a slow pitch 
speed. 
-Prior to updating r45 firmware Pitch Gain was fully adjustable using GUI 48.