Host Engineering Forum

General Category => General Discussion => Topic started by: PLCGuy on August 03, 2016, 12:14:28 PM

Title: rungs and timers
Post by: PLCGuy on August 03, 2016, 12:14:28 PM
Maybe this was brought up before. When inserting a rung, the rung will turn blue and there is no way to get rid of the blue once the new rung is inserted. Am I doing something wrong?

Concerning timers. I was using the Timer.Timing and noticed once the timer was done, it kept on timing! Is this the normal function? I would expect the Done to turn on, which it does but it keeps on timing. Threw me off when I saw the Timer.Timing flag stay on after it reached the set value. Can there be an option to make it stop timing once it reaches the set value and the done flag turns on. In my case the rung stayed true, which of course kept the timer active.
Title: Re: rungs and timers
Post by: franji1 on August 03, 2016, 12:49:21 PM
Maybe this was brought up before. When inserting a rung, the rung will turn blue and there is no way to get rid of the blue once the new rung is inserted. Am I doing something wrong?

The background color of the rung should not be turning blue.  This shows that the rung is in a "selected" state.  We fixed a bug where this state was incorrectly being set but never cleared, but that was a while ago.  What version are you seeing this in?

Quote

Concerning timers. I was using the Timer.Timing and noticed once the timer was done, it kept on timing! Is this the normal function? I would expect the Done to turn on, which it does but it keeps on timing. Threw me off when I saw the Timer.Timing flag stay on after it reached the set value. Can there be an option to make it stop timing once it reaches the set value and the done flag turns on. In my case the rung stayed true, which of course kept the timer active.

This is the correct behavior for the TMR instruction.  If the Timer is Enabled, it will keep on timing, regardless of the .Done state.  The Koyo PLCs behave similarly.

If you want to be able to stop a timer from timing, but maintain its accumulator value, look at the TMRA (Accumulating Timer), then add a NC contact with Tx.Done parameter in series with your Enable contact logic (i.e. stop timing once done).  TMRA will NOT reset the timer when the Enable leg turns OFF.  There is a Reset leg on the TMRA instruction for performing the reset behavior.
Title: Re: rungs and timers
Post by: BobO on August 03, 2016, 05:02:46 PM
If the timer direction doesn't matter, you can also use a TMRDOWN.
Title: Re: rungs and timers
Post by: Mike Nash on August 03, 2016, 07:24:45 PM
Maybe this was brought up before. When inserting a rung, the rung will turn blue and there is no way to get rid of the blue once the new rung is inserted. Am I doing something wrong?

I have a couple of computers that do this still. Mentioned here:
http://forum.hosteng.com/index.php/topic,1830.0.html (http://forum.hosteng.com/index.php/topic,1830.0.html)
and here:
http://forum.hosteng.com/index.php/topic,1747.0.html (http://forum.hosteng.com/index.php/topic,1747.0.html)

Yes, they are XP and lower memory and speed (just like me.)
Title: Re: rungs and timers
Post by: Garyhlucas on August 03, 2016, 10:42:30 PM
Does it on my Dell M6700 too running Win7 Pro.
Title: Re: rungs and timers
Post by: BobO on August 04, 2016, 01:17:07 AM
So when we 'fixed' it, maybe we didn't?
Title: Re: rungs and timers
Post by: franji1 on August 04, 2016, 08:19:40 AM
Does it on my Dell M6700 too running Win7 Pro.

Do you see the rung's background turn blue only when you insert a rung, or does the rung background change in other situations?
Title: Re: rungs and timers
Post by: PLCGuy on August 04, 2016, 11:53:36 AM
Sorry taking so long to respond. Only when I insert a rung. According to updates, I have the current version.
Title: Re: rungs and timers
Post by: franji1 on August 04, 2016, 11:55:04 AM
Sorry taking so long to respond. Only when I insert a rung. According to updates, I have the current version.

Do you use the keyboard INS key or the menu/mouse to "insert"?
Title: Re: rungs and timers
Post by: Mike Nash on August 04, 2016, 04:00:10 PM
I want to play!

Win XP DMD 1.4.3

If I have highlighted a rung via keyboard or mouse click on the far left, any rung insert above, mouse or keyboard, will leave the originally highlighted rung still highlighted. The newly inserted blank rung will not be. The only consistent means to de-highlight that rung is to select it again using mouse or keyboard (even though you can't see any change) then mouse click (or cursor with keyboard right, left or down) somewhere to the right of the rail WITHIN that highlighted rung. The exception to the last sentence is that the cursor will be at the bottom left after selecting and cursoring down will de-highlight also.

And it doesn't matter if I am online or offline. It also doesn't seem to care if keep empty row option is used or not.

Inserting a rung AFTER the cursor does not leave the rung highlighted. Everything seems hunky-dory as long as the rung is not selected/highlighted before the insert above.
Title: Re: rungs and timers
Post by: Garyhlucas on August 04, 2016, 10:05:52 PM
I believe Mikes description is exactly what I am seeing.
Title: Re: rungs and timers
Post by: PLCGuy on August 06, 2016, 09:20:17 PM
Mike nice job in your explanation.
Only to add. After I use the ins key to add a rung before the curser, then using my mouse any rung I click on also turns blue.
Title: Re: rungs and timers
Post by: franji1 on August 07, 2016, 03:55:22 PM
Mike nice job in your explanation.
Only to add. After I use the ins key to add a rung before the curser, then using my mouse any rung I click on also turns blue.

Interesting.  We can definitely duplicate the issue of trying to insert rung(s) in the middle of a selection ends up creating TWO selection groups, one of which cannot be removed.  It should either maintain the selection and include the new rung as part of the selection.
Title: Re: rungs and timers
Post by: franji1 on December 22, 2016, 12:51:26 PM
We can definitely duplicate the issue of trying to insert rung(s) in the middle of a selection ends up creating TWO selection groups, one of which cannot be removed.
We fixed this.  It will be in the next release.  It just eliminates the selection whenever you try to insert a rung in the middle of the selection.