Flex727
-
Posts
3,259 -
Joined
-
Last visited
-
Days Won
236
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
Email support (support@unitronics.com).
-
Your error message says "No Application". It means what it says. You need to reload the application, either from VisiLogic or an SD card. This was likely caused by a power cycle with a dead battery. Unless you have a clone file on an SD card, you will need to reload the application and re-enter all user-configurable settings.
-
1
-
-
8 hours ago, benito.carrasco said:
I have updated the programming tool to the latest version, I get the message that the firmware needs to be updated.
Stop doing that. Stay with the VisiLogic version you originally programmed the software with. Unless there is a specific feature you require or a specific bug fix that has hindered you, do NOT routinely update to the latest VisiLogic version. PLCs are not like PCs where you always want the latest version of the app.
-
1
-
-
17 hours ago, Ausman said:
With your PLC being a 130, I respectfully disagree with Flex saying you can update firmware by ethernet. Software yes, Firmware no.
Correction noted, thanks. My experience with V130s is far less than with the other Vision models.
-
1
-
-
This is very confusing. The PLC never requires an O/S update on its own. In fact, we recommend that the programmer never update the O/S once the PLC is in production.
If your PLC will not boot properly when power cycled, then you have another problem that must be addressed. If you are periodically removing mains power and the program is lost, then it sounds like you need to replace the battery. I don't believe that causes the O/S to be lost, so there may be another issue at play.
All that said, though it's not recommended by Unitronics, it is possible to update the software and/or firmware via ethernet.
-
1
-
-
1 hour ago, user32767 said:
for some unknown reason you need to use 701 instead of 700
Likely because Unitronics starts their addressing at zero and the other device begins at one. This is a common issue.
-
1
-
-
5 hours ago, Sailor_Poon69 said:
After reading the forum, I've learned conditional subroutines should never be used.
Never say never, but in general it's bad practice. The reason is that it's easy to leave coils in "limbo" causing unexpected results. If you're very careful and know what you're doing it can work fine. That said, don't do it anyway.
5 hours ago, Sailor_Poon69 said:Should I simply call the subroutine in the main routine every cycle and add a switch or compare to every rung of my remap subroutine so it only activates upon a button press or MB compare+ state change to disable.
Yes, this is the proper way, IMO.
-
7 hours ago, MarvinP said:21 hours ago, Flex727 said:
There is an entire forum here on this board dedicated to this question.
https://forum.unitronics.com/forum/61-best-programming-practices/
Thank you for the link! I checked it out and it seemed to go deeper into smaller bits of best practices instead of creating a baseline from where to restructure my program. I can't really seem to find a answer to problems I currently am encountering, but I will post a question in this forum if this is more appropriate.
I hope you caught this message:
-
There is an entire forum here on this board dedicated to this question.
https://forum.unitronics.com/forum/61-best-programming-practices/
-
1 hour ago, DanT said:
There are limits to the number of -|P|- and -|N|- that can be used in a program
As Dan correctly points out, transition contacts are limited in your PLC program. The reason for this is that in order for the transition contact to work properly, memory must be set aside to "remember" the state of the bit operand on the previous scan. The size of the block of memory set aside for transition contacts varies by PLC model from 256 to 1024, but sometimes the actual compiled number of transition contacts is greater than what you can count in ladder due to the result of the STL translation from ladder that actually gets compiled.
-
The .vlp file typically does NOT have the operational parameters you're looking for.
-
On 11/10/2016 at 9:48 AM, Joe Tauser said:
Look in the Help on "Data Table Find"
4 hours ago, Ravi said:Can I get a Sample coding for Data Table find in Visi Logic.
Did you review the Help entry as Joe suggested? It is very clear and performing the action you need is very simple.
Please keep in mind that this is a user forum staffed by volunteers with actual full time jobs. This is not official Unitronics Support.
-
I've seen this in the past when the Snap-In module works loose. Be sure it's snapped in tightly and consider a bit of duct tape to hold it tight. This is especially a problem in a high vibration environment.
-
You can find the IP Address in INFO Mode (see the Help file for more information). However, if this is a new PLC that does not have a program in it, you are better off connecting with a USB cable until you get a program downloaded that has Ethernet initialization and IP Address assignment.
-
16 hours ago, Ausman said:
I don't use unilogic
Aus, UniLogic is a totally different beast when it comes to button presses. In VisiLogic, pressing a button activates the associated MB. The MB is on for as long as the button stays pressed and turns off when the button is released. It doesn't work that way in UniLogic. Button presses can have a variety of "Actions" associated with them and there is no action that performs like a button press in VisiLogic. If you want the button to behave the way it does in VisiLogic, then you Set the operand on press and Reset the operand on release. This is totally independent of Set & Reset you are familiar with in ladder.
-
Copy the VisiLogic folder (in the C:\Windows\Program Files (x86)\Unitronics folder) of the 1st instance (the one that is currently working) on top of the VisiLogic folder of the 2nd instance (the one with the error message) and allow all the files to replace or copy over. That should solve your problem.
I keep a working copy of every VisiLogic folder (I have 23) on another drive ready to replace any corrupt VisiLogic folder at a moments notice. I haven't seen the exact error you're experiencing, but I've had my share over the years of corrupted VisiLogic files and this is the best solution I've found.
-
10 hours ago, Cara Bereck Levy said:
Hi--sorry for the lag in answering!
I think we can cut you some slack. You've been...busy.
-
10 hours ago, Joe Tauser said:
I intentionally used that word and I was actually ready for PC blowback, as PC is one of my highest irritations.
Figured I could trigger you with that comment. 😉
-
7 hours ago, Joe Tauser said:
The "Modbus" device I am reading data from is retarded
Now, now, now, Mr. Tauser. We simply must replace that word with "intellectual disability".
Your "Modbus" device is intellectually disabled. Now isn't that better?
🙊
😂
-
42 minutes ago, DanT said:
Linearization in the Screen Number box is limited. Applies to the Display Only. ( see Help)
Unless I'm misunderstanding, not exactly the case. Here is an example that allows the user to enter a number from 0-100% at the HMI and the MI (presumed attached to a 12-bit 4-20mA analog output) will be linearized to the correct value:
-
-
I will email you directly. If my email doesn't reach you, please feel free to PM me on this forum.
-
I just tried it and it downloaded fine. What's the problem you're having?
-
15 minutes ago, Gabriel Franco said:
Electrical noise also can cause it. I´ve had a couple of machines suddenly loosing all or some parameters and only after doing proper electrical isolation did solve the problem.
I've experienced this as well.
Is it possible to "ignore" UniStream PLC Uni-I/O hardware configuration?
in UniLogic Software
Posted
Just change the PLC model in the program temporarily to test, then change it back. I don't program UniStream very often, but it seems like I've done this successfully in the past.