-
Posts
3,263 -
Joined
-
Last visited
-
Days Won
237
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
You can't take the requirement for an SD card out of the program?
-
Didn't Unitronics get their start by developing automated parking garages? They had an elevator, of sorts, to move the cars around. I can't find that information on their website anymore, so perhaps I'm misremembering.
-
7 minutes ago, RickL said:
You can minimize the explorer in width, just don't close it!!
That's certainly interesting - and something to note, but why would you want that window closed??? It's very important and constantly needed when writing your program.
-
12 minutes ago, LeonMötter said:
The range we use is around 1X10E7 to 1x10E-8.
Seems like this is easily within the range of a 32-bit signed integer. It may be "easier" to work with floating point, but if they don't work then the harder path is necessary.
-
8 hours ago, Gianni said:
Is this download still available somewhere?
It's still right there in the original post - hasn't moved.
-
Is there any possibility to use integers with implied decimal instead of floating point?
-
Many of the Vision PLCs have a mini-USB connector. Which model are you working with?
-
28 minutes ago, RickL said:
......... is the --------(S)------- "set" need an assigned I/O in hardware config?
I'm sure the answer to this question is no, but I have no idea what you're asking.
-
I took a chance and opened up your file on my computer. No problem opening the file and it compiled without errors. The problem would appear to be with your PC or your VisiLogic installation.
That said, I have to ask, what the heck are you doing in ladder rung 15? Under most circumstances mixing Set coils and Direct coils in a program will not work as intended. And also, while it is permissible to use a contact and coil of the same bit in the same rung as a latch, this is not what you are doing. It looks like you should be doing something like what you have in rung 6.
Also, please do not place multiple logic threads in the same ladder rung (rungs 7 & 8). The compiler will not report an error, but it is extremely bad programming practice in ladder logic.
And finally, use subroutines to break your code up into manageable pieces. Personally, I reserve the Main Routine for Start-Ups, configuration blocks, and subroutine calls. All other logic should go in subroutines.
-
17 hours ago, Ausman said:
So....take MB3144 and TD81 out of the rung and see what happens, but I acknowledge this might upset the running ok in the first place.
I did exactly that. No change.
15 hours ago, kratmel said:I think that the solution to the problem lies in moving the location of the subprogram where the display is updated in the main program.
I had that thought as well. I changed the subroutine run order to reverse the operations. Again, no change. I had the subroutine where MB 3141 goes high coming after the subroutine where the HMI element is changed. I moved it to before so that MB 3141 going high and the HMI element changing occurs in the same scan, but the only difference it made was that I was unable to force MB 3141 high from VisiLogic while online. Strangely, forcing MB 3141 high while online does not cause the screen refresh, but forcing it high with TD 80 or with a test bit inserted into the rung did. What I'm not sure of is what exactly is the timing of the online interaction of VisiLogic within the order of all the scan operations.
I think both of you are headed in the right direction. I have a few more permutations to run through to narrow this down and I'll let you know what I find. Thanks for your help!
-
4 hours ago, draganjr said:
My question is can a MF be reset?
Sure, just use the Store Direct function and store zero to the MF.
You have to use the special Float Store Direct function under Math/Float/Basic...
-
Thanks for the suggestion, kratmel. I tried it and it didn't appear to change anything. It appears to not do it all the time, but when it does it looks exactly like an SB 31 screen refresh. I have isolated it to a bit of code:
MB 3141 (rung 20) will (in another subroutine) cause the HMI element to change. When triggered by TD 80 (or even a test bit placed in the rung), the screen refresh happens. But when I'm online and manually SET MB 3141, the screen refresh does not happen. It's consistent. I'm still working through all the possible permutations.
-
Bump. Any thoughts?
-
It also should be mentioned that programming all models of the Unitronics Enhanced Vision series is nearly identical. This includes your V350 and the V570 in the video I linked to, as well as the models used in the example projects.
-
Unitronics presents training webinars regularly which get posted to their YouTube channel. Browse those videos to get basic training on VisiLogic. Here's a link to one to get you started:
I'll also suggest that you browse the Help file in VisiLogic in addition to the example projects, as Joe mentioned.
-
32 minutes ago, Ausman said:
I give up!
Use a larger font next time! 😂
-
45 minutes ago, Ausman said:
Your experience is well worth noting if it enables remote firmware update on a plc that shows that it will only do an update via a direct serial line (onsite).
A .v57 file does not update the firmware. I tested by trying to download the 9.8.96 file from VisiLogic after and it still refused and wanted to do a firmware update. A .c57 file certainly does update the firmware.
Also note that I am not creating the file from ladder, but rather directly from VisiLogic using Project/Create Project Files:...
-
I've just discovered something interesting. Perhaps someone can explain it to me.
Let's say, for example, that I have a PLC (say, a V570) that has the firmware associated with VisiLogic 9.4.0, then I take a project created in 9.8.96 and try to download that file (using 9.8.96) into the older PLC, it will properly refuse and tell me the firmware needs to be updated first. However, if I create a .v57 file from VisiLogic 9.8.96, place it on an SD card and load it into the PLC from INFO Mode, it will download and run just fine. Why?
-
Okay, to answer your question, MI 812 has a Power-Up value of 1760. You can change the value by going online with VisiLogic or through INFO Mode and it will stay that way until the PLC is power cycled. If you change that power-up value in the VisiLogic software and download the change then try to overwrite all the operand values from a file, the operand values will revert to the (new) power-up value when the PLC is restarted.
- 1
-
8 minutes ago, MeriCummins said:
my edited project will have a new value for a variable operand (MI) full scale-is THIS an operand? In which case will downloading the originals (if necessary) overwrite the variable within the project that I just edited??
Yes, an MI is an Operand. The answer to your question depends. Which MI are you editing?
-
9 hours ago, RickL said:
Screen capture! I got now! : )
Yes, screen capture (alt-PrintScreen button), paste into Paint, crop, copy, paste into the forum. Quick and easy.
From your post above, note that the Reset Numeric block is equivalent to Store 0 and takes up less space (see where I used it in the post above yours).
-
Easy peasy:
I also provided a way to re-enable the toggle button.
-
8 minutes ago, RickL said:
including an additional set and resets to make the buttons look locked down
Why did you need additional set and resets? The button, when set as Toggle type, will look pressed when the bit is on and you can change the text and color as desired.
Regarding the MIs, I can't imagine why you need to use logic function blocks with bits, but it's simple enough to do the following (do this with each button):
-
To use buttons, as in your original post, is simple. Take your original logic, change the first contact to a positive transition, and change each button to be a Toggle button. It will look like this:
New to PLCs and need guidance
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Is your V1040 new, or does it already have a program in it? If there's already a program, it may have initialized COM1 as something incompatible with VisiLogic. Go into INFO Mode and check it. Also, screenshot your Connection window so we can see if that is set up properly.