Flex727
-
Posts
3,276 -
Joined
-
Last visited
-
Days Won
239
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
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?
-
12 hours ago, Joe Tauser said:
...to let the system catch it's breath.
PLCs hate being anthropomorphized!
-
Just now, PaulK said:
Are the pictures visible?
I see them. Thanks for posting them!
-
1 minute ago, PaulK said:
I was actually looking at adding the 4 holes in the snap IO (yes...void the warranty) and add some self tapers to hold the IO snug.
That's a great idea. I wish Unitronics offered that standard.
-
I still say it's vibration with the Snap-In module. I've seen it happen more than once and I got those exact same errors.
-
In the first picture (rung 5) you are checking the status of Socket 1 (Initialized, but not connected). You might want to do the same in the V700 using Request #22.
In the bottom picture you seem to be checking the status of Socket 0 (rung 6). Not sure why.
Changing over to the V700 shouldn't be a big mystery. Unitronics has clearly labeled the System Operands that no longer apply and provide a function that replaces those operands. Otherwise, everything works the same.
-
That date is the firmware date. not the current date.
It's possible that your V200-18-EB6 Snap-In module is vibrating loose and losing its connection with the PLC. Either replace it if it's old and/or press down on it securely and run some tape around it to hold it in place.
-
You're piling too much stuff into one ladder rung. I've never tried to perform MODBUS Config before Socket Init, but it is likely important to perform the Socket Init first. Your ladder rung loses control over that order execution. Try breaking that rung into 3 or more separate rungs.
I'll repeat something I've said before - Unitronics WILL NOT charge you by the rung. Break your code up into the basic simple instructions for both readability and to have more certainty that the code will compile the way you think it will.
If that doesn't solve your problem, then you need to post the internal workings of each of your function blocks or post your .vlp file here.
-
I've never done it, but I thought you could run a full-blown webserver off the SD card in the Vision line.
No question though that UniStream is more powerful in that regard.
-
1
-
1
-
-
8 hours ago, Joe Tauser said:
Make sure your OS is updated.
I recently had a V570 that wouldn't communicate over Ethernet. I swapped out Ethernet cards with a known working card (and several other troubleshooting steps) and still no worky. Since then I began using VisiLogic 9.8.64 and updated the firmware on the PLC to the latest. Now it appears to be working. We shall see.
-
Did you install VisiLogic "As Administrator"?
Do you run VisiLogic "As Administrator"?
Does it do this when you open other projects, or only this one?
Is this a new problem (i.e. was VisiLogic running fine and then suddenly developed this problem)?
Which version of VisiLogic?
Visilogic Timers
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Looks good. Does it work the way you expect?