Hi Andy , its been a while since Id seen you answer a question , I had feared you had left the forum... excellent to know such is not the case.I have not solved this , I did initially write this as a finite state machine. It would fall through the cases , but would miss the button presses and wouldn't set the status bits ( cs_your_bit_name). Here is one of my iterations of this code.
Code:
component coolant;
pin in bit cool_auto_on; // connected to iocontrol coolant
pin in bit pb_cool_on; // connected to pokeys input bit
pin io bit cs_coolant_auto_on;
pin io bit cs_coolant_man_on;
pin io bit cs_coolant_off;
param rw bit cool_mode;
pin out bit cr_idod_clnt; // connected to mesa output bit
function _ nofp;
license "gpl";
;;
FUNCTION(_)
{
switch(cool_mode)
{
case 0:
if((cool_auto_on)==1&&(cs_coolant_auto_on)==0) // auto on
{
cs_coolant_auto_on=1;
cs_coolant_man_on=0;
cs_coolant_off=0;
cr_idod_clnt=1;
}
else
{
cool_mode=1;
}
break;
case 1:
if((cs_coolant_auto_on)==1&&(pb_cool_on)==1) // auto interrupt
{
cs_coolant_off=1;
cr_idod_clnt=0;
}
else
{
cool_mode=2;
}
break;
case 2:
if(((cs_coolant_auto_on)==1&&(cs_coolant_off)==1)&&(pb_cool_on)==1) // auto resume
{
cs_coolant_off=0;
cr_idod_clnt=1;
}
else
{
cool_mode=3;
}
break;
case 3:
if((cool_auto_on)==0&&(cs_coolant_auto_on)==1) // auto off
{
cs_coolant_auto_on=0;
cr_idod_clnt=0;
}
else
{
cool_mode=4;
}
break;
case 4:
if((pb_cool_on)==1&&(cs_coolant_man_on)==0) //man on
{
cs_coolant_man_on=1;
cs_coolant_auto_on=0;
cr_idod_clnt=1;
}
else
{
cool_mode=5;
}
break;
case 5:
if((cs_coolant_man_on)==1&&(pb_cool_on)==1) // man off
{
cr_idod_clnt=0;
cs_coolant_man_on=0;
}
else
{
cool_mode=0;
}
break;
}
This has been a part of larger component that runs my whole operator panel and has been a separate component like above. In both instances, the behavior of the button press and subsequent actions have been inconsistent. Sometimes they work, sometimes takes two pushes. Commanding coolant with M8 always works , shutting it off with M9 ,eventually-it hangs up. Sometimes the coolant will come on with a button press, often just for a couple seconds . It seems like logic is getting caught up between scans . This panel uses pokeys 55 usb, my other panel uses mesa smart serial. My guess was getting caught up in user space , maybe this would be better off as pure user space component? If I lose the code that uses m8/m9 and just keep as a button press, it engages the contractor on and off like a fluttering relay contact . Your thoughts?
