Flex727
-
Posts
3,325 -
Joined
-
Last visited
-
Days Won
241
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
8 minutes ago, Al. said:
For deleting variables in the subroutines and displays, I did it manually and made sure that the variables are removed (MB initialized ; MI, ML, T set to 0 ; etc.). it was long and tedious but now it is fine.
Why did you feel that was necessary? All you're deleting is the descriptor text that the PLC never sees anyway.
If you have a bunch of operands that are no longer being used and you find the descriptor text annoying, you can go to View / Operands Not Referenced in Project. That will generate a list that you can delete from.
-
2 hours ago, Al. said:
I have another question if you would answer : is it possible to delete a variable everywhere in program in "one click" ?
Because for the moment I search for the occurence of the variable in question and I delete every call to make sure that the variable is removed, initialized and then available.
Sorry, I have no idea what any of this means.
-
2 hours ago, Al. said:
So I need to delete every call relating to subroutines and displays.
No, you only need to delete calls for the specific subroutine or display you want to delete. As CAM said, they are easy to find.
-
Your reply is unclear. Try deleting any entry into the Disable View function, download the updated program into your PLC, and then tell us what happens.
-
Have you checked to see if MB 83 is on when the buttons aren't working?
-
You must delete the reference to the subroutine or display first. For instance, if the subroutine is called in ladder that subroutine call must be deleted first before you can delete the subroutine. Same goes with HMI displays.
-
You need to show the variable box opened so we can see the details.
-
Without more information it's going to be difficult to be of any help. Post a screenshot of the open HMI Variable box.
-
There are Clock functions in the Utils drop-down menu. They will do what you are looking for. There is also a lot of good information in the Help file under Clock Functions.
-
Can you post your program?
-
Nice work, Joe.
-
2 hours ago, Ausman said:
why didn't anyone pipe up during recent asks about "how to get all info out of the plc into a new one?
Because it can't be done without the Set SD Password FB pre-existing in the program.
-
7 hours ago, Saragani said:
You can clone directly from the PLC itself in a Vision PLC.
If you have a Set SD Password FB in the program.
-
My guess is that there's a mistake in the VisiLogic software that embeds the version code in the project file when first saved. They probably forgot to update that line of code. However, there's different code that UPDATES the project file to the new version when an older version is opened. That code is correct, so once the file gets opened the second time and saved it finally has the correct version code embedded in the file.
That's my theory anyway.
-
This happens to me with 9.8.65 every time I create new and save. It only happens the first time I open after the first save. I notified Unitronics about it and presumably it was fixed in 9.8.79, but I haven't tested it.
Oddly, my version code is totally different:
-
Just to be clear, in order to lose data, both the battery must be dead AND the 24v power must be disconnected from the PLC. EITHER the battery or the 24v power supply will maintain all data. You can replace the battery with power connected without losing data.
-
I'm not sure why you posted this topic again since you are getting a lot of responses and help here, but I deleted it.
On 3/26/2019 at 7:36 PM, Flex727 said:You have a hardware or electrical noise issue causing your problem.
You say there is no VFD, which can be a likely source of electrical noise - that is not to say there isn't a source that you'll need to track down. Electrical noise can really be a pain to troubleshoot, but that is what you're going to have to do. If you think there is no chance this is electrical, then you might want to start swapping out hardware components. You can also remove your PLC from the current environment and let it run for awhile on your office desk. No Fatal error likely means some electrical problem in your panel.
Joe Tauser is probably the best expert on this forum and you haven't provided the schematic he asked for.
While my suggestion about the re-seating of the Snap-In module (I've seen a poorly seated Snap-In module cause this exact fault) may not solve your problem, you don't say whether or not you actually tried it. A photo can't reveal proper seating of the module.
-
Using the Unitronics SD Card Explorer application, you can read the SD card in any manner that you use to connect to the PLC. with VisiLogic. The communications setup is exactly the same.
-
Thank you for replying back with the resolution to your problem. Glad you're back up and running.
-
Your program is a bit of a mess. You cannot communicate with two different devices over MODBUS IP using the same Socket unless you specifically disconnect from one before connecting to the other (and waiting for the fairly lengthy time for the disconnect and connect to properly occur. But with 8 Sockets available, there is no need - use two different sockets.
Also, do NOT place two logic networks in the same ladder rung as you have in rungs 8 & 12.
Make sure the IP addresses and Port numbers are properly aligned between Master and each Slave.
Your logic appears to disconnect from the slave instantly upon connection (and in the same PLC cycle!). That can't possibly work.
Please be sure all the operands in use are labeled if you want someone else to review your program. It's unnecessarily difficult without labeling.
And this is just a guess, but you seem to be writing your program like your PLC is a computer, which executes each step of the program sequentially from beginning to end with each step completing before the next step is executed. A PLC is different - it's a loop. The PLC does not interact with the outside world, or even its own I/O until the entire program loop has been completed. The basic execution in a PLC is as follows (one scan cycle):
1) Read all inputs
2) Execute ladder
3) Write all outputs
4) Repeat infinitely
There are more complexities, but this is the basic cycle which you must keep in mind while writing your program.
-
1 hour ago, JohnR said:
I see the Store Direct under Math/Float/Basic functions, but (unless I'm missing the obvious), you can't do vector functions with MF's.
I was talking about Store Indirect, but you are correct that you can't do that with MFs. Not sure why.
It looks like your solution may be the most straightforward way.
-
Moved to the correct forum.
-
12 minutes ago, Ausman said:
Flex's answer is correct
Yay! I'm 1 for 1 today!
-
Can't you just use a vector of the 6 MFs? Store the new value using an indirect address for the MF, increment that indirect value, then sum and divide for your moving average. This should work fine if you only have 6. If you have a hundred or a thousand values to average, I have developed an elegant solution for that, but it's only an approximate calculation.
Vision 700 HMI Variable Issue
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
There is no internal PLC command of that nature that I'm aware of. You might want to contact Unitronics Support and see if they can help.