Date time sync by Network Time Protocol (NTP)

    I have an ABB robot with an IRC5 controller model. I am retrieving the robot movement by using EGM. This records via UDP the robot movements and works fine. The problem is that the robot keeps loosing its date time accuracy each time I switch it off, so the data I am recording is not accurate. I cannot synchronize it with other systems.
    I have configured an NTP server but this only works when I do it manually, it does not update the robot time.
    This would be ok if I can get the robot time, so I can calculate the difference. But I cannot get the robot date time remotelly in an accurate way. I only can find workarounds (Cdate to a log file, creating an FTP file, etc).

    In a nutshell, my questions are:

    How do you update the robot date time remotely?
    Why NTP does not work automatically?
    How do you get the robot date time remotely?

    I hope anyone can help!

    Edited once, last by molbalga (November 30, 2018 at 8:09 AM).

    From RS Help:

    Setting the controller date and time
    You can either set the date and time to the same as the network time server, or you can specify the date and time manually.

    Use this procedure to set the controller date and time:

    In the Configuration group, click Properties, and then click Date and Time.

    The Set Date and Time dialog box appears.

    This dialog provides two options: Network Time and Manual Time.

    Select Network Time and in the Time server address box, enter the IP address of the network time server.

    Select Manual time and then set the Date and Time in the boxes provided. You can select the required time zone in the Time zone list.

    I am almost entirely certain the option PC Interface is required.

    An alternative, as long as fully licensed RS is available, is to run a Job (with Windows Task Scheduler) to execute the action Set Time.
    Check out RS Help> Controller tab> Features for real controllers> Jobs

    It does not work. When I set the date time manually, the robot time is updated. But when I check again the date and time, it has shifted some seconds, it does not retain the same date and time.
    I have also configured an NTP synchronization and it does not work properly. Time is different in server and robot.
    When you select manually the robot to synch, it says it has worked, but when you check again the time is out of synch.
    When I contacted with ABB service, they suggest to change the battery. We will try this, and I will post the result.

    Yes, there is bound to drifting of the time in the control. The control is not an atomic clock. :icon_smile:

    Do you have your LAN port IP setting correct?

    From the Ethernet - IP Manual 3HAC04127 (it is suggested to obtain one):

    Can I configure the WAN connector and the selected LAN connector on the same subnet?
    No, the EtherNet/IP address for the WAN connector must belong to another subnet
    than the address of the selected LAN connector.
    For example, if the address of the LAN connector is 111.122.133.144, the address
    for the selected LAN connector cannot be 111.122.133.145 if you are using a subnet
    mask 255.255.255.0 (but it can be 111.122.134.145).

    &

    My Ethernet/IP network and factory network is on the same logical network but i want to have one
    logical network for factory LAN and one logical network for Ethernet/IP and have a switch separate
    the traffic. How do I do?
    1 In the I/O configuration under I/O bus, configure the IP address, subnet mask,
    gateway and destination of the Ethernet/IP network.
    2 Do an X-start.
    3 Change the network settings (these are used for the WAN connector) and
    choose the correct system.
    4 Make sure that these two networks are on separate subnets.
    5 Restart the controller.

    Edited once, last by SomeTekk (January 4, 2019 at 7:17 PM).

    Quote from SomeTekk

    Do you have you LAN port IP setting correct?

    I am using the Service port, so LAN configuration is very basic. Therefore they are both in the same network, both the PC an tthe robot controller. address for the robot in the service port is by default 192.168.125.1, and any PC connected have the 192.168.125.xxx.

    This robot does not have the PC option, this is why we are using the service port.

    Quote from molbalga

    I am using the Service port, so LAN configuration is very basic. Therefore they are both in the same network, both the PC an tthe robot controller. address for the robot in the service port is by default 192.168.125.1, and any PC connected have the 192.168.125.xxx.

    This robot does not have the PC option, this is why we are using the service port.

    The IRC5 system hands out IP addresses because there is a DHCP server attached to that port. Do you have static IP addresses for for your PCs connected to the service port? If not try assigning them in the range above 192.168.125.010. Where I work a PC has a static IP in the 192.168.125 (above .010 for the final octet) range and it is able to connect to the IRC5.

    From the IRC5 Product Manual ( whether you believe ABB's manual, or not, is entirely up to you):

    Note
    The service port shall only be used for direct connection to a PC as described
    in this procedure. It must not be connected to a LAN (local area network), since
    it has a DHCP server that automatically distributes IP addresses to all units
    connected to the LAN.
    Contact your network administrator for more information.

    Note
    The maximum number of connected network clients using robapi is:
    • LAN: 3
    • Service: 1
    • FlexPendant: 1
    The total max. number of applications using robapi running on the same PC
    connected to one controller has no built-in maximum however, UAS limits the
    number of logged on users to 50.
    The total max. number of concurrently connected FTP clients is 4.

    I do not say you are wrong, it may be possible that the network connection through the service port is the issue. However it is difficult to believe, since all functions are correct through this port. I can connect both via FTP and EGM (UDP) and I receive all trajectory data.

    I have static addresses and I have only one pc connected to the robot, but it is true that both are connected to a switch in between.

    In any case I cannot see how this can affect the internal clock of the robot controller.

    ABB has suggested me to change the CMOS battery in the controller. We will try this and also connecting only the PC to the service port and I will let you know the result.

Advertising from our partners