Flex727
-
Posts
3,273 -
Joined
-
Last visited
-
Days Won
239
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
The new feature in VisiLogic involving Restore Points is nice, but it needs some work:
1) Provide a way to turn the feature off completely if the user doesn't want or need it.
2) The Restore Points apparently take up significant memory because I keep getting messages to delete some. Make that automatic - the oldest ones need to roll off automatically.
3) Allow the shift or control key to be used to select more than one Restore point for deletion. Deleting each of them one at a time, with the confirm prompt, is a pain.
-
4 hours ago, Cara Bereck Levy said:
Live Update from the Web will download the fixed OS 4.10.46.
Okay, that's quick and easy, but I wasn't having any problems. What was the specific bug?
-
12 hours ago, Cara Bereck Levy said:
It should be doable--I need to give a definition to the team.
Is this really doable (in terms of time an effort needed by the people who maintain VisiLogic)? I feel like this is asking for the moon.
I'd much rather get direct copy and paste between two instances of VisiLogic.
-
4 hours ago, Cara Bereck Levy said:
Our team tracked down thisV700 Modbus TCP issue bug, which is indeed related to the OS version released in mid-December 2021, 4.010.34 .
@Cara Bereck Levy, could you be more specific here? I don't have any VisiLogic version that includes 4.010.34 for the V700. My 9.8.94 has 4.010.36. Does .36 also have the bug?
-
Yes, not sure how to implement in practice, but as I see it, if an operand is already in use in the receiving project *and has a different description* the importing operand should be reassigned to an unused operand and retain the description.
-
1
-
-
12 minutes ago, Buzz_nz said:
Maybe Unitronics could add an image/drawing to the docs for the V100-17-CAN module showing the orientation. This would leave no doubt regardless of the polarity protection?
This is absolutely needed. @Cara Bereck Levy, is this something within your purview?
-
5 hours ago, vken said:
I need also the bin and boot files that support the VCO00401036_V1040. and reload them all from the begining. doing that it might solve the problem.
Those files come with the VisiLogic software installation. VCO00401036_V1040.UOS came with VisiLogic 9.8.94. All the files you seek are in VisiLogic installation folder, however, you just need to startup VisiLogic, confirm you can go online with the PLC, then have VisiLogic install the firmware.
15 hours ago, vken said:the only thought that i cannot execute because i'm missing files. is to roll back everything. find visilogic v.9.8.80 where is the last project backup and all the plc system files that response to that but I don't have them.
Install VisiLogic 9.8.80 and you'll have all the firmware files you need. If you opened a 9.8.80 project with 9.8.94, VisiLogic should have automatically saved a version of the project with the file extension .1.154 (instead of .vlp). Change that file extension to .vlp and you have the previous version as it was before you changed to to 9.8.94.
-
6 hours ago, kratmel said:
At the beginning of my work with Unitronics, I read a message from Flex that the most correct is to use the controller firmware with the version of the Visilogic program in which it was created and burned. To do this, Flex has a set of versions with the ability to quickly switch.
Updating PLC software and firmware to the latest version needlessly is one of my pet peeves. One should never do this!
3 hours ago, vken said:you are right but i never thought that when got the new laptop to install the old software!
Software and firmware version control is critical when working with industrial components. Always check and never upgrade unless there is a critical need. Further, always keep a backup copy of any previous version before upgrading, if that does become necessary.
-
1
-
-
It's difficult to follow your logic flow without the actual program, and also because it seems confusing. I'll offer this to start: you seem to be confusing two different types of latch circuits which overly complicates your logic.
I've rewritten your Main Routine ladder rung 2 in two different ways. Either can work but you might choose one over the other based on other program requirements. The top (rungs 1 & 2) use Set & Reset coils to latch MB 13. The bottom (rung 4) is a standard latch circuit without Set & Reset coils. Your logic combines them weirdly and I don't know what the result would be without spending more time than I would like puzzling through it.
-
11 hours ago, Dermie said:
I have tested the download today and it worked with out a problem. I extended the time out time to 4 sec, increased retry’s to 12, ensured no remote access from mobile and and changed the sb168. The plc now has a copy of the software burnt in flash.
@Ausmancomes through again!
-
6 minutes ago, Ausman said:
Does this mean the entire download problem is solved?
I think he meant the compile error regarding SB 168 was solved.
7 minutes ago, Ausman said:MB51...if you want things to run all the time, you simply connect them direct to the left hand of the ladder, possibly in series with other elements. In your case I would say that MB51 is totally unnecessary.
He mentioned trends which IIRC has an activating bit in the trend definition. @Dermie, just Set MB 51 in Power-Up and you'll be fine, though there's nothing really wrong with the way you did it (though you don't need the SB 1 there - you are allowed to just hang a coil off the left rail). You might also check to see if an SB is allowed in the trend definition and just use SB 1 there. VisiLogic doesn't allow SBs everywhere it allows MBs though.
-
1 hour ago, Fernando Castro said:
to my surprisse, when upgrading the OS my Modbus communication stopped working!!. so I rolled back to my previos well known version and modbus worked again!
I just checked this with a V570 as MODBUS Master and a V1210 as the MODBUS Slave using port 502 and VisiLogic 9.8.94 with the upgraded firmware (by necessity). It all worked perfectly. When I get more time I'll dig out two of my V700s and try that (I just happened to be working a V1210 project so that PLC was hooked up and readily available).
-
2 hours ago, Fernando Castro said:
also I have spoted some "bugs" on v700 software
As a heavy user of V700 PLCs, I sure would be interested in your findings.
-
1
-
-
22 minutes ago, John_R said:
A quick check of Remote Operator connected to a PLC via Ethernet, results in a message "Info Mode not yet supported in online mode".
Thanks for the info. I thought I might be misremembering.
-
34 minutes ago, Javier Galaz said:
Don't know, when I tried to go to info mode from visilogic using the "Online Test" it simply says, "No can't do" xD
VisiLogic uses "Remote Access" - try using "Remote Operator" (a small stand-alone utility that Unitronics provides). I can't recall off the top of my head, but it seems to me that Remote Operator will allow access to INFO Mode, but it's been a long time since I tried that and I may be mistaken.
-
23 minutes ago, Javier Galaz said:
I've perused this program and see no relevant difference to my software.
Yep, it looked to me like your program should work also.
23 minutes ago, Javier Galaz said:Until then, THANKS VERY MUCH guys, you've been so helpful and nice It has been a really lovely experience for being my first time here.
We try, but I wish we could have solved your problem.
-
35 minutes ago, Javier Galaz said:
I'm remoting this unit through a field computer connected through usb.
This is confusing to me. What is the USB connection? Between what & what? What is the full path of connection to the PLC?
-
10 minutes ago, Javier Galaz said:
Do you have a working program that I can test?
I can't send you a whole program, but here is the part that matters.
-
23 minutes ago, Ausman said:
I know I'm a dumbo on this sort of thing, but one difference I see b/n the example and this project is that there is no Slave TCP address reference in the IP config area. In the example there is. Does this matter?
No it doesn't. That's only used when the PLC is a MODBUS Master.
-
2 minutes ago, Ausman said:
I'm assuming you've tried a different network ID other than 255. I don't use TCP for modbus but this looks odd. Someone explain the 255 ID use to me in this case
To the best of my knowledge, the network ID is not used for MODBUS TCP. I've always just left it at 255.
3 minutes ago, Ausman said:And Joe, I only have 8.65 as you mention, but by trying to open the file I get an error message and things close on screen, you then have to go to task manager to actually end the task, double click the project again and up come other messages along the way to opening the project ok. This has always been my consistent way to read later version projects.
That did not work for me going from 9.8.91 to 9.8.94. It used to work for earlier versions.
I'm hoping 9.8.94 fixed some of the glaring problems with 9.8.91 and will be trying it out on my next major project.
-
Just as a data point, I have used V700s as MODBUS TCP slaves on port 502 for SCADA systems many, many times without incident, though not using 9.8.94 - mostly 9.8.65, as mentioned by Joe.
-
Did you confirm in INFO Mode that the Socket was actually set to port 502?
-
2 hours ago, Javier Galaz said:
So, if I understand correctly, if I use this:
like this
I would get Modbus port in port 502 instead of 20258 which is the default?
Yes, that is correct.
-
2 hours ago, Javier Galaz said:
In the help, the page that Kratmel pointed out: "Vision700 - Using Ethernet". At the bottom to be more precise.
Thanks. Oddly, that does not appear in my version of the Help file that came with VisiLogic 9.8.94, nor is the operand description in the operands list in VisiLogic.
Vision Activation?
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Howdy!