Talk:Getting Started: Difference between revisions

From STorM32-BGC Wiki V1
Jump to navigation Jump to search
No edit summary
No edit summary
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Okay, getting closer. But your IMU example does not match mine. I as well have the dot left bottom, I as well look at the camera from the bottom (so that "right" is on the wrong side, but my index no is 15, in your example it is the zero. So either we change the index numbers or we assume the IMU was mounted on top of the camera and the right arrow is pointing to the right.
Oh fu**. Then change the UI back to what it was.


Agreed?
Just kiddin'. I'll update the screenshots and text once it is out.


->
Was about 6 hours of work, not including the break.


I'm not sure I get exactly what you say, but the "old" picture describes a different situation than seen in your setup photo.... in your photo one is looking at the camera FROM BELOW while in the "old" picture one is looking at the camera FROM ABOVE (I guess I said this before ;))... the "right" is correct and no index number needs to be changed, it's just this different perspectives... maybe have a look at Greg's addition to this figure in the rcg thread... I'll provide you with some additional figures


O:
ja, tut mir leid ... aber ich denke dass das neue Tool gut ankommt ... hoffe ich zumindest
ich frage mich auch ob es nicht vielleicht "besser" wäre ein Video zum Gimbal Tool zu machen ... das 6-punkt video macht ja schon vieles schnell klar was vermutliche vieler Worte und Bilder bedurft hätte


Understood but I find it confusing. I would still not be able to relate this picture to my concrete example. What should we do?
== STorM 32-BGC as a hand held brushless gimbal ==


->
Hi,
Not sure what to do. I'll send a new picture with an explicit photo of a camera instead of the blueish scheme, I would hope that this avoids at least missreading it. I have my doubts though that this by itself would simplify relating things or remove any confusion. Ideally you would figure out what it exactly is what makes you confused and makes you not to be able to relate the pictures.


I think the basic problem is that it's not everyone's cup of tea to relate coordinate axes seen from different perspectives. I.e. one photo shows a camera from below, the next from above, the next from the front etc. etc.
I am new to gimbals and online wiki's etc. so I am not sure where to ask questions or for advice. I figured since this page is under the discussion tab that this would be a good place to start.
Here goes nothing, I have been building a hand held brushless gimbal as an action research project for my Btech degree. I based the frame design on the Letus Helix jr. because I thought it is
the most compact and practical design. After facing many problems and overcoming them through trial and error I eventually ended up with a functional hand held gimbal. The only thing that
I am not able to do is hold the gimbal as if it is a suitcase (as seen in this video made by No Film School https://youtu.be/A1Uwr_sLVBs). The closest I have come to making the gimbal work
in this position is by switching off the onboard (second) IMU, which I have mounted to the handle. Therefore I believe that the gimbal does not work when you hold the gimbal in this position
because you are basically swopping the roles of the yaw and pitch motors (the yaw becomes the pitch motor and vice versa) and so the gimbal freaks out because it is not able to comprehend
what is happening.


I could imagine if one would stay within one perspective things might get simpler. In fact, I tried to aid the user into this with the grey axes labeled front, right, up shown in the GUI window. Following up on this I could suggest the following general recipe. Look at your camera from the front, i.e. directly into its lens. Then the meaning of the grey axes and their relation to the camera should be obvious. Now, still looking at your camera from the front, identify in which direction the IMU's z axis points to. It can only be one of six cases: it can point towards you, away from you, to the left, to the right, to the top, or to the bottom. Sounds fairly easy to me. Next, still looking at your camera from the front, do the very same for the x axis. What do you say?


PS: maybe the figure with teh many configurations should be totally removed
I would like to know if this is true? Has the board not been programmed to enable it to switch the two motors (since a quadcopter hardly ever banks at 90 degrees)? Or do I have to update the
firmware (I have firmware version 80)? Or have I just made a rookie mistake by overlooking a setting of some sort that would allow the gimbal to function in this position?




Frankly I find the current method to most easy one.
P.S
The z-axis does grow out of the IMU chip, so where does it point to? It points down in my example.
The x-axis can be seen on the board but is the one pointing in reading direction (from the white dot left to right in the direction of the printed text on the chip), it points forward.
Done.  


Your image I find confusing. How about that change?
I want to thank Olliw and everyone else who have developed this control board and wiki into what it is today. It is a job done excellently!




The last thing I find confusing is where the camera right side is. I would have thought that if I hold the camera in my hand for shooting, the right hand side would be to the right. But be it as it is, at least it is not confusing anymore with all the examples, especially the coordinates (front/right) you have added to my picture.
Hey,
 
first, in principle this discussion page is an appropriate place for discussions, only that essentially no one is using it and is hence very little frequented - as you may see form the number of discussions here ;). From that point of view, the rcgroups thread is a much (much, much) better place. Maybe you want to move with your question (and follow up discussion) over there.
second, the controller can handle a swap of the yaw and pitch motors, in the "standard" yaw-roll-pitch configuration, but the gimbal in the video doesn't have that configuration, and the code isn't made for that.
 
OW
 
Hi Olliw,
 
Thank you for your follow up. I am glad I came to the right place :). I will have a look and see if I can join the rcgroups thread as well though. Ok I understand, when a gimbal with the  standard
configuration (yaw-roll-pitch) is held in that position the yaw and roll motors swop roles but when a gimbal with a pitch-yaw-roll configuration (like the one I have chosen to build) is held in that position
the yaw and pitch motor swop roles. Hmmm that is a pity, maybe writing the code for that could be the next challenge ;).

