inputio interrupt driven?

[howling60]

i know this may seem like a dumb question.. but it recently crossed my mind that i may have been approaching all my rebuild problems with the wrong thought process.

Is the InputIO file/logic an interrupt driven item? i always assumed that it was, and was counting on that fact so that when many things were happening @ once, the controller would see that an I/O had changed state, and would jump into the InputIO file logic. However, was just running a log file on my tool changer, and realized that while the state of an input had changed, the INPUTIO file was not called for "quite some time".. granted, it was still only a short time in MY world but in the computer it seemed like a decent timeslot.

Not that the answer will make a HUGE difference in how i have things setup, but I would like to know for my own benefit & understanding.

Thanks as always!

-Nate

[camsoft]

Howling60

The short answer is that many separate files that contain logic remain dormant until an event causes that file to run it's logic. They all act independently of each other and will run separately. What might through you off is that when you view a Logfile.Fil file the actions you see are listed in a single print out list sequentially, from all events. That's why in the later versions we show the event name that was raised to the left of the logic to help you see the mixing of logic from all files that run together.

Tech Support
CamSoft Corp.
(951) 674-8100
support@camsoftcorp.com
www.cnccontrols.com

[howling60]

awesome.. i kind of had a mental image that contained your explaination.. like i said, just wanted to make sure i had the right thought process going on. Thanks!

-nate