Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - nickkinsman

Pages: [1]
1
Hello, this is follow up to older thread on HLFB feedback from clearpath servos, which have inverted logic for their fault drivers (HLFB) to what the PMDX 126 needs.  Was there any firm solution to this problem? 


Thanks. 

2
Hello;

I've recently upgraded servo's on my mill to Clearpath SDSK.  I am wondering how to get an outputs enable signal to the clearpath from the PMDX 126?  The clearpath needs 5 to 24VDC to enable the outputs.  I tried connecting to the 'outputs enabled' LED connection on the 126 but it doesn't have enough to drive the clearpath.  I don't know where there is another place to get an outputs enabled signal off the BOB?

Right now I've got it working by simply connecting the clearpath input to the 12V unreg on the board, so it enables when the BOB comes online, but I would like it to be driven by the chargepump signal so it will shut off on estop, not just by board power. 

Any ideas?
Thanks.

FYI, in case anyone needs the info, I used a 3-block opto-isolated relay bank to invert the fault signal from the clearpath to drive the fault circuit on the 126 (since they work in inverted function). It works great.  I used 12VDC relays powered off the 12V unregulated on the BOB, but you could use 5V off the board too.

3
Hello;

I have an odd problem with my setup and I wanted to see if the problem might be in the BOB or speed control.

First of all I want to mention that I am continually impressed with the excellent design and setup, especially the good labelling and on-board diagnostic of the PMDX products.  I was having trouble with a servo and I was easily able to check the pulse train was making it through the board just by looking at the 'step' LED.

I have Mach3 to an Smoothstepper ESS, with PMDX 126 RevA board, 107 spindle control using with a 0-10V VFD, 108 for additional inputs, and PMDX 171 for spindle speed feedback.  I have gotten pretty much all of it working with very little problems.  My question is around the spindle start command;

I have to issue the start command twice for the spindle to startup.  A  normal S1000 M3 command shows the delay LED on Mach kicking in, but the spindle does not start up.  only when I issue a command like this does it startup:

M3
S1000 M3

It does the same thing in MDI or even on the program run page, I have to click the 'spindle' button, then type in the speed and hit enter before it will start (even if the speed is already set in the DRO).
This doesn't seem likely to be a hardware problem but thought I would check.  What seems odd is Mach appears to be putting out the start command, as the LED's start flashing indicating the delay is taking effect.

Thanks
Nick

Pages: [1]