Help with homing on dual axis PlasmaC
18 Jul 2020 20:07 #175074
by Clive S
No problem I like the banter.
Replied by Clive S on topic Help with homing on dual axis PlasmaC
To many things......... But we are hijacking Clive's topic, so i will shut up !
No problem I like the banter.
The following user(s) said Thank You: phillc54, tommylight
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
Less
More
- Posts: 2328
- Thank you received: 745
19 Jul 2020 19:34 - 19 Jul 2020 19:41 #175189
by snowgoer540
Should all the "pid" lines be commented out/deleted for each joint in a stepper system, as opposed to just the line referenced by Clive?
So comment/delete:
EDIT: It seems that it's just the max error line. It wouldn't home without all the other stuffs.
Replied by snowgoer540 on topic Help with homing on dual axis PlasmaC
Those lines should be deleted or omitted, in most cases.could it be this setp pid.y2.maxerror .0005
Should all the "pid" lines be commented out/deleted for each joint in a stepper system, as opposed to just the line referenced by Clive?
So comment/delete:
setp pid.x.Pgain [JOINT_0]P
setp pid.x.Igain [JOINT_0]I
setp pid.x.Dgain [JOINT_0]D
setp pid.x.bias [JOINT_0]BIAS
setp pid.x.FF0 [JOINT_0]FF0
setp pid.x.FF1 [JOINT_0]FF1
setp pid.x.FF2 [JOINT_0]FF2
setp pid.x.deadband [JOINT_0]DEADBAND
setp pid.x.maxoutput [JOINT_0]MAX_OUTPUT
setp pid.x.error-previous-target true
setp pid.x.maxerror .0005
net x-index-enable <=> pid.x.index-enable
net x-enable => pid.x.enable
net x-pos-cmd => pid.x.command
net x-pos-fb => pid.x.feedback
net x-output <= pid.x.outputEDIT: It seems that it's just the max error line. It wouldn't home without all the other stuffs.
Last edit: 19 Jul 2020 19:41 by snowgoer540.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 17778
- Thank you received: 5909
19 Jul 2020 21:29 #175203
by tommylight
Replied by tommylight on topic Help with homing on dual axis PlasmaC
Those should not be deleted, they are required for Mesa stepgens.
They are not required for software stepping, but i would think they could be used also, never tested that.
They are not required for software stepping, but i would think they could be used also, never tested that.
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
Less
More
- Posts: 2328
- Thank you received: 745
19 Jul 2020 21:36 #175206
by snowgoer540
So just delete the maxerror line then? Or are you saying don’t delete any?
Replied by snowgoer540 on topic Help with homing on dual axis PlasmaC
Those should not be deleted, they are required for Mesa stepgens.
They are not required for software stepping, but i would think they could be used also, never tested that.
So just delete the maxerror line then? Or are you saying don’t delete any?
Please Log in or Create an account to join the conversation.
19 Jul 2020 21:46 - 19 Jul 2020 21:47 #175207
by Clive S
Yes just delete setp pid.x.maxerror .0005 or comment them out
Replied by Clive S on topic Help with homing on dual axis PlasmaC
Those should not be deleted, they are required for Mesa stepgens.
They are not required for software stepping, but i would think they could be used also, never tested that.
So just delete the maxerror line then? Or are you saying don’t delete any?
Yes just delete setp pid.x.maxerror .0005 or comment them out
Last edit: 19 Jul 2020 21:47 by Clive S.
The following user(s) said Thank You: snowgoer540
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 4962
- Thank you received: 1369
20 Jul 2020 13:34 #175254
by Todd Zuercher
(Maybe this is going a bit off topic)
Yes, the PID loops should be left in, but no they aren't nessisary. The Mesa stepgens can be commanded directly with position commands just like a software stepgen usually is. But they supposedly work better with the PID, as it helps to cancel out error caused by real-time jitter in servo-thread. (But remember we are talking about tiny errors that most likely would be imperceivable except at high feedrates.)
One way to look at the difference between the two command types is one way is telling the step gen where it should be, and the other is telling it where it should be going.
Replied by Todd Zuercher on topic Help with homing on dual axis PlasmaC
Those should not be deleted, they are required for Mesa stepgens.
They are not required for software stepping, but i would think they could be used also, never tested that.
(Maybe this is going a bit off topic)
Yes, the PID loops should be left in, but no they aren't nessisary. The Mesa stepgens can be commanded directly with position commands just like a software stepgen usually is. But they supposedly work better with the PID, as it helps to cancel out error caused by real-time jitter in servo-thread. (But remember we are talking about tiny errors that most likely would be imperceivable except at high feedrates.)
One way to look at the difference between the two command types is one way is telling the step gen where it should be, and the other is telling it where it should be going.
Please Log in or Create an account to join the conversation.
24 Jul 2020 10:55 #175617
by phillc54
Replied by phillc54 on topic Help with homing on dual axis PlasmaC
Chris has pushed a fix to Pncconf for the pid.n.maxerror issue.
The following user(s) said Thank You: Clive S
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
Less
More
- Posts: 2328
- Thank you received: 745
24 Jul 2020 17:38 #175665
by snowgoer540
Do main LinuxCNC updates come along with the recovery branch? I dont need this one, just was curious.
Replied by snowgoer540 on topic Help with homing on dual axis PlasmaC
Chris has pushed a fix to Pncconf for the pid.n.maxerror issue.
Do main LinuxCNC updates come along with the recovery branch? I dont need this one, just was curious.
Please Log in or Create an account to join the conversation.
24 Jul 2020 19:59 #175670
by rodw
No, not unless the branch is rebased back to master branch by the developer concerned. The usual workflow is to create an experimental branch containing a new feature and once its tested and working, a pull request is created which if accepted by the team will move the change to master branch
Replied by rodw on topic Help with homing on dual axis PlasmaC
Chris has pushed a fix to Pncconf for the pid.n.maxerror issue.
Do main LinuxCNC updates come along with the recovery branch? I dont need this one, just was curious.
No, not unless the branch is rebased back to master branch by the developer concerned. The usual workflow is to create an experimental branch containing a new feature and once its tested and working, a pull request is created which if accepted by the team will move the change to master branch
The following user(s) said Thank You: snowgoer540
Please Log in or Create an account to join the conversation.
24 Jul 2020 20:54 - 24 Jul 2020 20:57 #175674
by Clive S
Replied by Clive S on topic Help with homing on dual axis PlasmaC
I have a brain fade.. re 7i96
On a Hypertherm 45xp the torch start wires are green and black the manual states dry contacts
I have connected them to hm2....ssr.......7i96....00 output this does not fire the torch.
Do I have to put 24V on pin 14+ and then connect green to pin 12- then black to gnd
On a Hypertherm 45xp the torch start wires are green and black the manual states dry contacts
I have connected them to hm2....ssr.......7i96....00 output this does not fire the torch.
Do I have to put 24V on pin 14+ and then connect green to pin 12- then black to gnd
Last edit: 24 Jul 2020 20:57 by Clive S.
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.088 seconds