5i25 to PMDX-131 Configuration Issues

More
09 Feb 2017 03:33 #87632 by rockabye74
I have been working to configure a Mesa 5i25 connected to a PMDX-131. I have used MesaFlash to install the 5i25_dmmbob1x2.bit file to my 5i25 and I have configured the 5i25 to contain 4 stepgens. The dmesg appears to match my configuration, but I have been unable to get the steppers to move. I am able to turn the spindle on, I have connected a charge pump to pin 17, and have even been able to turn on my flood coolant. I have included the dmesg output below: If anyone has any ideas that may help me I would greatly appreciate it.

[ 3892.998060] hm2: loading Mesa HostMot2 driver version 0.15
[ 3893.003776] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 3893.003869] hm2_pci: discovered 5i25 at 0000:04:00.0
[ 3893.008933] hm2/hm2_5i25.0: 34 I/O Pins used:
[ 3893.008944] hm2/hm2_5i25.0: IO Pin 000 (P3-01): IOPort
[ 3893.008952] hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort
[ 3893.008961] hm2/hm2_5i25.0: IO Pin 002 (P3-02): StepGen #0, pin Direction (Output)
[ 3893.008969] hm2/hm2_5i25.0: IO Pin 003 (P3-15): IOPort
[ 3893.008977] hm2/hm2_5i25.0: IO Pin 004 (P3-03): StepGen #0, pin Step (Output)
[ 3893.008984] hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort
[ 3893.008992] hm2/hm2_5i25.0: IO Pin 006 (P3-04): StepGen #1, pin Direction (Output)
[ 3893.008999] hm2/hm2_5i25.0: IO Pin 007 (P3-17): IOPort
[ 3893.009007] hm2/hm2_5i25.0: IO Pin 008 (P3-05): StepGen #1, pin Step (Output)
[ 3893.009015] hm2/hm2_5i25.0: IO Pin 009 (P3-06): StepGen #2, pin Direction (Output)
[ 3893.009024] hm2/hm2_5i25.0: IO Pin 010 (P3-07): StepGen #2, pin Step (Output)
[ 3893.009032] hm2/hm2_5i25.0: IO Pin 011 (P3-08): StepGen #3, pin Direction (Output)
[ 3893.009041] hm2/hm2_5i25.0: IO Pin 012 (P3-09): StepGen #3, pin Step (Output)
[ 3893.009048] hm2/hm2_5i25.0: IO Pin 013 (P3-10): IOPort
[ 3893.009055] hm2/hm2_5i25.0: IO Pin 014 (P3-11): IOPort
[ 3893.009062] hm2/hm2_5i25.0: IO Pin 015 (P3-12): IOPort
[ 3893.009069] hm2/hm2_5i25.0: IO Pin 016 (P3-13): IOPort


[ 3893.009076] hm2/hm2_5i25.0: IO Pin 017 (P2-01): IOPort
[ 3893.009083] hm2/hm2_5i25.0: IO Pin 018 (P2-14): IOPort
[ 3893.009090] hm2/hm2_5i25.0: IO Pin 019 (P2-02): IOPort
[ 3893.009097] hm2/hm2_5i25.0: IO Pin 020 (P2-15): IOPort
[ 3893.009104] hm2/hm2_5i25.0: IO Pin 021 (P2-03): IOPort
[ 3893.009111] hm2/hm2_5i25.0: IO Pin 022 (P2-16): IOPort
[ 3893.009124] hm2/hm2_5i25.0: IO Pin 023 (P2-04): IOPort
[ 3893.009131] hm2/hm2_5i25.0: IO Pin 024 (P2-17): IOPort
[ 3893.009138] hm2/hm2_5i25.0: IO Pin 025 (P2-05): IOPort
[ 3893.009145] hm2/hm2_5i25.0: IO Pin 026 (P2-06): IOPort
[ 3893.009152] hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort
[ 3893.009158] hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort
[ 3893.009165] hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort
[ 3893.009172] hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort
[ 3893.009179] hm2/hm2_5i25.0: IO Pin 031 (P2-11): IOPort
[ 3893.009186] hm2/hm2_5i25.0: IO Pin 032 (P2-12): IOPort
[ 3893.009193] hm2/hm2_5i25.0: IO Pin 033 (P2-13): IOPort
[ 3893.009484] hm2/hm2_5i25.0: registered
[ 3893.009495] hm2_5i25.0: initialized AnyIO board at 0000:04:00.0
[ 4028.652663] hm2_5i25.0: dropping AnyIO board at 0000:04:00.0
[ 4028.652684] hm2/hm2_5i25.0: unregistered
[ 4028.653829] hm2_pci: driver unloaded
[ 4028.669790] hm2: unloading

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

More
09 Feb 2017 14:02 #87659 by andypugh

I have connected a charge pump to pin 17,


You will have a 500Hz charge-pump running through GPIO. The PMDX docs say that 100Hz is the minimum, so that seems OK.

Can you open a halmeter and check that the value of hm2_5i25.0.stepgen.00.position-cmd is actually changing value when you jog that axis?

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

More
09 Feb 2017 17:39 #87683 by PCW
Also please post your hal/ini files

That would save a lot of guessing

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

More
09 Feb 2017 23:29 #87729 by rockabye74
Please find attached all of the files in my config area.

File Attachment:

File Name: custom.hal
File Size:0 KB

File Attachment:

File Name: custom_gvcp.hal
File Size:0 KB

File Attachment:

File Name: custom_postgui.hal
File Size:0 KB

File Attachment:

File Name: myBridgeport.hal
File Size:12 KB

File Attachment:

File Name: myBridgeport.ini
File Size:4 KB

File Attachment:

File Name: myBridgeport.pncconf
File Size:307 KB

File Attachment:

File Name: postgui_call_list.hal
File Size:0 KB

File Attachment:

File Name: shutdown.hal
File Size:0 KB

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

More
10 Feb 2017 00:04 #87731 by PCW
As a quick guess I think you have your step times too short (500 ns)
for most step motor drives with optocoupler inputs, 2usec (2000 ns) is
probably a better starting point

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

More
10 Feb 2017 00:50 #87735 by rockabye74
OKay, headed out to change it now and test.

I am assuming you mean the steplen in the ini file.

BRB

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

More
10 Feb 2017 01:34 #87736 by rockabye74
I am one happy camper right now. You hit the nail on the head. I started getting fairly reliable movements at around 3000ns, so I set both the steplen and stepspace to 5000ns and then started tuning the velocities and accelerations. Even with the 5000ns values I am running at least twice as fast as I did with the parallel port using Mach3.

You have made my evening. Thank you so much!

Mike

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

More
10 Feb 2017 09:31 #87749 by andypugh

Even with the 5000ns values I am running at least twice as fast as I did with the parallel port using Mach3.


Your scales seem to be 3000 steps per inch. At that scale and at 5000nS step-length you would need to be at 2000 inches/minute before the step length started to be a speed limit.

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

Moderators: cmorley
Time to create page: 0.125 seconds
Powered by Kunena Forum