Flex727

My response from Unitronics Support has always been within 24 hrs and most often within the same day.

Under Utils/Clock, there are functions that allow you to specify action based on Time of Day, Day of Week, Day of Month, etc.

Use a self-resetting 24 hour timer to increment a counter. When the counter reaches the appropriate number of days, it will trigger the action you want. Then reset the counter to start again.

Unfortunately, I think the answer to that is no.

It doesn't keep growing because the sum is multiplied by 99 then divided by 100. In other words, you take 99% of the 100 point sum and add the new value (which is 1% of the total). As I said, it appears to me to be a bit smoother and more laggy than a genuine 100 point moving average (which sometimes can be a good thing), but it is only 3 steps and two operands to create a (pseudo) moving average of any number of points - to the limits of a 32-bit integer. However, I'm going to study your LargeFilterJT a bit. By the way, that vlp file appears to have been saved with 9.8.64, but you seem to be using the version from before Unitronics fixed the database issue to prevent it from being opened in 9.8.31. You should remove that version and re-download & install.

That's a common problem. Glad you got it working.

What is turning MB 216 back on? Also, what is "pressure stays high"? Which bit is that?

Looks good. Does it work the way you expect?

No, change rung 9 & 10 to match what I posted above. Rung 7 looks right.

You cannot do what you want as long as a Direct Contact for MB 1004 is in Rung 7. You either need to remove it or change it from a Direct Contact to a Positive Transition Contact. Change the MB 216 Direct Coil to a Set Coil in Rung 7, remove the contact for TE 21, and remove the contact for MB 216. Change Run 9 to: MB216 TD21 ---| |---------( )--- Add after Rung 9: TD21 MB216 ---|P|-------(R)--- Note that the above requires you to change the Timer from a TE to a TD.

Sorry, I'm confused about what you're trying to do. If you write your algorithm out in simple words, I can help you program it.

Use a DIRECT Contact. -||-

That is an INVERTED CONTACT, not a normally closed contact. An Inverted Contact will flow power only when the bit is OFF.

How did you think it would work? Did you read the Help file?

Which of the 3 types of timers are you using? Look in the Help file under Timers (T) and you'll find a very clear and detailed description of how each timer works. If you want a bit to stay on for 1 minute, one way is to use a TE timer set for 1 minute. You will need to reset it before using it again, however. Another method is to use a TD timer and Set the bit you want on for 1 min and Reset the bit when the timer expires.

I loaded your program into a V700 and the RTC is working perfectly. I also see the Direct Clock Function is turning on the correct bit (as of right now, MB 503). You either have a hardware/firmware problem or something about the I/O (that I don't have on my V700) is causing the problem. Please note that the only value you should see changing constantly is SI 30 (Current Second). Did you try setting the time from your PC by using the SET RTC function? By the way, I can't imagine your control over the LCD screen brightness (SI 9) is working properly. Why are you using STI (Store Indirect) with a Constant value?

I hate to dig up a 5 year old post, but I'm wondering if anyone has used this potential shortcut: This would be for a 100 point moving average: ML 0 is the final moving average and ML 1 is each new point added to the moving average. This appears to me to be a bit smoother than an actual moving average, but with a slower response to large changes, but possibly good enough. I think it's obvious how to change it for any length moving average. Thoughts? I'm not a math whiz, so maybe I'm missing something important.

For troubleshooting, I'm going to suggest you set the V700 logic IDENTICAL to the V570 logic but leave out the System Operands that don't apply. If that works, than re-create those operands, one at a time, using the Socket Status Request #22. When converting from V570 to V700, I would normally just change the V570 Hardware Configuration to V700 then adjust the graphics to fill the screen, as needed (as well as replace the communication System Operands that don't apply).

What are you connecting to? What information are you exchanging? I notice that your local port and remote port are the same. Nothing wrong with that, but if the post # is changed, you need to re-initialize the Socket.

With a V570, my Connect rung normally looks something like this. I've never tried to activate a Connect function with a one-shot as you are doing, but I suppose it could work if there was no other traffic to interfere. You should do a bit of experimentation and take out the MI 2 Compare block and see what happens. When I work with a V700, I create equivalents to the system operands that I need using the Socket Status Request #22 rather than trying to do it in the rung for Connect.

What protocol are you using?

Are you missing a MODBUS Configuration block, or is it just not visible?

PLCs hate being anthropomorphized!

I see them. Thanks for posting them!

That's a great idea. I wish Unitronics offered that standard.