Jump to content

Gabriel Franco

Members
  • Posts

    418
  • Joined

  • Last visited

  • Days Won

    20

Posts posted by Gabriel Franco

  1. 20 hours ago, engineer118 said:

    Is there a way to do this through visilogic? Unfortunately the HMI screen is completely black so there is no possibility of navigating to INFO mode from the HMI (Information Mode (unitronicsplc.com))

    I´m affraid no. As long as I remember, INFO mode is not accesible via remote operator neither remote access, so, you would be completely blind to perform SD actions from INFO mode.

     

    I would get a new unit, exchange CPU as Kratmel suggested then verify if project is burnt.

  2. It´s a normal behavior.

    If you want your PLC act as slave (named server in Modbus TCP), you configure it under PLC Communications | Protocols | MODBUS | Slaves, either Ethernet or RS485. Then, it will be another slave in the network.

    If you want your PLC act as a master (named client in Modbus TCP), you must configure all your slaves under PLC Communications | Protocols | MODBUS | Masters, either Ethernet or RS485. Then, it will be the master in the network. All slaves must have unique IP (Ethernet) or ID (RS485).

     

     

     

    • Thanks 1
  3. 11 hours ago, Flex727 said:

    I'd love to know what SI 14 is telling you, though you would need to calculate it using SB 14 in ladder first.

    I like to have a screen on most of my projects that includes PLC temperature, scan time, and other misc info that could be useful for troubleshooting.

    I´ve used it and not always gives too much information about how hot is the snap.

  4. Mod add, pinned in "topics almost worth pinning"

    1. Initialize the socket as usual, but using UDP instead TCP.

    image.png.982d48f18cb7d32a323221b49e478317.png

    2. Configure Modbus TCP.

    image.png.848a9c2cb0e247b2a64d86acba3eeda2.png

    3.  Execute Modbus function. There is not need to open socket nor wait for open connection.  What I do here is to increase a pointer to read sequencialy all slaves.

    image.png.b47b4aa8d30793b3b835d6075b8c7d89.png

    4. Wait for response and process your data.

    image.png.8aa7f85ad270e6f07b2e5dfc8e74f101.png

     

    On 5/6/2022 at 11:30 PM, Flex727 said:

     Are there any issues with mixing UDP and TCP on the same network? What are the disadvantages to using UDP vs. TCP?

    I´ve used up to 4 sockets mixing TCP, UPD and TCP_Raw with no problems at all. Keep in mind that each socket acts as a logical port, so you may use each one with its own port number and protocol.

    UDP disadvantages:

    1. Packages lost because of inherent lack of error check of UDP, but it´s compensated with more speed and less comms overhead. 

    2. Some devices only accept TCP connections.

     

     

    • Thanks 1
  5. 8 hours ago, Sergio Ramos said:

    So I would have to wire in two power sources? In the CANbus pins and the HMI Pins? 

    No, just one device on the entire CANBus network. You can use same PS used to power PLC, however I recommend to protect with fuse the CANBus power lines.

    8 hours ago, Sergio Ramos said:

    Wouldn't adding an external PS make my code a bit irrelevant since it would start the communication immediately without user input? Is there a solution for this?

    Is your code what defines when and how exchange data, you may add conditions as required.

    8 hours ago, Sergio Ramos said:

    Would I have to buy an expansion module to be able to power the CANbus ports?

    I don´t think

     

     

×
×
  • Create New...