2nd stage of Crusader II retrofit
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 19203
- Thank you received: 6436
03 Aug 2018 21:55 #115556
by tommylight
Disconnect the wires from a healthy drive and measure the resistance, then measure the yet to be named faulty one. If they are the same, change the cable.
Replied by tommylight on topic 2nd stage of Crusader II retrofit
If there is voltage without the wires connected, that is for sure miss wiring or short in those wires, or even worse it could be the drive with internal problems on the -+10V input (analogue input).Not sure what to make of this but... or why there is no voltage.
I tried reading voltage without the wire in the connection and then there is voltage.
Jim
Disconnect the wires from a healthy drive and measure the resistance, then measure the yet to be named faulty one. If they are the same, change the cable.
The following user(s) said Thank You: jamby
Please Log in or Create an account to join the conversation.
03 Aug 2018 22:07 - 03 Aug 2018 22:08 #115559
by OT-CNC
Replied by OT-CNC on topic 2nd stage of Crusader II retrofit
I'm sorry you haven't sorted it out yet. I think you have the voltage settings wrong on the max output limit. Although I'm not entirely sure that's the problem.
Here is my Y
[JOINT_1]
#********************
TYPE = LINEAR
HOME = 0.0
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
P = 50.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0005
MAX_OUTPUT = 0.0
ENCODER_SCALE = -2540.00508
OUTPUT_SCALE = 10.0
OUTPUT_MIN_LIMIT = -10.0
OUTPUT_MAX_LIMIT = 10.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
HOME_OFFSET = 0.000000
HOME_SEARCH_VEL = -0.050000
HOME_LATCH_VEL = -0.016667
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_SEQUENCE = 2
# Axis Y
#********************
[AXIS_Y]
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
#********************
Here is my Y
[JOINT_1]
#********************
TYPE = LINEAR
HOME = 0.0
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
P = 50.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0005
MAX_OUTPUT = 0.0
ENCODER_SCALE = -2540.00508
OUTPUT_SCALE = 10.0
OUTPUT_MIN_LIMIT = -10.0
OUTPUT_MAX_LIMIT = 10.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
HOME_OFFSET = 0.000000
HOME_SEARCH_VEL = -0.050000
HOME_LATCH_VEL = -0.016667
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_SEQUENCE = 2
# Axis Y
#********************
[AXIS_Y]
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
#********************
Last edit: 03 Aug 2018 22:08 by OT-CNC. Reason: changed scale to limit
The following user(s) said Thank You: jamby
Please Log in or Create an account to join the conversation.
04 Aug 2018 01:12 #115571
by jamby
Replied by jamby on topic 2nd stage of Crusader II retrofit
TommyLight, OT-CNC
Thanks guys. I finally ran down the problem and much like my golf game the problem is with the monkey holding the stick.
I started checking continuity from ground to the connections from TB5 to the J1 connections on the westamp cards. Doing comparisons showed differences between X and the Y connections. And when testing the wiring at PCB-803 P7 Y axis test backwards of the other two axis. So once the wires on the Y axis connection to TB5 were reversed, Y axis jogged --YEAH.
I don't remember even disconnecting those wires besides reversing them but I am just happy that with you help I finally found the problem.
My wife seems to be muttering something about "no fool like an old fool" but I am a happy fool.
Thanks again. Now if I can just get everything buttoned up with out breaking anything else.
Jim
Thanks guys. I finally ran down the problem and much like my golf game the problem is with the monkey holding the stick.
I started checking continuity from ground to the connections from TB5 to the J1 connections on the westamp cards. Doing comparisons showed differences between X and the Y connections. And when testing the wiring at PCB-803 P7 Y axis test backwards of the other two axis. So once the wires on the Y axis connection to TB5 were reversed, Y axis jogged --YEAH.
I don't remember even disconnecting those wires besides reversing them but I am just happy that with you help I finally found the problem.
My wife seems to be muttering something about "no fool like an old fool" but I am a happy fool.
Thanks again. Now if I can just get everything buttoned up with out breaking anything else.
Jim
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 19203
- Thank you received: 6436
04 Aug 2018 06:23 #115586
by tommylight
Those are the correct values for almost all cases when using 7i77.
Replied by tommylight on topic 2nd stage of Crusader II retrofit
I'm sorry you haven't sorted it out yet. I think you have the voltage settings wrong on the max output limit. Although I'm not entirely sure that's the problem.
Here is my Y
[JOINT_1]
#********************
TYPE = LINEAR
HOME = 0.0
FERROR = 0.5
MIN_FERROR = 0.05
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
P = 50.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0005
MAX_OUTPUT = 0.0
ENCODER_SCALE = -2540.00508
OUTPUT_SCALE = 10.0
OUTPUT_MIN_LIMIT = -10.0
OUTPUT_MAX_LIMIT = 10.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
HOME_OFFSET = 0.000000
HOME_SEARCH_VEL = -0.050000
HOME_LATCH_VEL = -0.016667
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_SEQUENCE = 2
# Axis Y
#********************
[AXIS_Y]
MAX_VELOCITY = 3.33333333333
MAX_ACCELERATION = 30.0
MIN_LIMIT = -10.5
MAX_LIMIT = 0.0
#********************
Those are the correct values for almost all cases when using 7i77.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 19203
- Thank you received: 6436
04 Aug 2018 06:24 #115587
by tommylight
Replied by tommylight on topic 2nd stage of Crusader II retrofit
Glad you got it going, it is rewarding to see it move correctly.
Please Log in or Create an account to join the conversation.
04 Aug 2018 17:21 #115610
by OT-CNC
Good, that's from my ini. Jambi has OUTPUT_MIN_LIMIT = -21.63 and OUTPUT_MAX_LIMIT = 11.63 in his ini.
I actually don't understand the DAC scaling or when it's used. I assume as set in my ini the output limits are +/- 10v as that is what the drive requires.
Jamby,
I'm glad you got it working. Did you make changes to the ini?
Replied by OT-CNC on topic 2nd stage of Crusader II retrofit
Those are the correct values for almost all cases when using 7i77.
Good, that's from my ini. Jambi has OUTPUT_MIN_LIMIT = -21.63 and OUTPUT_MAX_LIMIT = 11.63 in his ini.
I actually don't understand the DAC scaling or when it's used. I assume as set in my ini the output limits are +/- 10v as that is what the drive requires.
Jamby,
I'm glad you got it working. Did you make changes to the ini?
The following user(s) said Thank You: jamby
Please Log in or Create an account to join the conversation.
04 Aug 2018 18:46 #115614
by PCW
Replied by PCW on topic 2nd stage of Crusader II retrofit
In general there is no reason to change the defaults and non-matched limits don't make any sense.
For velocity mode drives, you might want to change the analog scaling and limits to machine units (say Inches per second or mm per second) if you know the scaling of machine units/sec at 10V
The advantage of this kind of scaling is that FF1=1.0 and all PID terms and outputs are in machine units, for example, if you had a mill that moved 6 IPS
(360 IPM) at 10V you would set the analog scale and limits to 6,6,-6, FF1 would be 1.0 and the PID output would be scaled in IPS
For velocity mode drives, you might want to change the analog scaling and limits to machine units (say Inches per second or mm per second) if you know the scaling of machine units/sec at 10V
The advantage of this kind of scaling is that FF1=1.0 and all PID terms and outputs are in machine units, for example, if you had a mill that moved 6 IPS
(360 IPM) at 10V you would set the analog scale and limits to 6,6,-6, FF1 would be 1.0 and the PID output would be scaled in IPS
The following user(s) said Thank You: tommylight, OT-CNC
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 19203
- Thank you received: 6436
04 Aug 2018 21:25 #115620
by tommylight
Thank you very much PCW.
Replied by tommylight on topic 2nd stage of Crusader II retrofit
I was sure that it can be set at any value, granted all three values had to be the same for normal use ( except when using analogue drives with +10v/dir inputs, then minimum would be 0 ), but i did not know that with the FF1 to make scaling tailored for 1 !In general there is no reason to change the defaults and non-matched limits don't make any sense.
For velocity mode drives, you might want to change the analog scaling and limits to machine units (say Inches per second or mm per second) if you know the scaling of machine units/sec at 10V
The advantage of this kind of scaling is that FF1=1.0 and all PID terms and outputs are in machine units, for example, if you had a mill that moved 6 IPS
(360 IPM) at 10V you would set the analog scale and limits to 6,6,-6, FF1 would be 1.0 and the PID output would be scaled in IPS
Thank you very much PCW.
Please Log in or Create an account to join the conversation.
06 Aug 2018 15:53 #115670
by jamby
Replied by jamby on topic 2nd stage of Crusader II retrofit
Over the weekend I was able to run several test programs and at the end cut some parts. All went well except for the times when the machine was idle and the computer was sitting with linuxcnc running. Several times like that communication between the 5i25 and 7i77 was lost and linuxcnc threw errors (see pic below).
I had tried turning off options in the bios in hopes of stopping these errors but it still occurs. It never happens while the machine cycling but only when sitting idle (drives not enabled).
There's a pic of the latency test I ran this morning below (this is a servo machine). And a couple of shots of the bios screen.
I don't know if this is a software problem or if its a hardware issue, bad connection or badly seated card. I will open it up and look.
Thanks again guys I am so close I can taste it!!
Jim
I had tried turning off options in the bios in hopes of stopping these errors but it still occurs. It never happens while the machine cycling but only when sitting idle (drives not enabled).
There's a pic of the latency test I ran this morning below (this is a servo machine). And a couple of shots of the bios screen.
I don't know if this is a software problem or if its a hardware issue, bad connection or badly seated card. I will open it up and look.
Thanks again guys I am so close I can taste it!!
Jim
Please Log in or Create an account to join the conversation.
06 Aug 2018 15:58 - 06 Aug 2018 16:04 #115671
by PCW
Replied by PCW on topic 2nd stage of Crusader II retrofit
Those errors indicate complete loss of communication to the 7I77
Possibly because of 5V issues on the 7I77
How is 5V power supplied to the 7I77?
Have you checked the 5V voltage at the 7I77 card?
5V power option jumpering should be:
7I77 W5 RIGHT
5I25 W2 DOWN
External 5V supply to 7I77 TB1
Possibly because of 5V issues on the 7I77
How is 5V power supplied to the 7I77?
Have you checked the 5V voltage at the 7I77 card?
5V power option jumpering should be:
7I77 W5 RIGHT
5I25 W2 DOWN
External 5V supply to 7I77 TB1
Last edit: 06 Aug 2018 16:04 by PCW.
Please Log in or Create an account to join the conversation.
Moderators: cncbasher
Time to create page: 0.108 seconds