Flex727
-
Posts
3,275 -
Joined
-
Last visited
-
Days Won
239
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
4 hours ago, thecarb said:
...and 1 oxygen transducer with 0-20 mV output.
Do you mean 0-20 mA or 0-10 V?
-
Joe Tauser was kind enough to educate us all on this topic and wrote a very nice example program, which can be found here:
-
1
-
-
I know that @Joe Tauser would recommend a State Machine, and I would agree, but there is no reason you can't do it exactly like you would in S7 using ladder logic. You can SET and RESET bits in VisiLogic in any way you see fit.
-
Wow, what an ordeal! Glad you got it working.
-
On 5/19/2017 at 9:11 AM, cmarcus said:
If I do File/Open and select any other files they seem to open.
Does that include the backup of your corrupted project file? If so, I'm confused as to what your current problem is.
-
Thanks for letting us know you got it solved.
-
1
-
-
Do you have a backup of the file you were working on? If not, try copying your file to a different location on your hard drive - a location with less subfolder nesting, then try opening it. If you are still getting the error and other projects open fine, then the problem is almost certainly with a corrupted project file, not a problem with your VisiLogic installation.
When working with mission critical files, whether VisiLogic or other software, I always keep daily backups and multiple versions saved. I strongly recommend creating a system to mitigate this type of problem as file corruption can happen at any time and with any software.
-
I think you are probably correct in your assessment. If you have Windows Restore enabled, you might try using that to go back to the day before the incident.
-
When you uninstall VisiLogic, make sure ALL the files from the previous VisiLogic installation are deleted (except project files, of course - move them elsewhere). Reboot the computer then install VisiLogic AS ADMINISTRATOR. Then when you run VisiLogic, make sure you run it AS ADMINISTRATOR (every time).
If the problem still exists, then follow the instructions on the error message and contact Unitronics Support (Edit - I see you already did that).
-
Also, do a search on the tag, "Control stick pos..." to make sure you're not assigning it a value anywhere else in the program.
-
1
-
-
Yes, you can connect to two different PLCs without connecting/disconnecting manually. In the master, you just need two ladder rungs, each with a socket connect FB, making sure to have the correct IP addressing in each. Then you need two separate data exchange FBs, one for each PLC. It works best if you have a polling timer, rather than trying to execute the data exchange on every single PLC cycle. I usually use a 100ms timer. Also you need to initialize both sockets with the correct protocol and port number.
Make sure the Port numbers match between the master and slave for each socket. Go through every FB you're using and make sure all the IP, port numbers, and socket numbers are correct - it's easy to miss a setting.
By the way, when others mentioned connecting/disconnecting manually, they didn't mean anyone has to be physically present. It just meant performing a disconnect in the ladder logic to one PLC and then connecting to the other rather than simultaneously connecting to both. This is rarely done but is sometimes necessary when connecting to more than 4 PLCs since there is a physical limitation of 4 sockets with the Vision PLCs, except for the V700, which can have 8. The UniStream is basically unlimited.
-
22 hours ago, Flex727 said:
You must use two different sockets to connect to two different PLCs.
I will amend this to say, "You must use two different sockets to connect to two different PLCs at the same time without disconnecting and reconnecting (as Ljuba was trying to do).
-
You must use two different sockets to connect to two different PLCs.
-
1
-
-
bbird suggests a good workaround. I fully understand the issues with binary-decimal conversion, but I've personally never seen the problem you experiencing. I would request that you post the rest of your code and let's take a look.
-
Make sure you're not overflowing your Memory Integer. Just to be sure, use MLs instead and see if the situation improves.
-
It seems to me that you could account for the reset of the PLC with the proper math at startup. SB 2 is handy to execute some instructions on the first PLC cycle only.
Unitronics personnel often browse these boards, but I recommend emailing support@unitronics.com if you want to be sure you get some immediate help.
-
This is likely due to the USB-to-serial driver issues.
-
Is it possible for you to use a State Machine instead of recipe drum?
-
Since the PLC RTC is being synchronized with an external clock, why not create your own SBs based on the RTC? Run a 10 or 100ms timer that indexes a counter that gets reset by the RTC seconds.
-
I've let this run for hours now. MI 19 hasn't budged (though it changes at each reset), but MI 21 still bounces around randomly.
-
Just a data point for you:
I didn't have a Samba readily available so I downloaded into a V700. My scan time is less than 1ms. You are correct that there is some variation exhibited with MI 19 & MI 21. I am seeing MI 19 sitting at 4 with no variation and MI 21 is ranging from -3 to 4. MI 19 seems stable and MI 21 seems to jump suddenly to a new value after sitting at a value for some length of time.
Based on your code, I would expect MI 19 to be 0-9 (depending on where the RTC is at power up), and indeed I see it at a rock solid value that is different each time I reset the PLC. I would have to give some thought to MI 21 to understand why it seems to be jumpy.
By the way, I deleted the Store to SI 0 before testing on my V700.
-
Why are you trying to write to SI 0?
-
For MODBUS addressing, go to the Help file in VisiLogic, click on the Contents tab, then expand the following: Communications / Communications FBs / MODBUS, then select any of the topics you need to read up on. For addressing from an external MODBUS master, select Slave Addressing.
-
I've never had to deal with the kind of clock accuracy you're needing here so this is interesting. I can't imagine that SB 15 would be based on anything but the RTC, so in theory they should be exactly the same. However, I would ask what is your Scan Time (SI 0)? You must keep in mind that the PLC communicates with the outside world only once per PLC scan. A lot can happen during that scan. You might be able to overcome this to some extent by using interrupts and immediate reads and writes.
Also, in my experience, the built-in PLC clock is not usually an extremely accurate clock. They drift pretty rapidly.
Error 1012 Illegal NET
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
You have two networks in a single ladder rung. That is a no-no. Perhaps VisiLogic has changed that from a Warning to a Critical error in later versions.