Brain Bugs workaround (as of Mach 3.0)........

[poppabear]

Here is the Bugs:

If in a single brain you using 2 or more of the same input (i.e. if you have Enable1 as an input 2-3 times), and you have the input going to different terminators. When you run the Brain only the first of the Three identical inputs will work the other 2 or more will not.

Work around is simple:
for each instance of of the input past the first, put the next in another brain, and if more put each in its own brain. I noted this will happen for Variables as well.
I.e. if a Varible is a terminator, and then you will reuse the variable further down as an input, the only One per brain rule works here too. If you need to use the varible again for another function put it in its own brain.

so, until these bugs are addressed, make sure you only have one instance of an input per brain.

Next Bug:

This is not really a bug, but an undocumented finding. If you have larger brains at Rung 14 and up, the Input will not automatically turn off after you add your 1st lobe. You have to click the input then click the lobe  to turn the lobe on, and the input off.

Next Bug:

This is also a undocumented finding:  When your doing larger brains 20-50 rungs, and then you Enable and hit view brain, you will note that sometimes the lines crunch down so small you cant read them, and if you click on the scroll button nothing happens..............  Well, (and I may be stating the obvious or I am just stupid), but, if you click anywhere in the rungs area, THEN click the scroll, it will grow big again to see the rungs.  Unfortunatly, when it gets bigger in heigth, the individual blocks truncate and you cant read the data, you might see something liike OEMLED but you cant read the number cause it is truncated off.   the only thing I have done is just Document my brians rung by rung (see TCP doc, templates), as the only way to go back and see what the function was since you cant read it on larger brains.

Scott

[mvcalypso]

Hi,  when you say "If you need to use the varible again for another function put it in its own brain."
I don't think I see how this will be a work around can be used since I though the scope of a brain variable was restricted to be local to the brain...?

Dave

[poppabear]

It appears that I was unclear, sorry thinking faster than typing.

redefine the variable in the next brain and only use it as an input once.

[poppabear]

I forgot to mention here, that there is a limit to 50 lines (Rungs), in a brain, for more than that, you have to start another brain and remember to start at the modbus address of the next one up from where you left off on the previous brian.

scott

[poppabear]

Another thing to be aware of, not really a bug just something you will need to address.

For instance if you have an Input that when it activates it "Presses" the reset button, that will Press the reset in Mach, But as long as the Input stay active, you can toggle Mach in and out of the reset on the screen button. The Input that normally presses the Reset until it toggles states again, will only press the Reset ONCE while it is on. This applies to any Input that turns on or changes state, to Reset the Rung you will need to Reset the Input by some other means if you want it act like a "Scanner".

I.e. In the reset button, you drop some code that looks at the input in question and if it is still on, it will reset the Input bit, and if the input bit remains on, it will once again Reset the machine, until you address the INput fault that is turning on the bit.

Scott