Please tell us what your experience has been with Do-more...

[BobO]

What does it do to make program structures retentive?  Remembers status bits like .Running, .Done, and so on and last yield point on a program to run transition?

They are all retained following a power cycle (from RUN mode), but everything is reset when doing a program to run transition. $Main is always reset.

[Controls Guy]

Got it, thanks.  VERY helpful trending MyProgram.RunCounter today -- so cool!  Found out the program was running more often than it was supposed to, and had to revise the RUN rung logic.

[BobO]

Got it, thanks.  VERY helpful trending MyProgram.RunCounter today -- so cool!  Found out the program was running more often than it was supposed to, and had to revise the RUN rung logic.

The effort to develop Trend View was worth it just for the benefit to us while developing the engine. Invaluable tool. 

[Controls Guy]

It really is.  I've used it multiple times on every project I've done since I was aware of it.  Troubleshooting logic, looking at events external to the control system, seeing what various programs do to scan time so you can decide how yieldy to make them, etc.   You can do doggone near anything with that thing!   

[Controls Guy]

Oh yeah, trend view solved another problem for me today as well.

There are a number of I/O lines where another control system sends me a recipe pointer.  I start processing that workpiece and set a flag requesting the next queued job.  I was asking, they weren't telling, despite there being physical work there.

Trend view showed my physical entry switch, my subsequent request for next part, and from them.....nothing.  Later it was sending recipes spontaneously without being asked.  Can't really argue with a trend view in a case like that.

In both cases, I just took a screenshot of Trend View, emailed it to the customer, and let him get it sorted with the makers of the other control system.

[plcnut]

Feature request:
Could you please add CTRL+A (select all) to the Rung comments editor?
Thanks!

[franji1]

Could you please add CTRL+A (select all) to the Rung comments editor?

We will add it.

[plcnut]

Cool beans!

[MAEdwards]

Just downloaded version 1.4.1 today.  Thanks for all of the hard work, HOST Engineering!

[MAEdwards]

Bug or Glitch.

I have encountered a certain bug or a glitch a couple of times now.  While in the Clean Documentation Database, an error window will pop-up stating "Encountered an improper argument" and offers an OK selection.  This selection will not remove the pop-up and will freeze the window.

I have attached pics.  These pics are from two separate encounters.

Let me know you're thoughts.  Thanks.

[MAEdwards]

One of the pics failed to make it.  I am resubmitting.

[franji1]

One of the pics failed to make it.  I am resubmitting.

I sent you a private message.

[MAEdwards]

One of the pics failed to make it.  I am resubmitting.

I sent you a private message.

Thanks.  I will see if I can duplicate it and get back to you.

[LWgreys]

Instruction request!
After hard-coding all the E-stop stuff in to kill all except two programs. I came up with the idea of a Kill-All-Programs with Exception-list and should only be able to use the instruction in $Main.

[franji1]

Instruction request!
After hard-coding all the E-stop stuff in to kill all except two programs. I came up with the idea of a Kill-All-Programs with Exception-list and should only be able to use the instruction in $Main.

Good idea.  We already have a HALT, which halts a specific PROGRAM or TASK code-block.

So HALTALL would halt ALL PROGRAMs and TASKs, except for all the system tasks (e.g. $Main, $tTopOfScan, $t1Second, etc.), and also except for any other specified USER PROGRAM and/or TASK code-blocks (variable list).

And like you stated, HALTALL would only be available from $Main.