Jump to content

Flex727

MVP 2023
  • Posts

    3,276
  • Joined

  • Last visited

  • Days Won

    239

Posts posted by Flex727

  1. Two lines of code to change the PLC name, and you should already be keeping track of time of day, or whatever the criteria is for the different report folders. This sounds like an incredibly simple workaround for now.

     

    If you find that you need to regularly remote in, then use 3 names. Change the name immediately before writing each of the two reports and immediately change it to a third name after writing is complete. The PLC will have that 3rd name 99% of the time for you to remote in.

  2. Is there a table somewhere that lists exactly what firmware files are associated with each version of VisiLogic?

     

    I have a clone file for a V1210 that was programmed with VisiLogic 9.4.0. When I try to load that file from the SD card into a V1210 that has had the firmware updated with VisiLogic 9.7.24, it just crashes. Will I be successful if I revert the V1210 to the firmware from 9.4.0?

  3. It's too quiet here in Unitronics-Land, so I'll add this...

     

     

    A young Programmer and his Project Manager board a train headed through the mountains on its way to Wichita. They can find no place to sit except for two seats right across the aisle from a young woman and her grandmother. After a while, it is obvious that the young woman and the young programmer are interested in each other, because they are giving each other looks. Soon the train passes into a tunnel and it is pitch black. There is a sound of a kiss followed by the sound of a slap.

    When the train emerges from the tunnel, the four sit there without saying a word. The grandmother is thinking to herself, “It was very brash for that young man to kiss my granddaughter, but I’m glad she slapped him.”

    The Project manager is sitting there thinking, “I didn’t know the young tech was brave enough to kiss the girl, but I sure wish she hadn’t missed him when she slapped me!”

    The young woman was sitting and thinking, “I’m glad the guy kissed me, but I wish my grandmother had not slapped him!”

    The young programmer sat there with a satisfied smile on his face. He thought to himself, “Life is good. How often does a guy have the chance to kiss a beautiful girl and slap his Project manager all at the same time!”

    • Like 1
    • Upvote 1
  4. I have to backtrack on my conclusion here. The MODBUS Read Registers was working all along, but often took several minutes to update. After eliminating all the Read Coils operations by packing the bits into registers, I ended up with 7 lines of Read Registers - all but one was an array. The total number of registers being read was 33. This should be a very simple and quick operation, but one or more registers would fail to read for random periods of time, up to several minutes.

     

    I solved this problem by moving all the data in the V1210 to be sequential then made a single read from the UniStream with a 33 register array. It all works perfectly now, but I'm wondering if there isn't some bug in the MODBUS Read Registers function in UniLogic. Is the function trying to execute multiple reads simultaneously causing a collision, or is it something else?

  5. I may have solved my immediate problem, though I'd still like to understand exactly where the limitation comes from. I performed a "Bits To Numeric" function on some of the coils in the V1210 and then performed the reverse "Num to Bits" in the UniStream. That worked by reducing the number of coils being read while increasing the number of registers.

     

    It looks to me like there is an absolute limit in the number of coils that can be read using MODBUS in the UniStream. I've never noticed a similar limitation in Vision, and when I did hit a MODBUS limit, I would just initiate an additional read. I have one project that has 5 MODBUS reads of over 100 registers each. Even with the reads being initiated simultaneously, all of them execute flawlessly. Is there a similar way to initiate multiple reads in UniStream?

  6. I upgraded to UniLogic 1.13.09 but there was no change. By the way, upgrading UniLogic is a major pain. I cannot find a way to successfully upgrade the PLC to match the requirements of the UniLogic software without writing the whole thing to a DOK (a very time-consuming process) and then inserting the DOK into the PLC. If I try to upgrade the PLC directly from the UniLogic software I get this error when I try to connect via USB: "The selected PLC needs to be updated." That's fine, but when I try to update the firmware from the UniStream Manager I get this error: "No compatible version found for update." This looks like it's because the project file residing in the PLC is, of course, from the previous version and won't run until it get's updated in the new version of UniLogic. Updating feels a lot like chasing one's tail.

     

    While I often have the need to transfer a LOT of data between PLCs, the above isn't that much. With Vision PLCs I would normally pack all those coils into a few registers with the Struct function. Since in the above I am reading 411 coils, that could be packed into 26 registers in the V1210, then reading would be easily done by the UniStream. The problem is that I don't know how to unpack that Struct array in the UniStream. Is there a way to do that?

×
×
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.