More VSD-e questions

[scrambled]

Tero-

I am still trying to figure out how to disable all drives when a fault ocures. According to the VSDEPI manual- the VSDEPI should do this automatically

Quote--
Lacking charge-pump signal, fault on any drive or hitting
E-Stop button will
○ Disable all drives
○ Disable relays
○ Inform control software by setting logic 0 status to D-Sub
pin 10 (fault or E-stop condition signaled to PC)

Is this correct?

If so, I could use the relay contacts to send a signal to the CandCNC BOB that a fault has ocurred.

Yes I installed the config file for the VSDEPI in each drive


Steve

[Xerxes]

Steve,

VSDEPI won't actually disable drives alone. CNC software (Mach3) will disable them if you configure it according to VSDEPI manual. So you may try it without additional BOB to see if it works as intended.

Unfortunately I have no experience on CandCNC BOB.

[scrambled]

Tero-

I am still having a problem understanding how the VSDEPI works, and how to configure it.

This from the online manual


Location in Figure 1 Description
1 (USB-B) USB connector for 5V power input (USB-B connector type)
2 (PARALLEL) 25 pin male D-Sub connector for control input/output signals
3 (ESTOP) E-Stop switch input terminal. Normally open switch may be connected to this input.
4 (RELAY) Relay terminal. Up to 10A 250VAC load can be powered through this connector.
5 (EXT_RELAY) External relay output. 5 Volt relay coils of external relay can be connected to thisconnector.
6 (JP1) Charge pump setting jumper. Charge pump feature is disabled when jumper is inserted.
7 (X_CMD) X axis drive output. Direct 16 pin flat ribbon cable connection to VSD-E or VSD-XE.
8 (Y_CMD) Y axis drive output. Direct 16 pin flat ribbon cable connection to VSD-E or VSD-XE.
9 (Z_CMD) Z axis drive output. Direct 16 pin flat ribbon cable connection to VSD-E or VSD-XE.
10 (A_CMD) A axis drive output. Direct 16 pin flat ribbon cable connection to VSD-E or VSD-XE.

Parallel port pin Function
1 Charge pump input (feed 10-30 kHz frequency to this input or insert jumper JP1 to disable this
feature)
2 X axis direction
3 X axis step (rising edge)
4 Y axis direction
5 Y axis step (rising edge)
6 Z axis direction
7 Z axis step (rising edge)
8 A axis direction
9 A axis step (rising edge)
10 Drive fault & E-stop input to PC (active low). Also low when charge pump signal was not
detected while JP1 is open.
11 X home switch to PC. Routed from VSD encoder connector, connect actual switch to VSD-E/XE
home switch input.
12 Y home switch to PC. Routed from VSD encoder connector, connect actual switch to VSD-E/XE
home switch input.
13 Z home switch to PC. Routed from VSD encoder connector, connect actual switch to VSD-E/XE
home switch input.
14 Drive enable from PC (drives active when high, disabled when low)
15 A home switch to PC. Routed from VSD encoder connector, connect actual switch to VSD-E/XE
home switch input.
16 On-board relay control input. Relay on when high.
17 External relay control input. Relay on when high.
18-25 Ground




----Where is the physical locations of Opto-in 3 and 4 on the VSDEPI that is used in GDtool

----Where is the physical location of analog in 1 and 2 on the VSDEPI that is used in GDtool

-----Where is the opto-out 1 and 2 on the VSDEPI that is used in GDtool


Can I control the relay that is mounted on the VSDEPI from one/all of the VSD-E’s

Is pin #10 (Drive fault & E-stop input to PC (active low)) all that I need to connect to my other BOB?

Sorry for all the questions, but I have read the manual and still don’t understand.


Steve

[Xerxes]

----Where is the physical locations of Opto-in 3 and 4 on the VSDEPI that is used in GDtool
----Where is the physical location of analog in 1 and 2 on the VSDEPI that is used in GDtool
-----Where is the opto-out 1 and 2 on the VSDEPI that is used in GDtool

Plese see VSD-E manual CMD connector pinout. Pin locations are defined there.

Can I control the relay that is mounted on the VSDEPI from one/all of the VSD-E’s

No. Control of relay from parallel connector only.

Is pin #10 (Drive fault & E-stop input to PC (active low)) all that I need to connect to my other BOB?

Pin number 10 should go some way to PC to tell Mach that one of drives has faulted. No matter if it goes directly or thru another BOB. When Mach sees that pin 10 is active (logic 0), Mach sets logic 0 to pin 14 to disable all drives. Also pin 14 can be passed thru another BOB.

Just make sure that signals go thru from PC to VSDEPI. And if they are inverted by the other BOB, adjust Mach settings accordingly.

Could you post a link to your BOB manual so I could take a look?

[scrambled]

Tero-

I think there is some mis communication going on. I know where the pins are located on the VSD-E, but since I am now using the VSDEPI I am not sure where the location of the pins are.

I checked the voltage to Pin #10 on the VSDEPI (10 Drive fault & E-stop input to PC (active low). and when there is NO fault the voltage from pin #10 to ground (common) is 4.85 vdc. When the drive gets either a following error or a overcurrent fault then the voltage is 4.85 VDC.

I am assuming that I do not have the user I/O set correctly. I did install the config. file for the VSDEPI in all 4 drives.

What else do I need to do?


Steve

[Xerxes]

It sounds like either the drive I/O settings are wrong or the measuerment is done from wrong pins or connector. How exactly did you measure that (voltage probe locations)? Does your voltage reading change if you short ESTOP terminal with wire?

It's enough to have one drive connected to VSDEPI to test the faulting feature. You can also "emulate" fault with ESTOP switch which should disable Mach even when no drives are connected.

[scrambled]

Tero-

Not sure what I was doing yesterday, but today it looks like everything is working as it should.

I get 4.85 volts when everything is not faulted or e-stopped, and I get 0 volts when the machine is e-stopped or it faults.


I am still getting following errors when the machine is traveling in the X and A axis over long distances 5-6 feet at 400-500 ipm.

If I disable the following fault, then it is might not run "True" correct?

Is there a way to prevent the VSD-E drives from moving when they have the folloowing fault cleared? My problem is using 2 servos for 1 axis. If only one drive faults, when the fault is cleared the gantry starts to "Rack". The only way I can prevent this is to power the drives down after a following fault.


Thanks



Steve

[scrambled]

Tero-

I set the following error to "0" and the gantry would not move.


Steve

[Xerxes]

Its no wonder that nothing works if you set following error fault limit to zero. One encoder count deviation will fault the drive.

Please follow my earlier posts to fix the following error.

[Jason3]

Tero, perhaps Steve was under the impression that setting the following error limit to zero would disable the limit?

Best regards,

Jason

[jalessi]

Tero,

What should the settings be?

Please post a image of the correct settings.

How do the settings effect the performance of the servo.

What do the settings actually do?

Jeff...

[Xerxes]

Sorry Steve & folks. I just checked GDtool manual and found out that follow error limit really isn's defined there. We clearly need to revise the manuals.

However, every parameter has a tooltip. It can be seen by hovering mouse over control for a second. Please see the screenshot. Correct value should be adjusted so that motors won't fault in normal operation. It can be also to find out how much following error are you getting during motion (i.e. if you set it to 100 and get fault, you know that following error was greater than 100).

One should elimiate faulting by adjusting PIV or PID gains so that following error is minimized. For some tuning guides, see:

http://support.motioneng.com/Downloa...ng/default.htm
http://granitedevices.datamappi.com/...ing_manual.pdf