Latest revision as of 20:46, 30 September 2015

Oh fu**. Then change the UI back to what it was.

Just kiddin'. I'll update the screenshots and text once it is out.

Was about 6 hours of work, not including the break.


O: ja, tut mir leid ... aber ich denke dass das neue Tool gut ankommt ... hoffe ich zumindest ich frage mich auch ob es nicht vielleicht "besser" wäre ein Video zum Gimbal Tool zu machen ... das 6-punkt video macht ja schon vieles schnell klar was vermutliche vieler Worte und Bilder bedurft hätte

STorM 32-BGC as a hand held brushless gimbal

Hi,

I am new to gimbals and online wiki's etc. so I am not sure where to ask questions or for advice. I figured since this page is under the discussion tab that this would be a good place to start. Here goes nothing, I have been building a hand held brushless gimbal as an action research project for my Btech degree. I based the frame design on the Letus Helix jr. because I thought it is the most compact and practical design. After facing many problems and overcoming them through trial and error I eventually ended up with a functional hand held gimbal. The only thing that I am not able to do is hold the gimbal as if it is a suitcase (as seen in this video made by No Film School https://youtu.be/A1Uwr_sLVBs). The closest I have come to making the gimbal work in this position is by switching off the onboard (second) IMU, which I have mounted to the handle. Therefore I believe that the gimbal does not work when you hold the gimbal in this position because you are basically swopping the roles of the yaw and pitch motors (the yaw becomes the pitch motor and vice versa) and so the gimbal freaks out because it is not able to comprehend what is happening.


I would like to know if this is true? Has the board not been programmed to enable it to switch the two motors (since a quadcopter hardly ever banks at 90 degrees)? Or do I have to update the firmware (I have firmware version 80)? Or have I just made a rookie mistake by overlooking a setting of some sort that would allow the gimbal to function in this position?


P.S

I want to thank Olliw and everyone else who have developed this control board and wiki into what it is today. It is a job done excellently!


Hey,

first, in principle this discussion page is an appropriate place for discussions, only that essentially no one is using it and is hence very little frequented - as you may see form the number of discussions here ;). From that point of view, the rcgroups thread is a much (much, much) better place. Maybe you want to move with your question (and follow up discussion) over there. second, the controller can handle a swap of the yaw and pitch motors, in the "standard" yaw-roll-pitch configuration, but the gimbal in the video doesn't have that configuration, and the code isn't made for that.

OW

Hi Olliw,

Thank you for your follow up. I am glad I came to the right place :). I will have a look and see if I can join the rcgroups thread as well though. Ok I understand, when a gimbal with the standard configuration (yaw-roll-pitch) is held in that position the yaw and roll motors swop roles but when a gimbal with a pitch-yaw-roll configuration (like the one I have chosen to build) is held in that position the yaw and pitch motor swop roles. Hmmm that is a pity, maybe writing the code for that could be the next challenge ;).

Retrieved from "http:///storm32bgc-v1-wiki/index.php?title=Talk:Getting_Started&oldid=2762"