Help with homing on dual axis PlasmaC

More
6 years 3 months ago #175074 by Clive S

tommylight wrote: To many things......... But we are hijacking Clive's topic, so i will shut up ! :)


No problem I like the banter.

Please Log in to join the conversation.

More
6 years 3 months ago #175189 by snowgoer540

tommylight wrote:

Clive S wrote: could it be this setp pid.y2.maxerror .0005

Those lines should be deleted or omitted, in most cases.


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:
Code:
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.output

EDIT: It seems that it's just the max error line. It wouldn't home without all the other stuffs.

Please Log in to join the conversation.

More
6 years 3 months ago #175203 by tommylight
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.

Please Log in to join the conversation.

More
6 years 3 months ago #175206 by snowgoer540

tommylight wrote: 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 to join the conversation.

More
6 years 3 months ago #175207 by Clive S

snowgoer540 wrote:

tommylight wrote: 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

Please Log in to join the conversation.

More
6 years 3 months ago #175254 by Todd Zuercher

tommylight wrote: 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 to join the conversation.

More
6 years 3 months ago #175617 by phillc54
Chris has pushed a fix to Pncconf for the pid.n.maxerror issue.

Please Log in to join the conversation.

More
6 years 3 months ago #175665 by snowgoer540

phillc54 wrote: 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 to join the conversation.

More
6 years 3 months ago #175670 by rodw

snowgoer540 wrote:

phillc54 wrote: 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

Please Log in to join the conversation.

More
6 years 3 months ago #175674 by Clive S
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

Please Log in to join the conversation.

Time to create page: 0.058 seconds
Powered by Kunena Forum