|
Post by riton39 on Jan 9, 2015 9:39:15 GMT
non ça marche pas.la trace revient et écris par dessus.
|
|
|
Post by vicpopo on Jan 9, 2015 12:11:28 GMT
Clique sur off 1cm avant la fin de la fenetre ou au milieu pour voir si cela marche
|
|
|
Post by riton39 on Jan 9, 2015 16:18:58 GMT
to increment P, starting from a position on the cam position already, and P is increased until oscillation.
Before your soft Fabi, I indicated P, for example, 20 to start, then starting from the center position of the cam, I pressed on CMA button to move in the up position the cam.
the engine was off to the far position and function of P, I rode or not Fr.
I wonder if this approach is more effective in the setting?
shown overshoot and oscillation right? also it seems to me that the result is more repeatable.
a move too close to the target seems more complicated to give an oscillation.
In any case, this is what I see on my simulator.
I add that the couple base speed is difficult our engine in general.
|
|
|
Post by riton39 on Jan 9, 2015 17:09:05 GMT
thank you Fabi, the button to lower the P value will probably help.
I did some tests and a video to show what happens using the buttons up and down the cam of the engine; it will help to understand what I was saying earlier. it loads ...
Maybe you could put on one page, manual tuning and autotuning?
put the cam up and down during the autonuning seems interesting that you think.
you will see what happens on my video: it loads ...
|
|
|
Post by riton39 on Jan 9, 2015 18:47:21 GMT
|
|
|
Post by vicpopo on Jan 9, 2015 19:06:47 GMT
Hi Fabi,
Tested the 1.0.0.8 .
- I had one more time an overshooten problem ! Let me explain when I made once a auto tune process , no problem exept sometimes one motor kiks hard ( about 10° angle , that means from far a bigger value that the increment step) ! I decided to make an another try without leaving the app .The same arm kick problem ( increment 200 ms , 5 Hz thick = 1 ) and when the platform oscillated I stoped to increase P and when I clicked on the stop plateform button ,the platform gone up full speed! No damage .
One more detail : before to stop the oscilloscope to measure oscillations I clicked on the off button in oscilloscope window and after i was using the cursors.Now the oscilloscope is stoped when clicking stop plateform on the auto tune window.I would prefer the previous option ;-)
I found an another PID values which seems to be ok 37 122 1
That's all folks
|
|
|
Post by vicpopo on Jan 9, 2015 19:55:00 GMT
Riton , J'ai nregardé ta vidéo .Dans le processus auto tune normalement la plateforme monte .Toi le compteur de position reste sur 32 767 , pour moi ce n'est pas normal !
|
|
|
Post by riton39 on Jan 9, 2015 20:21:15 GMT
si c'est normal, je suis volontairement allé dans manuel , pour faire monter et descendre la came avec les bouton jump vers le haut et jump vers le bas. je voulais mettre en vidéo le fait que ca donne des résultat différent quand tu attaque le P par des passages a grande vitesse partant du centre.
je pense que le réglage du P par incrémentation continu est plus délicate... on vois bien ce que ça fait.
il y a du coup une sacré variante entre 30 et 45 .la came bouge pas forcément si tu part de la position ceentrale en montant doucement. alors que si tu part du haut vers le centre , là le P est plus sollicité, tu arrives a pleine vitesse, il y a la charge et l'inertie , la c'est le réel.
if this is normal, I voluntarily went to manual for raising and lowering the cam with the jump button to jump up and down. I wanted to video the fact that it gives a different result when you attack the P by passages at high speed from the center.
I think the setting of continuous increment P is trickier ... we can see how it feels.
there is suddenly a big variation between 30 and 45. cam not move necessarily, if you share the central position amount softly. whereas if you share the top to the center, where P is applied, you get to full speed, there is the load and inertia, it is real.
|
|
|
Post by fabi on Jan 11, 2015 6:27:53 GMT
Don't understand exactly: Are you saying at a certain P value, one motor starts to oscillate much earlier than the other motors are doing? If so, could it be that this motor needs more mecanical forces than the others? Maybe turn on the logging "Log Send to Thanos Board" to see what happens. Behind the stop button I have only the AZ command... If com2.IsOpen Then
com2.Write("AZ")
If Log_SendThanos_isOpen Then
Log_SendThanos.write("AZ" & vbCrLf)
End If
End If tronicgr Should I send another command? Opps.. you mean the results in the oscilloscope are gone when clicking the stop button?
|
|
|
Post by tronicgr on Jan 11, 2015 6:33:30 GMT
fabiWell, if you sent the AZ command, it will place the controller to off-line mode. If you have small motor speed for off-line mode, it should stop the vibrations, but it does not stop completely the motion. Perhaps I'll add another command that kills the motor signals kinda like what KLM switch does but in software. Then have it stay "killed" until another command activates again the motor signals. I'll try to get that done tomorrow (playing with the RFduino wireless at the moment). Thanks Thanos
|
|
|
Post by vicpopo on Jan 11, 2015 15:41:18 GMT
Fabi ,
Yes at some moment when increasing P one motor kick ( don't remember which direction if on the same as up) .You can see clearly the feedback sensor on the oscilloscope with big peak! Ok for the test click on log send to thanos board
No I don't say that the oscilloscope traces gone with the stop,button in auto tune window.I said that before to measure the oscillations when auto tune finished I was clicking on the off button in the scope window to made tha the trace still. With the 1.0.0.8 that hadn't worked to proceed like this .I achieved to stop the traces on scope not clicking like described like before but only by clicking in the auto tune window to the stop plateform.
|
|
|
Post by stevant on Mar 5, 2015 17:09:24 GMT
Hey Fabi,
Just wanted you to know that Thanos help me get things going with your software and it is awesome. It's great making changes right from my screen and the Auto-tune works great. Thanks so much as it has made our projects that much more user friendly!!!
Sincerely,
Steve
|
|
|
Post by callenger on May 6, 2015 13:55:31 GMT
Hi Fabi, Your App looks very good, but won't work correct with my 6dof flightsimulator. If i evaluate the current position of the platform, the app shows a center position while the platform stays in the lower parking position. When i klick jump to mid she moves slowly to the mid and returns instantly down to parking pos. Same effect with the max heave position and also with the manual control. I think the platform has to stay in the selected position and the evaluation function has to find the actual position of the 6 axes. What's wrong here? Regards from Bern Rolf
|
|
|
Post by tronicgr on May 6, 2015 14:36:05 GMT
Hi Fabi, Your App looks very good, but won't work correct with my 6dof flightsimulator. If i evaluate the current position of the platform, the app shows a center position while the platform stays in the lower parking position. When i klick jump to mid she moves slowly to the mid and returns instantly down to parking pos. Same effect with the max heave position and also with the manual control. I think the platform has to stay in the selected position and the evaluation function has to find the actual position of the 6 axes. What's wrong here? Regards from Bern Rolf Hi Rolf Set the kill switch function to number 2... Otherwise it may timeout and try to park the motors. Thanks Thanos
|
|
|
Post by callenger on May 6, 2015 19:34:37 GMT
Hi Thanos, Do you mean the KLM switch? Don't helps. Some times with manual control mode and pressing the "up" button the platform goes up and stays, but only one time. Next move the platform goes again to park position. The other curious thing ist the current position evaluating function that shows always 32400 instead of 16000, where the park position is. Some idea? Regards Rolf
|
|