[legendboy]

Just can't seem to get the disable input to work.

I have a 24v relay powered up when my estop circuit is not activated
I have a 5vdc regulated ps connected 0v to io_com and 5v to the Opto input on the drive. Power is applied thru a 220ohm resistor to the input when the relay is turned off.

I have tried all available Opto inputs and 2 drives. Power is flowing as it should.

[neilw20]

What model driver are you trying to control.
Signaling methods are many and varied, and some may not even have enable inputs that work.
Without reference to the specifications of the specific model, it is rather hard to guess.

What you have shown will operate the opto correctly.
Current flows through the 220ohm. Opto is on. No current it is off.
Measure the voltage across the resistor. You will see 2.5-3v or so when on.
Nothing when off.

PS.
As legendboy did not identify the model, I did not assume anything about the resistor.

I'll add to this, as the resistor is internal.
Voltage across terminal > 3v or so. It is ON.
0-0.8v. it is OFF

[Al_The_Man]

The 220ohm resistor is internal on the Granite?
Al.

[legendboy]

Thanks for the reply guys, sorry I should have stated my drive is VSD-XE.

I should explain what I am trying to do. Temporarily wire the disable input to my estop circuit for servo tuning.

I have added an external resistor probably in error, however when I supplied 5vdc directly to the opto input I just loose connection to the drive and am un able to connect back to it with my laptop.

What exactly is suppose to happen when the drive has been disabled? Is the only status indicator flashing blue led?

What should show on the device status page?

[neilw20]

When disabled, power is removed from the motor.
For 5v you don't need a resistor to operate the opto.
Do you have charge pump enabled?
That will stop it if not working. See troubleshooting in vsdepi_manual

[Al_The_Man]

There appears to be no dedicated input for enable?
Are you using IN4 or IN5 and configured it with GDtool?
I notice the option is for SPI or Pulse input, is this set up for pulse?
I haven't used Granite devices so just going by the manual?
Al.

[legendboy]

When disabled, power is removed from the motor.
For 5v you don't need a resistor to operate the opto.
Do you have charge pump enabled?
That will stop it if not working. See troubleshooting in vsdepi_manual

Neil, is there any physical indicator I can see when the drive has been disabled?

Got it, no resistor needed.

I am not exactly sure what a charge pump is, nor do I see any mention of it in GDTool or the vsd_xe manual. So to answer your question, I don't know.

I don't have the vsdepi but I will check out the manual

There appears to be no dedicated input for enable?
Are you using IN4 or IN5 and configured it with GDtool?
I notice the option is for SPI or Pulse input, is this set up for pulse?
I haven't used Granite devices so just going by the manual?
Al.

Right, unless "servo ready" is the equivalent to enable
(This becomes logic 1 when servo is ready for user commands)

There are 2 available opto inputs I can use, in3 and in4.

I think what you are referring to is "Drive pulse input mode"?
I have that set for step/dir.

Thanks for taking some time to help me out guys

[legendboy]

Does this accurately describe a charge pump and how it relates to a granite drive and controller?:

Motion controller watchdog output -> vsd-xe servo ready input

[Al_The_Man]

That is one way of using it, the fact that the drives are enabled means that the Charge pump/watchdog is not being used.
You can either use this method or the N/C relay contact.
If using disable from watchdog timer then other means Should be used for E-stop such as hardwired removal of supply power, or the watchdog output can be inserted in the E-Stop string.
Al.

[legendboy]

Got it, so definitely not using a charge pump in this case because what I am doing has nothing to do with my motion controller at this point.

using the NC relay i am merely trying to get a temporary estop circuit in place so that I don't have to risk physical damage to my mill while trying to get the axis's tuned

Thanks for the explination/confirmation

[legendboy]

One thought.....

I do remember reading that the SPI port and the CMD port can't be used at the same time.

I wonder if this just won't work? If that IS the case, how can one protect his machine against runaway while tuning the drive with GDtool? Strictly with software? ie, motion fault limit

[Al_The_Man]

Drive enable is just about standard and usually a dedicated input?
Maybe clarify it with Granite, there should be a way?
Otherwise you would have to cut the drive power.
Al.

[Xerxes]

Yes, the 220 ohm resistor is inside drive so you can connect 5V directly between IO_COM and IN.

I wrote instructions of how to verify signal propagation to drive:
Testing input pins on VSD-E/XE - Granite Devices Knowledge Wiki

I'll watch this thread for further questions

[legendboy]

When I give +5vdc on pin 9 or 10 of the cmd connector I get an error on my laptop:

"Please check connections and reconnect"

I have tried both pins on 2 drives, same thing.

I have a 5vdc sola power supply 0v connected to v_com and +5v to pin 9 or 10. As well, 0v is connected to the system star grounding point.

This power is being controlled by a relay. The relay is turned on when my estop circuit is not activated and is turned off when the estop is activated.

+5vdc flows thru the relay to the cmd connector when the relay is turned off.


I have checked over my wiring, measured with my multi meter and can not find any problems.

