Device connection troubleshooting - Revision history

Esa: /* Common failure reasons */

2017-04-27T11:09:37Z

‎Common failure reasons

Tero K at 15:43, 17 June 2016

2016-06-17T15:43:37Z

Tero K at 15:42, 17 June 2016

2016-06-17T15:42:07Z

Tero K at 15:41, 17 June 2016

2016-06-17T15:41:48Z

Tero K at 15:40, 17 June 2016

2016-06-17T15:40:24Z

Tero K: /* Granity (Argon & Ioni drives) */

2016-03-08T14:45:32Z

‎Granity (Argon & Ioni drives)

Tero K: /* Granity (Argon & Ioni drives) */

2015-07-15T11:59:47Z

‎Granity (Argon & Ioni drives)

Tero K: /* Granity (Argon & Ion drives) */

2015-05-01T13:19:00Z

‎Granity (Argon & Ion drives)

Tero K at 11:41, 15 April 2015

2015-04-15T11:41:01Z

Tero K: undo mistake edit where content was removed

2014-12-29T17:13:46Z

undo mistake edit where content was removed

@@ Line 11: / Line 11: @@
 *Bus [[Setting device bus address|address]] conflicting between devices (two or more devices set to same address)
 *Missing [[Setting device bus address#Bus termination|bus termination]] or too long stub after termination. Correct termination is important especially if RJ45 cable is longer than 3 meters or stub longer than 0.5 meters.
-**With IONICUBE, make sure that bus termination is set on (IONICUBE 4 axis board: insert jumper to JP10 position 1, see image [[IONI & IONICUBE user guide/Making the first Granity connection|here]]) and IONICUBE 1X, set DIP switch S1 position 1 on).
+**With IONICUBE, make sure that bus termination is set on
 *Use of crossover RJ45 cable. If this has been used, it might have caused damage that might prevent communication even with correct cable.
 **For repair instructions of Argon, see [[Determining Argon hardware failure]].

@@ Line 1: / Line 1: @@
-This article helps finding cure for connection problems between PC and drive.
+This article helps finding cure for connection problems between PC and SimpleMotion based drive (ARGON, IONI, ATOMI etc).
-==Granity (Argon, Ioni & Atomi drives)==
+===Requirements for connection===
 [[Granity]] requires following conditions to establish connection:
 *Compatible RS485 adapter, such as [[SimpleMotion V2 USB adapter]]
@@ Line 8: / Line 8: @@
 *Straight (not crossover) RJ45 cable on the devices with RJ45 ports ([[IONICUBE]], [[ARGON]])
-Common failure reasons:
+=== Common failure reasons ===
 *Bus [[Setting device bus address|address]] conflicting between devices (two or more devices set to same address)
 *Missing [[Setting device bus address#Bus termination|bus termination]] or too long stub after termination. Correct termination is important especially if RJ45 cable is longer than 3 meters or stub longer than 0.5 meters.

← Older revision		Revision as of 15:42, 17 June 2016
Line 27:		Line 27:
	[[Category:Argon_troubleshooting]]		[[Category:Argon_troubleshooting]]
	[[Category:IONI_troubleshooting]]		[[Category:IONI_troubleshooting]]
−	~~[[Category:VSD-E/XE_troubleshooting]]~~

@@ Line 12: / Line 12: @@
 *Missing [[Setting device bus address#Bus termination|bus termination]] or too long stub after termination. Correct termination is important especially if RJ45 cable is longer than 3 meters or stub longer than 0.5 meters.
 **With IONICUBE, make sure that bus termination is set on (IONICUBE 4 axis board: insert jumper to JP10 position 1, see image [[IONI & IONICUBE user guide/Making the first Granity connection|here]]) and IONICUBE 1X, set DIP switch S1 position 1 on).
-*Use of crossover RJ45 cable. If this has been used, it might have caused damage that might prevent communication even with correct cable. For repair instructions of Argon, see [[Determining Argon hardware failure]].
+*Use of crossover RJ45 cable. If this has been used, it might have caused damage that might prevent communication even with correct cable.
 *Device has an error state, see [[Argon user guide/LED indicators|led indicators]]
 *Wrong communication interface device selected from Granity
@@ Line 19: / Line 20: @@
 *Device has insufficient logic voltage supply causing erroneous operation or rebooting of device
 *Possibly some incompatibility with the computer, try connection from another computer
-*USB adapter has bee plugged in ''after'' Granity has been started (and because of that it is not in listed in the communication interface devices). Ensure that USB device has been inserted before Granity is started.
+*USB adapter has bee plugged in ''after'' Granity has been started (and because of that it is not in listed in the communication interface devices).
-*Multiple communication interface devices are available and the wrong one has been chosen. Multiple SimpleMotion adapters may be listed even when there is only one SimpleMotion adapter plugged in because Granity might assume some other USB serial port to be also SimpleMotion adapter even when it's not. <br/>[[File:wikimultipleSMdevices.png]]
+**Ensure that USB device has been inserted before Granity is started.
 [[Category:Argon_troubleshooting]]
 [[Category:IONI_troubleshooting]]
 [[Category:VSD-E/XE_troubleshooting]]

@@ Line 1: / Line 1: @@
 This article helps finding cure for connection problems between PC and drive.
-==Granity (Argon & Ioni drives)==
+==Granity (Argon, Ioni & Atomi drives)==
 [[Granity]] requires following conditions to establish connection:
 *Compatible RS485 adapter, such as [[SimpleMotion V2 USB adapter]]
@@ Line 19: / Line 19: @@
 *Device has insufficient logic voltage supply causing erroneous operation or rebooting of device
 *Possibly some incompatibility with the computer, try connection from another computer
-==GDtool, DCtool (VSD-E & VSD-XE drives)==
+[[Category:Argon_troubleshooting]]
-===Symptoms===
+[[Category:IONI_troubleshooting]]
-*Software refuses to connect to the drive
+[[Category:VSD-E/XE_troubleshooting]]
-*After importing parameters, they seem invalid (many 0, 4095 or 65535 values)
-*Drive blinks communication error led sequence
-===Unable to establish (reliable) connection===
-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 (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.
-−
-===Getting communication error during normal use===
-If drive indicates communication error during normal operation (i.e. step/dir usage), it is caused by one of following reasons:
-*Drive is not configured & saved in correct input mode. Ensure that "Force SPI" input mode is not active.
-*IN3 in CMD connector is not in correct state during powering-up of 12V supply. Opto-in 3 (IN3 in CMD connector) should be held at logic 0 (or keep unconnected) while powering up logic supply voltage. If logic 1 is driven to IN3 during power-up, drive will enter into GDtool configuration mode which overrides functions of pins IN3, IN4 and OUT1 for SPI communication or enters in a device firmware upgrade mode. Correct IN3 pin setting is ensured in VSDEPI breakout board design.
-===Testing USB adapter condition===
-Sometimes inability to connect is caused by damaged USB adapter. To verify condition of the cable, please download following tester application and copy the cableTest.exe to GDtool installation folder (same folder with GDtool.exe). Typically GDtool is installed at C:\Program Files\GDtool.
-−
-http://granitedevices.com/assets/files/cabletest.zip
-−
-A short piece of wire that can be inserted in USB adapter 6-pin connector is needed for testing.
-[[Category:Argon troubleshooting]]
-[[Category:VSD-E/XE troubleshooting]]
-[[Category:IONI troubleshooting]]

← Older revision		Revision as of 11:41, 15 April 2015
Line 51:		Line 51:
	[[Category:Argon troubleshooting]]		[[Category:Argon troubleshooting]]
	[[Category:VSD-E/XE troubleshooting]]		[[Category:VSD-E/XE troubleshooting]]
		+	[[Category:IONI troubleshooting]]