|
|
Post by riton39 on Jan 8, 2015 16:40:56 GMT
oops, sorry I made a mistake in the test was P 0, then any movement.
I indicated P = 10 for manual testing.
but ...
I click "Evaluate heave position", it works. with 1 .... 65535
Then I tested up, down, Works.
then I go to Auto Tuning.
I have to redo the position, and there, Idem the bargrapher increased by 1 cm and stop ...
|
|
|
|
Post by riton39 on Jan 8, 2015 17:08:15 GMT
as I have allowed only one validation, I crafty!
I starts the app
I go on com6 (I have the feeling that from time to time there is a port detection problem ...)
Then I'll check the engine 2 because I have no potentiometer.
then I go directly Autotuning, I agree, it passes.
Then I start the process, the position value moves,
I increment P, but then as before, nothing moves, I went up to 100, the motor not move ..
PC test with Windows XP
i test with 1 .....65535 for the values
Only one motor , one potentiometer
|
|
|
|
Post by tronicgr on Jan 8, 2015 18:59:12 GMT
Then I start the process, the position value moves, I increment P, but then as before, nothing moves, I went up to 100, the motor not move .. Increments of one value won't move the motor much, it might take a few minutes to move a few mm.. If you want you can increase the increments to 10... That will make a more noticeable motion or trigger the motor faster to oscillate. Thanks Thanos |
|
|
|
Post by tronicgr on Jan 8, 2015 19:22:05 GMT
I managed to get great values for my mini linear actuator that I have for testing on my bench (10m/s speed!!!). It works like charm! Thanks fabi ! I'll be adding more resolution in the PID for floating point calculations and larger values for Integral and fixed point for Derivative as I see the need from the tool. I'll let you know how that goes. Thanks! Thanos |
|
|
|
Post by fabi on Jan 8, 2015 19:53:33 GMT
Have you tested 1.0.0.7 ? Good to know... I will be on travel for a week without coding access.... Awesome! Thx |
|
|
|
Post by riton39 on Jan 8, 2015 20:07:35 GMT
the app says it communicates with the card, I increment P, but P remains at 0 on the card.
what it happening.
I look atp on the card the P is 0.
that's why the motor is not moving.
I am unable to identify the problem.
what is certain is that I can click only one time set the position.
I think then it cuts off communication with the card ...
either quend I click a second time.
or so when I increment P, this does not make it on the map, the app says it communicates P increases, but the engine not move ....
|
|
|
|
Post by riton39 on Jan 8, 2015 20:07:47 GMT
I charge you 2 videos ...
to be sure that it works I have to reboot the card, start the app, and I am entitled to a validation luck.
I can start the process, the software increments P, but nothing in the card, it remains at 0. |
|
|
|
Post by riton39 on Jan 8, 2015 20:07:58 GMT
|
|
|
|
Post by riton39 on Jan 8, 2015 21:27:47 GMT
|
|
|
|
Post by tronicgr on Jan 9, 2015 1:42:48 GMT
Hmm... can you enable the feedback from the AMC1280USB? Also in the configuration check if you can change the PID from the sliders...
Some setting is not right... share a screenshot of the controller config tab...
|
|
|
|
Post by tronicgr on Jan 9, 2015 6:05:58 GMT
riton39Here is a screenshot of the settings I have on the "controller Config" tab:  fabiI can verify, there is a bug that it does not increase the P in the autotuning when the DOF is less that 6DOF. However, after I run the PID autotune once in 6DOF setting, it works if I switch it to 2DOF. There is a bug there in the logic. It always work if its used in 6DOF for now. Another bug: the "Print sensor feedback from the board" is switching back to mode 1 (no feedback) eevery time I stop the motion while in autotune. I would suggest to force it to mode 2 when the Comport of the AMC1280USB is selected, and then switch it back to mode 1 before closing the program, but not save it if it was already in Mode 1 in the AMC1280USB settings (no need to repeatedly stress the epprom with unnecessary saving). That's what I found so far, among the other improvements I suggested over PM. I know you are going to be away for a few days. Take your time for that. We'll have to use the workaround for now (suggested config values above). Thanks Thanos
|
|
|
|
Post by riton39 on Jan 9, 2015 7:51:10 GMT
here is my configuration before, when it not work
I did the same setting on your screenshot, it works apparently.
I have to continue testing.
I bring you my findings
I still had a strange thing, I have to restart the AMC, the app showed anything, not all good values.
how is being done to stop the scrolling of the trace of the oscilloscope to measure?
I can not find how to stop scrolling ...
|
|
|
|
Post by riton39 on Jan 9, 2015 8:06:23 GMT
there should be a decrease button P.
for example, I go up to 50, it does not move, I go to 51 .... 80ca moves a lot.
I would need to go down to see if it is 80 it starts to move.
after several attempts, as the case it moves to 50 times and it does not move, or it moves to 60 ....
after testing it does not always do the same thing.
I feel that both the engine and move times or less.
you have to turn goshawks movement and value to confirm the oscillation.
may be the speed is not sufficient to cause an oscillation in each case?
my minimum frequency on my drive is 2.5 Hz, not 0, but 2.5Hz
otherwise I would not have enough starting torque.
it's the same thing if speed is not enough e torque is too low to create a swing each time the same. |
|
|
|
Post by riton39 on Jan 9, 2015 8:09:44 GMT
un bouton pour adapter la vitesse serait intéressant , et un bouton pour diminuer P aussi ?
Edit: is when we actually stop the oscilloscope stop too. my cam does not move and I have spikes on the oscilloscope ...what is it?
I think the speed is not enough for me to properly trigger the oscillations.
suddenly as I said it would be able to increase the base speed, and also to reduce return P if the oscillation that will trigger unexpectedly, it triggers it, then stops ...
|
|
|
|
Post by vicpopo on Jan 9, 2015 9:32:54 GMT
how is being done to stop the scrolling of the trace of the oscilloscope to measure? I can not find how to stop scrolling Appuie sur off sur l'oscilloscope quand la trace arrive à droite à la fin de la fenêtre ! |
|
