331
General Mach Discussion / Re: Ignore Z
« on: August 18, 2011, 08:00:23 PM »The CB option is DoOemButton(252) same as the setting screen button
Hope that helps, (;-) TP
Just got around to trying this. Worked great. Thanks for the tip.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
The CB option is DoOemButton(252) same as the setting screen button
Hope that helps, (;-) TP
Thanks for the responses, it has been incredibly helpful. It seems the only sure-fire way of making a robust dynamic height control would be to send the pulses into a PLC and apply the THC there, delaying all signals equally. A PID loop could also be implemented in the PLC, and wouldn't be too difficult. The result would be a kick-a$$ dynamic height controller.
While I think it's likely possible, it doesn't look simple at all, while the PLC approach is straight forward and extremely robust.
Could you recommend such a unit for me to research?
I guess the engineer that designed and built the unit did not know what he was talking about then. Shame to waste all that time on education. I'll let him know that he should not waste all his time working on such silly things that could never be possible.
But then again MAYBE that is why it works so good.
You guys are funny,
(;-) TP
RRC , it is very easy to get the MACHINE to operate outside of the preset PID range. IF you use a feed screw that is too fast it is possible to outrun the pid because is not adjustable in most THCs and most pids are range specific to tuning SO if the PID is not use adjustable you MUST engineer the feedsytem to OPERATE in the boundaries of the set PID.
The pid is used as PART of the sensoring of the arc voltages. IT tries to average out the input stream and make a smooth control output signal not just filter out high /low.
THE thcup/down is only the fairly high speed digital INPUT to control the Z thru MACH.
IF those signals are erratic then the Z will be erratic. The PID filtering takes place in the DTHC.
Being that Mach3 is NOT a real time controller your on the fly height correction calculations are not going to work well. Yes you can use #vars for Zheight control but ONCE the moves are loading into the buffer then that is it. IF you try to calculate the variable at the point the #var is loaded into the buffer you will find you cannot comp something that has not happened yet. the next problem is the only way you have to update those vars are thru either the brains or the macropump. At a MAX of 10 updates per sec you will fall FAR short of the speed to do it well.
The ONLY access you have at that point IS the THC functions up/down to comp the surface heights based on what the DTHC sees. AND it is NOT value based it is like playing ping pong slapping the ball back and forth. THe Z at that point will not even use the motor vel/accel parameters it just basically slaps the motor wide open in the direction it is to move and lets the DTHC deal with it being correct in height. Woops overshot slap it back in the other direction.
That is where the PID has to step in. Same basic princible as a servo motor drive.