Jump to content

AlexV

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by AlexV

  1. Hello all,

    Using Remote Operator with a v1210 PLC I have the following issue:

    When I navigate through the screens from the PLC I don't have any problem and the screens fits all. The problem is when I try to entry to pending alarms and the screen scales to a smaller resolution and tactile keeps the bigger resolution (the good one). When I want to close the alarm window I have to click on right top black corner where ESC is. Is there any way to fix that? Is the only PLC that occurs this problem while other works correctly, fitting the alarm window and tactile to the good resolution.

    Best Regards,

    Álex

    Smaller Screen.JPG

  2. On 4/7/2021 at 3:12 PM, Flex727 said:

    Do you consider this a bug, or just an implementation issue with UniLogic?

    Maybe it's a form to optimize memory due you are not saving a lot of 0 in the registers between the ones with data. In VisiLogic this "issue" do not exist due al registers have a 0 by default and if you normally program VisiLogic and once test UniStream, if you don't know about that "issue" you can spend more time than expected.

    Best Regards,

    Alex

  3. 14 hours ago, Flex727 said:

    Apparently without our help. How did you end up figuring it out?

    Nevertheless, THANK YOU for reporting back with the solution!

    Hi Flex,
    We were loking for a solution with other companies and we saw that we weren't able to read various registers so we checked again the comunication configuration. Doing some test one of us saw that he was able to read only one register and at the time he was triying to read more, there was the comunication problem. We thought that if you don't put the missing adrecess there's a null value instead a 0 so modscan shows the error.

    Best Regards,

    Alex

  4. On 4/1/2021 at 12:56 PM, AlexV said:

    Hi all,

    I'm having some troubles to make modbus TCP work in my installation. I have a PLC 15.6'' USP-156-B10 programmed with a slave register table using slave ID1 and Port 502. I have tried to connect using modscan and PLC recognizes that i'm connected and receives the asks (sessions) but do not answer (success) to any of them on the Slave1 Structure. In modscan appears the following error: MODBUS exception response from slave device. I have followed the youtube tutorials about the modbus configuration and it's identical. PLC has been updated to the last version. On VisiLogic I have no problems when I want to communicate the PLC with modscan using modbus TCP. Please find enclosed some pictures about the issue and the program I have on PLC.

    Thank you,

    Best Regards,

    Àlex

    Comunicacion1.JPG

    PinedaCOM.JPG

    C332724_Pineda_9Turbines_20210324.ulpr 7.53 MB · 0 downloads

    Hi all,
    To all the people who can have this issue, problem has been solved changing the Slave ID to 255 and don't letting empty adreces. 

    I was doing an slave table using 2 int16 per data and in some of them I only was calling 1 int16 because this data type was enough. If another PLC reads 10 registers, you cannot leave in UniLogic empty registers and jump adresses, you need to complete all or you will have comunication problems. As you can see on the image, I'm starting on adress 3500 and jumping to 3502, 3502 to 3506 and more. You need to create a tag with the name that you want and put the adreces to fill the spaces between them, so it will be consecutive: 3500,3501,3502,3503,...

    Best Regards,

    Alex

  5. Hi all,

    I'm having some troubles to make modbus TCP work in my installation. I have a PLC 15.6'' USP-156-B10 programmed with a slave register table using slave ID1 and Port 502. I have tried to connect using modscan and PLC recognizes that i'm connected and receives the asks (sessions) but do not answer (success) to any of them on the Slave1 Structure. In modscan appears the following error: MODBUS exception response from slave device. I have followed the youtube tutorials about the modbus configuration and it's identical. PLC has been updated to the last version. On VisiLogic I have no problems when I want to communicate the PLC with modscan using modbus TCP. Please find enclosed some pictures about the issue and the program I have on PLC.

    Thank you,

    Best Regards,

    Àlex

    Comunicacion1.JPG

    PinedaCOM.JPG

    C332724_Pineda_9Turbines_20210324.ulpr

  6. On 3/2/2020 at 10:20 PM, Flex727 said:

    It looks like you're trying to read two vectors each of length 2 in two separate reads. The two vectors are only 8 registers apart. Why not simplify by reading it as a single vector of length 12? Block out MI 2508 through MI 2515 as "Do Not Use" and move your current use of MI 2508 - MI 2509 to MI 2516 - MI 2517.

    Hello,

    I've done what you say and now reading a longer vector I can read the values without problems. Thank you!

    Which is the max number I can put in a vector lengh?

    Cheers,

    Alex

  7. On 3/2/2020 at 10:04 PM, Ausman said:

    EDIT  Ignore this one....Flex's next answer alerted me that I had missed the length of vector, even though I looked carefully!)  Please explain MI 2507  in rung 6.  Should this perhaps be 2506?

     

    But do answer this one......How are you transitioning all your calls?

    cheers, Aus

    Hello Aus,
    The device I'm reading holds values in 2 registers. The value I want it's always placed on the second register so that's the reason I pick the MI 2507 instead MI 2506. I use a set/reset cycle for the serial comunication.
    Cheers,
    Alex

  8. 6 hours ago, Flex727 said:

    Add a delay timer. You are trying to do the second read on the very next PLC cycle. Perhaps the MODBUS slave cannot respond to multiple requests that quickly. Try giving it a 100ms or so between reads.

    I've tryied to add a 3 sec delay and after a 5 sec delay and I have the same problem. Tried with the SB3 and I have the same problem as the delays. I have tryed to add a counter to control the requests from the modbus but counter do not increment with SB3 pulse. The subroutine is loaded in the main routine. Something strange happens. Any idea?

    Thank you,

    Alex,

  9. Hello,

    I'm having an issue with the modbus communication over TCP. I can start and connect with the device without problems but at the time I try to get more than 1 value, the program asks the first request, gets a response and jumps to another device without asking the other requests. In segment 5 at start, I've the start contact (MB26) and the realimentation from the last device (MB121). At the end of the same segment i have the activation of segment 6 and the desactivation of the segment 5.

    The VisiLogic PLC I'm using is a V1210 model.

    Please find some images attached showing the problem.

    Thanks,

     

    Alex

    ModbusTCP.JPG

  10. Good day,

    Please find attached some images with the problema that occurs at the time of oppening a Project in VisiLogic versión 9.8.65. The first error that appears is the "Load 12Type mismatch" and when you click to the "Ok" button and try to open another display it appears the second message "Run-time error '13': Type mismatch".

    I have read a post where the response was to put a DLL in the VisiLogic folder. I have tryed this solution but it does not work (post was from 2015 and other VisiLogic versión).

    Let me know if you have some solution!

    Thank you,

    Error1.JPG

    Error2.JPG

×
×
  • Create New...