I don't have a copy of the code handy, but for my table, I modified the thc
component to have two different correction velocities. The slower velocity
is used when the actual voltage is close to the set-point and the faster
velocity is used otherwise. Both velocities and how-close-is-close are set
Thanks for that code, I looked at pid.c a few times but > 600 lines of C
made me dizzy. Let me see what I can do with that.
JT
On 1/24/2017 7:29 AM, andy pugh wrote:
> On 24 January 2017 at 00:06, John Thornton wrote:
>> if(enable){
>> float min_velocity = requested_vel
>> -(requ
why not just use the pid component that is already in linuxcnc?
On 1/24/2017 7:49 AM, EBo wrote:
> On Jan 24 2017 6:29 AM, andy pugh wrote:
>> On 24 January 2017 at 00:06, John Thornton wrote:
>>> if(enable){
>>> float min_velocity = requested_vel
>>> -(requested_vel*(1/velocity_tol
On Jan 24 2017 6:29 AM, andy pugh wrote:
> On 24 January 2017 at 00:06, John Thornton wrote:
>> if(enable){
>> float min_velocity = requested_vel
>> -(requested_vel*(1/velocity_tol));
>> if(current_vel > 0 && current_vel >=
>> min_velocity){vel_status = 1;}
>> else {ve
On 24 January 2017 at 00:06, John Thornton wrote:
> if(enable){
> float min_velocity = requested_vel
> -(requested_vel*(1/velocity_tol));
> if(current_vel > 0 && current_vel >= min_velocity){vel_status = 1;}
> else {vel_status = 0;}
>
> if(torch_on && arc_ok &&