[legendboy]

I just replaced the sola power supply with a 6v battery, same results

[legendboy]

Here is a paste from the event log.

I connected to the drive and imported settings. Then i put 6.5v to pin 10 (in3 as configured in your wiki link)

I started out on the motor settings page, clicked on every page until i hit the device status page, then got the connection error. When this happens I get blue, red and green blinking leds.

Error 14

Got input from SPI shell
Saatiin viesti:  0
Parametreja: 2
 0
Import call done
load
Loading drive2gdtool.xml
XML in: CFG_MOTOR_MODE Max: 7 Min: 0 Current: 3
XML in: CFG_RECOVERY_SPEED Max: 32767 Min: 1 Current: 200
XML in: CFG_DEFAULT_CONTROL_MODE Max: 4 Min: 0 Current: 1
XML in: CFG_FERROR_TRIP Max: 16383 Min: 0 Current: 5000
XML in: CFG_MULTIPLIER Max: 30000 Min: 1 Current: 500
XML in: CFG_DIVIDER Max: 30000 Min: 1 Current: 500
XML in: CFG_PULSE_MODE Max: 5 Min: 0 Current: 0
XML in: CFG_ABS_IN_OFFSET Max: 65535 Min: 0 Current: 0
XML in: CFG_DRIVE_FLAGS Max: 65535 Min: 0 Current: 2048
XML in: CFG_MOTION_FAULT_THRESHOLD Max: 16384 Min: 0 Current: 1000
XML in: CFG_VEL_I Max: 32767 Min: 0 Current: 30
XML in: CFG_POS_P Max: 32767 Min: 0 Current: 440
XML in: CFG_VEL_P Max: 32767 Min: 0 Current: 4000
XML in: CFG_AD_VEL_I Max: 32767 Min: 0 Current: 26214
XML in: CFG_AD_POS_P Max: 32767 Min: 0 Current: 13107
XML in: CFG_AD_VEL_P Max: 32767 Min: 0 Current: 0
XML in: CFG_VEL_FF Max: 32767 Min: 0 Current: 1
XML in: CFG_ACC_FF Max: 32767 Min: 0 Current: 1
XML in: CFG_AD_LIM Max: 16383 Min: 0 Current: 2
XML in: CFG_TORQ_P Max: 30000 Min: 10 Current: 2300
XML in: CFG_TORQ_I Max: 30000 Min: 0 Current: 60
XML in: CFG_TORQUELIMIT_PEAK Max: 40000 Min: 0 Current: 40000
XML in: CFG_TORQUELIMIT_CONT Max: 18000 Min: 0 Current: 11000
XML in: CFG_TORQUELIMIT_HOMING Max: 18000 Min: 0 Current: 1000
XML in: CFG_TORQUELIMIT_FAULT Max: 43000 Min: 0 Current: 43000
XML in: CFG_ENCODER_PPR Max: 65535 Min: 50 Current: 250
XML in: CFG_MOTOR_POLEPAIRS Max: 100 Min: 1 Current: 2
XML in: CFG_PHASESEARCH_VOLTAGE_SLOPE Max: 20000 Min: 15 Current: 500
XML in: CFG_PHASESEARCH_CURRENT Max: 10000 Min: 100 Current: 1000
XML in: CFG_THERMAL_TIMECONSTANT Max: 7200 Min: 30 Current: 3300
XML in: CFG_TRAJ_PLANNER_ACCEL Max: 32767 Min: 1 Current: 7
XML in: CFG_TRAJ_PLANNER_VEL Max: 32767 Min: 1 Current: 8500
XML in: CFG_TRAJ_PLANNER_HOMING_VEL Max: 32767 Min: 1 Current: 2
XML in: CFG_TRAJ_PLANNER_HOMING_ACCEL Max: 32767 Min: 1 Current: 10
XML in: CFG_TRAJ_PLANNER_HOMING_BITS Max: 127 Min: 0 Current: 7
XML in: CFG_TRAJ_PLANNER_HOMING_HARD_STOP_THRESHOLD Max: 16384 Min: 0 Current: 0
XML in: CFG_TRAJ_PLANNER_HOMING_OFFSET_LO Max: 65535 Min: 0 Current: 0
XML in: CFG_TRAJ_PLANNER_HOMING_OFFSET_HI Max: 65535 Min: 0 Current: 0
XML in: CFG_ABSPOSITION_HI_LIMIT_HI Max: 65535 Min: 0 Current: 0
XML in: CFG_ABSPOSITION_HI_LIMIT_LO Max: 65535 Min: 0 Current: 0
XML in: CFG_ABSPOSITION_LO_LIMIT_HI Max: 65535 Min: 0 Current: 0
XML in: CFG_ABSPOSITION_LO_LIMIT_LO Max: 65535 Min: 0 Current: 0
XML in: CFG_TORQUE_LPF_BANDWIDTH Max: 9 Min: 0 Current: 3
XML in: CFG_VELOCITY_FERROR_TRIP Max: 16383 Min: 0 Current: 1000
XML in: RUNTIME_CAPTURE_SOURCE Max: 65535 Min: 0 Current: 1284
XML in: RUNTIME_CAPTURE_SOURCE_2 Max: 65535 Min: 0 Current: 487
XML in: RUNTIME_CAPTURE_TRIGGER Max: 65535 Min: 0 Current: 2
XML in: RUNTIME_CAPTURE_SAMPLERATE Max: 65535 Min: 0 Current: 200
XML in: RUNTIME_CAPTURE_BUF_LENGHT Max: 2064 Min: 0 Current: 2000
XML in: RUNTIME_FAULTBITS Max: 1 Min: 2 Current: 0
XML in: RUNTIME_STATUSBITS Max: 1 Min: 2 Current: 12571
XML in: RUNTIME_CONTROL_MODE Max: 4 Min: 0 Current: 1
XML in: RUNTIME_INPUT_WATCHDOG Max: 65535 Min: 0 Current: 0
XML in: RUNTIME_BUS_VOLTAGE_SCALE_100V Max: 1 Min: 2 Current: 14674
XML in: RUNTIME_CURRENT_SCALE_1A Max: 1 Min: 2 Current: 331
XML in: RUNTIME_RETURN_PARAMETER_TYPE Max: 31 Min: 0 Current: 0
XML in: RUNTIME_FEATURES1 Max: 1 Min: 2 Current: 1599
XML in: RUNTIME_FIRMWARE_VERSION Max: 1 Min: 2 Current: 208
XML in: RUNTIME_DEVICE_TYPE Max: 1 Min: 2 Current: 270
XML in: READONLY_PWM_FREQUENCY Max: 1 Min: 2 Current: 20000
XML in: READONLY_PID_FREQUENCY Max: 1 Min: 2 Current: 2500
XML in: RUNTIME_OVERRIDE_COMMUTATION_ANGLE Max: 65535 Min: 0 Current: 0
XML in: RUNTIME_DEBUGPARAM1 Max: 65535 Min: 0 Current: 0
XML in: READONLY_BACKWARDS_COMP_VERSION Max: 1 Min: 2 Current: 119
XML in: CFG_OPTO_OUT1_SOURCE Max: 65535 Min: 0 Current: 16402
XML in: CFG_OPTO_OUT2_SOURCE Max: 65535 Min: 0 Current: 16405
XML in: CFG_DISABLE_IN_SOURCE Max: 65535 Min: 0 Current: 8195
XML in: CFG_CLEAR_FAULTS_EDGESOURCE Max: 65535 Min: 0 Current: 8195
XML in: CFG_START_HOMING_EDGESOURCE Max: 65535 Min: 0 Current: 255
XML in: CFG_STAT_USER_BIT_SOURCE Max: 65535 Min: 0 Current: 2
XML in: CFG_HV_VOLTAGE_LOW_LIMIT Max: 17000 Min: 1000 Current: 10000
XML in: CFG_HV_VOLTAGE_LIMIT Max: 17000 Min: 2000 Current: 17000
Import succeeded.
fill
updatePinCaptions
Shell command: READENCODER
Running READENCODER...
cDevice::sendCommandOnly( 50, 25 )
0x32001981 -> 0x1b000012
cDevice::sendCommand( 51, 5600 )
0x3315e028 -> 0x1b000012
Communication error
0x200008a -> 0xffff
ERROR: Communication halted, please reconnect
cDevice::sendCommandOnly( 2, 0 )
0
>
Got input from SPI shell
Saatiin viesti: #7 0
Parametreja: 2
#7 0
Invalid shell command:#7 0

