Editing Device connection troubleshooting
| Your changes will be displayed to readers once an authorized user accepts them. (help) |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | This article helps finding cure for connection problems between PC and | + | This article helps finding cure for connection problems between PC and drive. |
| − | == | + | ==Granity== |
| − | + | Granity requires following to establish connection: | |
| − | *Compatible RS485 adapter, such as [[SimpleMotion V2 USB | + | *Compatible RS485 adapter, such as [[SimpleMotion V2 USB Adapter]] |
| − | *SimpleMotion V2 compliant drive, such as Argon | + | *SimpleMotion V2 compliant drive, such as Argon |
| − | *SimpleMotion V2 | + | *SimpleMotion V2 calbing with termination |
*Correct bus address setting on all devices in the SM V2 bus, see [[Setting device bus address]] | *Correct bus address setting on all devices in the SM V2 bus, see [[Setting device bus address]] | ||
| − | + | ===Typical errors=== | |
| − | + | *Bus address conflicting between devices (two or more devices set to same address) | |
| − | === | + | *Missing bus termination |
| − | *Bus | + | *Device has an error state, see led indicators |
| − | *Missing | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | *Device has an error state, see | + | |
*Wrong communication interface device selected from Granity | *Wrong communication interface device selected from Granity | ||
| − | + | ==GDtool, DCtool and VSD-E/XE== | |
| − | * | + | 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 [[VSD-E/XE CMD and SPI connectors|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. | ||
| − | + | 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. | ||
