01-31-2008 10:05 AM
Turn On: Fieldpoint1.Sw_StopPinA_Extended<1 and (Sequencer_VertMillingA.D or Sequencer_VertMillingA.E or Sequencer_VertMillingA.I or Sequencer_VertMillingA.J or Sequencer_VertMillingA.K or Sequencer_VertMillingA.L or Sequencer_VertMillingA.O or Sequencer_VertMillingA.S)
Turn Off: Pb_ResetLockpinA
02-01-2008 12:11 AM
Do you mean that after you open the lookout process the Latchgate will be ON, but it should be OFF?
Create another expression of Fieldpoint1.Sw_StopPinA_Extended<1 and (Sequencer_VertMillingA.D or Sequencer_VertMillingA.E or Sequencer_VertMillingA.I or Sequencer_VertMillingA.J or Sequencer_VertMillingA.K or Sequencer_VertMillingA.L or Sequencer_VertMillingA.O or Sequencer_VertMillingA.S). Then reopen the process. See when the Latchgate is unexpectedly "ON", what's the status of that expression. If the expression is False, this behaviour is wrong.
02-01-2008 11:31 AM
Ryan
The "latchgate" does not go high upon starting the process. The purpose of this latchgate is to monitor the extended position of the stop-pin, during certain states of a programmed "sequencer" object.
State #3(output-C) of the sequencer extends the stop-pin. The goto-4(output-D) data member of the sequencer is connected to the stop-pin extended switch. The stop-pin extended switch sends the sequencer to state #4, output-D.
The latchgate will go high when the stop-pin extended switch makes/closes. The ON expression never "trues".
This will happen every time I reset the latchgate and start the sequencer object, until I go into edit mode/object explorer and open the properties window for the latchgate(s). All I have to do is open & close the properties dialouge window for the 4 latchgates and then they will function as designed, until I close the process and reopen it. Then I have to do it all over again.
Chip Howell
Amtec Corporation
256-319-6210
02-03-2008 02:13 AM