Shell command: READENCODER
Running READENCODER...
cDevice::sendCommandOnly( 50, 25 )
cDevice::sendCommand( 51, 5600 )
cDevice::sendCommandOnly( 2, 0 )
0
>
Got input from SPI shell
Saatiin viesti:  0
 0
 0
Parametreja: 4
 0
setConnectionStatus
connected
Connection failed
 0
setConnectionStatus
connected
Connection failed
 0

[neilw20]

Looks like the connection crashed the USB part of the system.
You are stuffing voltage/current where it doesn't belong.
6.5 v is more than 5v, and unless it is only going into an opto you might fry things.

[legendboy]

Looks like the connection crashed the USB part of the system.
You are stuffing voltage/current where it doesn't belong.
6.5 v is more than 5v, and unless it is only going into an opto you might fry things.

I know 6.5v is more then 5v, someone on another forum suggested it, and I wanted to try it. VSD-XE has a 2yr warranty after all

Same result regardless

I also just downloaded a fresh copy of GDFlasher, uninstalled, reinstalled the new copy, flashed the drive

Same result

[legendboy]

Here is a link to my full event log


Here is a pic of my temp wiring
Temp wiring is ghetto because of how much i have been changing it

[legendboy]

Anybody have ANY ideas what might be causing this? No idea too unlikely at this point lol