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
-
-
Ah, step 1 will get you every time!
I always create a new subroutine for some function and then forget to add it to the Main routine. -
No reason the operator has to enter in any numbers - just have a button or spot on the screen for each hole position (use binary text element, with "toggle") and have the operator touch each position that will have a hole. At each position if the bit is on (has been toggled by the operator), then the hole is punched. Reset all the buttons at the end of the metal strip, or as each hole is punched as a visual indicator of progress.
-
I routinely code for systems with simultaneous multiple masters using MODBUS IP over Ethernet and Vision products. I've never had any issue even when the slaves are also masters to different PLCs. My systems get a bit complex due to the 4 socket limitation and I've created all kinds of crazy situations to shuffle data around to all parts of the system. One difference is that all my PLCs are always on the same subnet - I don't have any experience connecting across different subnets or across the internet.
-
I've had something similar happen on several occasions. The following procedure has fixed it for me:
1) Download a blank project to the PLC.
2) Initialize and Reset the PLC.
3) Download your project.
It seems that somehow the memory space for the images can get corrupted. Downloading a blank project clears that out and then when you download your actual project all will be well.
-
Rest assured the Timer function works properly in Unitronics PLCs and software, though it's a bit different than other popular PLC programming software. When I'm troubleshooting this type of problem here is what I do:
1) Confirm the subroutine with the Timer Coil is being called by the Main Routine.
2) Confirm the activating contact is actually ON (and stays ON). Go online with the PLC and check that the MB is SET.
3) Confirm that only one instance of the Timer Coil exists. Right click on the description box and select Find.
4) Confirm the Timer value while online with the PLC by clicking on either a Timer contact or coil.
If you do all this and the timer is still not working properly, post the code here and someone will look at it.
-
I find it works better to click and hold for half a sec rather than click multiple times.
-
2
-
-
Wouldn't it be more straightforward to trigger a 5 sec Extended Pulse Timer (TE) with SB2 and then use that timer's contact to trigger Output 0?
-
SB2 is the POWER-UP bit - is that not working for you?
-
Show 300 (minus) "weight from scale"?
-
Yes, Cara, I know re-engineering VisiLogic is not really feasible. That's why I was a little hopeful that it might be easier to just create a vision compiler for UniLogics. Sure, compilers aren't easy as pie, but people create compilers for multiple platforms all the time. Makes no difference, I said this many times before, Unitronics has the best PLC programming environment in the business - I wish everything in my life worked as well.
-
I participated in yesterday's Webinar on intro to UniLogic software. Holy cow is that an improvement over VisiLogic! I understand that this programming software cannot be used for the Vision products, but I wonder if it really is that difficult to include a compiler for Vision products or is this a marketing decision to encourage adoption of the new product line? Our company has a solid platform using Vision and moving to the new line is probably not in the cards for now, but I sure would like to be programming in UniLogic.
Anyway, I would like to congratulate you on the development of UniLogic. It really looks like you managed to incorporate most of your customer requests for updates to VisiLogic.
-
1
-
-
Thanks, Cara!
-
If the value is large, shouldn't you be using ML instead of MF?
-
Thanks, HighTech. I tried to upload an image, but this forum is restricting me to a max file size of 11.04KB. I shrunk it to near unrecognizable and it was still 43KB. Perhaps you can pass along a few general tips or maybe Cara can explain why there is such a small file size restriction.
-
1
-
-
This question was asked by someone in a different forum and needs to be answered - I thought it might be more appropriate here.
With the advent of UniLogics, does that mean that software development has ended for the Vision products? Should we consider the possibility of a PLC simulator, online editing, upgrades to the VisiLogic software, and all the other requests and improvements suggested in this forum to be dead now?
If development hasn't been totally ended, I presume the list is now very much shorter. Can you provide that short list?
-
I've never gotten an answer to the question as to why the Vision PLCs were limited to 4 simultaneous connection (4 available sockets). Is it hardware or software? And since it was so definitive with the Vision PLCs, why don't you have a definitive answer with the UniLogic PLCs?
-
Thank you!
-
I must have been thinking about the other direction. I don't think you can convert color to monochrome. Thanks for the correction, Joe.
-
There is no conversion program that I know of. All your ladder code can be copied directly into a new project for a V570, but, based on my experience, you will have to develop new HMI graphics for the color screen. Also, if you were using the keyboard pushbuttons on the V280 panel, you will have to update that logic and design the HMI user interface for input by touchscreen rather than the pushbuttons. I'm not sure, but you may have to make some modifications to the I/O. Good luck!
-
Thank you for the great response, Joe!
-
Can someone write a paragraph or two about UniLogics? What I primarily want to know (something press releases seem to never address) is why I would want to use this over the other Unitronics offerings. What are the advantages? Are there any disadvantages? Are there significant differences in the programming software? Any limitations we had before now being alleviated (for example, 4 sockets for IP communications, etc)?
Another thing I'd like to know, have the problems associated with higher resolution screens been addressed? I've been working a lot recently with the V1210 and have been struggling with the extreme slowness of the Visilogic software when attempting to edit complex HMI screens and also the PLC itself exhibits obvious indications that the processor can't keep up with manipulating 480,000 pixels (slow response and slow screen updates).
-
You can Initialize & Reset from Visilogic if you are online with the PLC by going to Connection / Communication & OS / then 2nd tab over.
Not sure about initialization, but you can reset the PLC with ladder logic by forcing SB300 high.
-
It's rare that you would need to program a loop on a PLC - the whole concept of the PLC operation is one big loop. Just put a contact in that indicates the condition you are looking for and it will activate when that condition is met.
If you already know and understand this, then I apologize, but it's important to know the fundamental operation of the PLC, which is as follows:
1) Read the INPUTS.
2) Execute the ladder code.
3) Write the OUTPUTS.
4) Repeat until Heat Death of the Universe.
-
Visilogic is buggy when used with high resolution screens. I'm using a 2560x1440 monitor on my desktop and Visilogic does all kinds of strange things it doesn't do on my laptop (both use Win7-64 bit).
I always create a new subroutine for some function and then forget to add it to the Main routine.
Timer forward / Reverse
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Under the "Store" dropdown, you will find "Load Timer/Counter Current (and Preset)" and "Store Timer/Counter Current (and Preset)". Use those to move the value into an MI or ML, do whatever math you need to and then move back to a timer (same or different one). Bear in mind that the value you receive will be in units of 10ms so anything over a few minutes must go into an ML.