Jump to content

Flex727

MVP 2023
  • Posts

    3,264
  • Joined

  • Last visited

  • Days Won

    237

Posts posted by Flex727

  1. 6 hours ago, yyh2 said:

     

    exm3.png

    There is nothing wrong with this. It should work perfectly every time. In my nearly 15 years of full-time experience using VisiLogic I've never encountered a software bug such as you describe.

    Also, I concur with @Fernando Castro - use ladder for HMI screen calls, not the Links & Jumps tab on the HMI screen. The primary purpose for that tab is for non-touchscreen PLC models that might need different physical buttons, or a specific subset of physical buttons, to make HMI screen calls from various specific screens.

  2. Yes, this is easy to do, but I can't help unless I understand your desired logic. What do you want to happen if there is a conflict between the HMI button and the input?

    I'll also add that you fail to understand how ladder logic works. If you're familiar with normal computer programming you will be led astray. A simple open contact with a direct coil is often thought of as an "If" statement - if I0, then O0 (looking at your top rung). But what most people new to ladder logic fail to understand is that the statement is incomplete. There is always the implicit statement: If Not I0, then Not O0. In your logic O0 and MB0 will always be in the same state as I0, irrespective of MB6 & MB7 (except for the single PLC cycle when they transition, which will be too quick for you to see).

  3. You cannot download a .vlp file to the PLC from an SD card. You must install VisiLogic (available free from Unitronics) on your PC or laptop, connect to the PLC using a programming cable or mini-USB (if available on the PLC), then download the program.

    It is preferable to use the same version of VisiLogic as used to create the .vlp file. There are also a lot of ins & outs to this process and you should probably seek some guidance from an experienced programmer.

    My recommendation is to send the PLC back to the manufacturer and have them perform the install. Seems pretty lazy to just drop a .vlp file on you and expect this to turn out well.

    You're welcome to PM me if you decide you would prefer to engage paid professional help.

  4. 18 minutes ago, DanT said:

    You may have to resort to an intermediate solution - Raspberry PI( for example)  to get the weather data, then Modbus the infomation into the V700

    What I have done when I must use a Vision PLC but need certain communications protocols not available in the vision line is use a UniStream USC-B3-R20 and communicate the information to the Vision PLC via MODBUS TCP, as Dan is suggesting. It's a little more expensive than a Raspberry Pi, but if you already know how to program the UniStream then it's really convenient. It will just sit on the DIN Rail alongside other components and works like a champ.

  5. 13 minutes ago, Fernando Castro said:

    I have seen that a lot of people "protect" their programs to charge for the additional services in the future, but not me ..for me is like Mr. Customer, you own this thing here is everything you need to know about it: diagrams, code, drawings help yourself.  (I don't want to be bother for each time a minor change will be made to the system that doesn't affect my part) and chances are that if there is a good relationship with Mr. Customer, he always is going to request more services anyway

    This is exactly my philosophy.

  6. 11 hours ago, RickL said:

    I don't know why this is , maybe a memory constraint of this PLC?

    No, the issue is the HMI display resolution on this particular PLC is 320x240. Unitronics makes higher resolution HMI screens on other PLC models that might suit you better. Further, The graphics and the programming software are both free. There is nothing preventing you from buying graphics from another source, or even creating your own. I do that frequently. Nothing forces you to use graphics that Unitronics supplies as a courtesy.

  7. I'm no expert on MODBUS, but I've found that the Slave ID usually only has significance if there is a conversion to serial somewhere in the pathway. If everything stays purely in the Ethernet (TCP, as opposed to RTU) domain then it can be ignored. However, there are a myriad of MODBUS slave implementations by various manufacturers and obviously their recommendations should be followed. I would say that in no case should multiple MODBUS TCP slaves have the same IP address. It looks to me, in your implementation, that you think that you can distinguish between MODBUS TCP slaves merely by Slave ID. You cannot do that.

×
×
  • Create New...