-
Posts
3,275 -
Joined
-
Last visited
-
Days Won
239
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
Which elements are not being found under View / Operands Not Referenced in Project?
-
Post your code.
-
This is rare, but I've seen it happen, too. I do what you do - change something else inconsequential. The other alternative is to select Download All & Burn, but that is rather lengthy. I know Unitronics is aware of this as it was mentioned by the instructor in a training course some years ago.
-
Have you looked at the "Projected Memory Map" under the Build menu?
-
Hmmm, I was thinking of the Vision products. I agree that I don't see any applicable display System Integers. It does sound like a hardware fail, but you should check with Unitronics Support for any procedure they might have to troubleshoot. Just email with your problem description above to: support@unitronics.com.
- 1
-
In the top-left corner of the on-screen text entry keyboard are two arrow keys. Pressing one of them repeatedly will cycle through all the available characters.
-
Have you gone online and checked the value of the System Integers for contrast and brightness?
- 1
-
The "Numeric Password" would be a separate entry. Place an MB in the "Legal Entry"box then use that bit to SET another bit to be used to indicate a password has been successfully entered. You can then use the successful password bit to turn on or off a "Disable" bit for the entries you want to protect. To log out, RESET the successful password bit.
- 1
-
5 hours ago, thecarb said:
I mean 0 - 20 mili V.
I'd be very surprised if you can get anything meaningful on a 0-10V analog input from a 0-20mV sensor, especially if it is a 10-bit resolution input.
-
11 hours ago, barkergc1978 said:
So i need different blocks for the same output?
Absolutely not. You have two networks in each of ladder rungs 1, 2, 3, 8, & 9, and you have three in ladder rung 7.
-
I don't have an M90 handy to test your logic, but before anything else, break up your logic so that you only have 1 single network in each ladder rung.
-
I've wondered the same thing, @JohnR!
-
Pull the Snap-In module off and re-seat it. I've seen this problem occur when there is poor contact between the PLC and the Snap-In I/O. If you have an environment with some vibration, place some tape around the interface between the PLC and Snap-In module to help it maintain contact.
-
That's interesting, I've never encountered a V260. Is that a Vision, or Enhanced Vision PLC?
When you say "did not make a difference", are you saying the same motor still had the problem even when you switched outputs or switched wiring? Or did the problem move with the switch?
When you say you swapped out a V260 for the V560, are you using the same Snap-In I/O module after the swap?
-
I don't believe you can open the keypad without referencing a numeric variable because the input from the keypad must have a place to go. However, you can accomplish what you wish easily enough. Just copy the analog value into the numeric variable when switch = 0 and disable it. When the switch = 1, then re-enable the variable to allow keypad input.
-
Which PLC and VisiLogic version?
-
Does this PLC have a Snap-In I/O module?
-
2 minutes ago, masrellim said:
leads back to 3 things. length/type of wire between output and motor drive, a difference in how the snap in and expansion outputs work, or I have a difference in the programing of the 2 outputs that I can not see.
It would be easier to lengthen the shorter wire than shorten the longer wire, no?
Also, swap the Outputs in the program - just do a search and replace (thrice, move one set to a parking place, then move the other set, then move the parked outputs). This would be easier if you used buffered outputs.
That should point to or eliminate the last 2 of the 3 remaining options.
-
I'd love to look at your .vlp file in depth (thanks for including it, by the way), but I'm a bit bogged down at the moment. Let me suggest this until someone else can come along to help (or I can crawl out from under my deluge of work). Swap the wiring between the motors and/or swap the outputs in the program to try isolating the source of the problem and see what you get.
-
If the video system has digital inputs available or communicates with a protocol compatible with the PLC, then it should be simple. Otherwise, it might be more difficult.
- 1
-
Fortunately, VisiLogic makes it easy. Copy, paste, drag, and drop. You can break those nets up literally in seconds.
-
By the way, your picture shows horrible programming technique. That ladder rung could easily (and absolutely should) be broken up into 7 separate rungs. Do that and your compile error will go away. I can't account for why it seems to be allowing it elsewhere.
-
It's the latter. I just tested and VisiLogic still allows multiple networks in a single rung (don't do it, though), but doesn't allow multiple HMI calls in a single ladder rung. Perhaps an older version did allow it.
- 1
-
Also, I don't think you can have multiple HMI screen calls in the same net.
Find ALL unused elements
in We're Listening...
Posted
Well, that's frightening. I use that frequently and had no idea I was at risk of removing an operand that was in use. Not horrible, I suppose, since it's only removing the description. It sounds like there may be a bug in that routine.