Difference between revisions of "Device connection troubleshooting"

[checked revision]

Revision as of 22:35, 4 March 2013

This article helps finding cure for connection problems between PC and drive.

Granity requires following to establish connection:

Compatible RS485 adapter, such as SimpleMotion V2 USB Adapter
SimpleMotion V2 compliant drive, such as Argon
SimpleMotion V2 calbing with termination
Correct bus address setting on all devices in the SM V2 bus, see Setting device bus address

Bus address conflicting between devices (two or more devices set to same address)
Missing bus termination
Device has an error state, see led indicators
Wrong communication interface device selected from Granity

Some most common resons for failing GDtool connection with VSD-E and VSD-XE:

Cable to CMD connector is connected simultaneously when USB adapter is plugged in (CMD connector should be left unconnected while using GDtool to prevent communication interference because these connectors have shared signals)
Wrong software being used for the installed firmware. Use only GDtool for single axis firmware and only DCtool for DualDC firmware. If you accidentally used wrong tool, re-flash the firmware file to reset all drive settings to factory state.
Electromagnetic interference (EMI). If connection breaks when HV voltage is applied to drive (and works fine when only 12V is applied), then it is probably cause by electromagnetic interference. Typical reasons:
- Motor output cable is not shielded and shield not connected to drive FG (frame ground)
- Motor casing (metal) not connected to drife FG via cable shield or earthing connector.
- Interference escaping from power supply leads
- Interference escaping from other nearby equipment such as VFD or welding machine
- EMI suppression cores on motor, power & USB cable may help
Device power-up sequence not properly done during establishing connection
USB adapter may have been damaged. Damage may occur with voltage potential error or when used with CMD cable plugged simultaneously. Also DOA cables have been the reason in rare cases (less than 1%).

More things to try:

Try on another computer
Try on isolated system with only one drive, 12V power supply and a computer. Preferably far from EMI sources.

@@ Line 22: / Line 22: @@
 **[[EMI suppression cores]] on motor, power & USB cable may help
 *Device power-up sequence not properly done during establishing connection
-*USB adapter may have been damaged. Damage may occur with voltage potential error or when used with CMD cable plugged simultaneously. Also DOA cables have been the reason in rare cases (less than 0.5%).
+*USB adapter may have been damaged. Damage may occur with voltage potential error or when used with CMD cable plugged simultaneously. Also DOA cables have been the reason in rare cases (less than 1%).
 More things to try: