Set up using AMC AB15A100 drives, brushed DC motor Prototrak Plus with Encoders

More
24 Aug 2022 17:49 - 24 Aug 2022 18:21 #250337 by new2linux
Todd, thanks! I have closely review (to the diagram a few posts earlier) my connections & tighten a few connections on temps & others, on P1 (the A-M-C drive) there is no wire from pin 2 to pin 11. Should there be? I see both have "GND" in the name (pin 11=GND vs. Signal GND=pin2).
As I start at the "terminal" screen, type in "~/linuxcnc/configs/test/test.demo" I can see the LED on the drives go from red to green, but no motor vibration on ether motor. Attached is pic of test.hal file. I hope to try the o-scope on the "y" axes.

Many thanks
Edit: I am ok with not testing the "y" axes, if the "x" axes data is accurate enough to set both drives to the best trace from the .zip file.
Many thanks
 
Attachments:
Last edit: 24 Aug 2022 18:21 by new2linux.

Please Log in or Create an account to join the conversation.

More
24 Aug 2022 18:41 #250339 by Todd Zuercher
There should be no wire connecting pins 2 and 11 on the AMC drive. But if you check the continuity between them I believe you will find that they are connected within the drive.

Just for the sake of experiment try setting up the test.hal file like this.
This will connect both drives to the same siggen signal at the same time. So you will need to have both of the motors detached and clamped down.
loadrt threads name1=fast fp1=0 period1=250000 name2=slow period2=1000000

loadrt siggen
loadrt hostmot2
loadrt hm2_pci config=" num_encoders=6 num_pwmgens=0 num_stepgens=5 sserial_port_0=00000x"
setp    hm2_5i25.0.watchdog.timeout_ns 5000000

#loadusr test.ui gladevcp ./test.ui

addf siggen.0.update    slow
addf hm2_5i25.0.read    slow
addf hm2_5i25.0.write    slow

net enable <= test.enable => hm2_5i25.0.7i77.0.1.analogena

net output <= siggen.0.square
net output => hm2_5i25.0.7i77.0.1.analogout0
net output => hm2_5i25.0.7i77.0.1.analogout1

net freq <= test.frequency-f => siggen.0.frequency
net amp    <= test.amplitude-f => siggen.0.amplitude
net offset <= test.offset-f => siggen.0.offset

start

loadusr halscope

It could also be possible that the settings in the y-axis drive are such that it's response is imperceptible to you.
The following user(s) said Thank You: new2linux

Please Log in or Create an account to join the conversation.

More
24 Aug 2022 18:44 #250340 by Todd Zuercher
You did remember to set all of the switches on Y drive to what they need to be for current mode to do the test?
The following user(s) said Thank You: new2linux

Please Log in or Create an account to join the conversation.

More
24 Aug 2022 19:19 - 24 Aug 2022 19:21 #250344 by new2linux
Todd, Thanks! I deleted everything in the "test.hal" file; copy & past your text from the prior post, saved & rebooted. At "terminal" key in:"~/linuxcnc/configs/test/test.demo", press return and I get the HAL Oscilloscope & siggen test screen, all looks good. I press the "enable servo drive" and the "x" axes motor vibrates, but not the "y" axes.
I look at the HAL Oscilloscope screen, at the bottom at "selected channel" the 1channel is "siggen 0 square" channel 2 is "hm2_5i25.0.7i77.0.1analogout1" should I include ""hm2_5i25.0.7i77.0.1analogout0"??

I do not have 2nd motor clamp yet, but working on it. The motors do not vibrate wildly, just a medium buzz sound.

Many thanks

Edit: Yes, all the dip settings are the same on both drives.
Last edit: 24 Aug 2022 19:21 by new2linux.

Please Log in or Create an account to join the conversation.

More
24 Aug 2022 19:26 - 24 Aug 2022 19:36 #250345 by new2linux
Todd, if I swap motor & encoder on the outside of cabinet the other motor (the "y" axes) will vibrate, but both motors do not vibrate at the same time, the LEDs on drives change from red to green.
Many thanks!

Edit: Is the workaround to swap the "x" axes motor and drive with the "y" axes? Making shore to keep the drive and motor as a set.
Last edit: 24 Aug 2022 19:36 by new2linux.

Please Log in or Create an account to join the conversation.

More
24 Aug 2022 21:14 #250350 by Todd Zuercher
The only thing left to do is to verify if the signal is or isn't being sent to the drive with the real oscilloscope. Either there is something wrong with the 7i77 that it isn't sending the analog signal, or there is something wrong with the drive that it isn't doing anything with it. (Either a switch or pot setting is wrong or the drive is broken.)

The analog and enable wires from each drive are they plugged in right beside each other in the TB5 row? (grasping at straws here.)
The following user(s) said Thank You: new2linux

Please Log in or Create an account to join the conversation.

More
25 Aug 2022 13:27 - 25 Aug 2022 13:58 #250398 by new2linux
Todd, thank you for your help. As you have suggested it appears the drive has an issue, I reset Pot 2 (11 turns), verified all of the switch settings, traded A-M-C drive with each other, and the "y" motor vibrated (very 1st time). The LEDs change from red to green when in "terminal" screen, the command is keyed in. I have been ever so careful.

Thanks

Edit: I should reach out to A-M-C and see if I can make arrangements to have this drive repaired??
Last edit: 25 Aug 2022 13:58 by new2linux.

Please Log in or Create an account to join the conversation.

More
25 Aug 2022 15:08 - 25 Aug 2022 15:54 #250408 by new2linux
Todd, The very best news, I adjusted Pot 1 & 3 to mid-point like pot 4. Now both motors vibrate, I needed to loosen the clamp (I need to make 2nd clamp) on the 1 motor to make shore it was moving/vibrating. I am not shore what pot needed 7 CW.
Many thanks.

Edit: Now the both motors vibrate can we use all 4 probes on 2 motors, if I make a set of "temps" to connect probe& gnd to? Should I adjust both drives to the mid point on Pot 1 & 3?

Many thanks
Last edit: 25 Aug 2022 15:54 by new2linux.

Please Log in or Create an account to join the conversation.

More
25 Aug 2022 18:01 #250425 by new2linux
Todd, Thanks! Attached is a .zip file of all "y" traces, the file name is the setting with 2 exceptions. The file names go like this DS1Z_QuickPrint(what ever the number is, is the SW3 "setting") exception: DS1Z_QuickPrint5=50(SW3) but has the 4th channel in the trace, so file DS1Z_QuickPrint33 is the same settings w/o the 4 channel in the trace, SW3 chart value=50. So when you read the files names, they are in order, all same units, only 1 do over (file 5 & file 33, are the same). The chart starts with 20 (as default), this is the 1st file saved & chart value 10 is the 2nd file, (these 2 file names are the opposite of the chart settings read) I have not pondered these yet, I am so glad this has worked!! Please offer your thoughts.

Many thanks!!!

 
Attachments:

Please Log in or Create an account to join the conversation.

More
25 Aug 2022 19:53 #250442 by Todd Zuercher
Looks very similar to what you found for the X-axis. (No surprises there.) I am inclined to say to set it to 120 or 130. It is a little difficult to tell for sure though because those traces just happen to have that stray bump in the analog output show up in just the wrong place to interfere with seeing if there is any overshoot. What ever setting you settle on, I'd suggest using the same setting for both drives. (Velocity tuning is less likely to be the same for both.)

Please Log in or Create an account to join the conversation.

Moderators: piasdom
Time to create page: 0.202 seconds
Powered by Kunena Forum