Results 1 to 5 of 5
  1. #1

    AX- JACE keeps resetting time

    i have a jace600 on 3.6.31.4 that imports schedules from a supervisor. every couple of days it seems like the time and date would reset to feb 11 2013 20:59, causing all the devices to shut off. i tried rebooting the jace a few days ago and this issue reappeared. something wrong with the timesyncclient? any help?



    MESSAGE [16:36:00 18-Jul-13 PDT][timesync] /Services/TimeSyncService/TimeSyncClient
    java.net.SocketTimeoutException: Receive timed out
    at java.net.PlainDatagramSocketImpl.receive0(Native Method)
    at java.net.PlainDatagramSocketImpl.receive(Unknown Source)
    at java.net.DatagramSocket.receive(Unknown Source)
    at javax.baja.timesync.BTimeSyncClient.poll(BTimeSync Client.java)
    at javax.baja.timesync.BTimeSyncService.executePoll(B TimeSyncService.java)
    at javax.baja.timesync.BTimeSyncService.sync(BTimeSyn cService.java)
    at javax.baja.timesync.BTimeSyncService.doSync(BTimeS yncService.java)
    at auto.javax_baja_timesync_BTimeSyncService.invoke(A utoGenerated)
    at com.tridium.sys.schema.ComponentSlotMap.invoke(Com ponentSlotMap.java)
    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineU til.java)
    at javax.baja.sys.BComponent.doInvoke(BComponent.java )
    at javax.baja.util.Invocation.run(Invocation.java)
    at java.lang.Thread.run(Unknown Source)
    MESSAGE [16:36:01 18-Jul-13 PDT][timesync] /Services/TimeSyncService/TimeSyncClient
    java.net.SocketTimeoutException: Receive timed out
    at java.net.PlainDatagramSocketImpl.receive0(Native Method)
    at java.net.PlainDatagramSocketImpl.receive(Unknown Source)
    at java.net.DatagramSocket.receive(Unknown Source)
    at javax.baja.timesync.BTimeSyncClient.poll(BTimeSync Client.java)
    at javax.baja.timesync.BTimeSyncService.executePoll(B TimeSyncService.java)
    at javax.baja.timesync.BTimeSyncService.sync(BTimeSyn cService.java)
    at javax.baja.timesync.BTimeSyncService.doSync(BTimeS yncService.java)
    at auto.javax_baja_timesync_BTimeSyncService.invoke(A utoGenerated)
    at com.tridium.sys.schema.ComponentSlotMap.invoke(Com ponentSlotMap.java)
    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineU til.java)
    at javax.baja.sys.BComponent.doInvoke(BComponent.java )
    at javax.baja.util.Invocation.run(Invocation.java)
    at java.lang.Thread.run(Unknown Source)
    MESSAGE [16:36:01 18-Jul-13 PDT][timesync] /Services/TimeSyncService/TimeSyncClient
    java.net.SocketTimeoutException: Receive timed out
    at java.net.PlainDatagramSocketImpl.receive0(Native Method)
    at java.net.PlainDatagramSocketImpl.receive(Unknown Source)
    at java.net.DatagramSocket.receive(Unknown Source)
    at javax.baja.timesync.BTimeSyncClient.poll(BTimeSync Client.java)
    at javax.baja.timesync.BTimeSyncService.executePoll(B TimeSyncService.java)
    at javax.baja.timesync.BTimeSyncService.sync(BTimeSyn cService.java)
    at javax.baja.timesync.BTimeSyncService.doSync(BTimeS yncService.java)
    at auto.javax_baja_timesync_BTimeSyncService.invoke(A utoGenerated)
    at com.tridium.sys.schema.ComponentSlotMap.invoke(Com ponentSlotMap.java)
    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineU til.java)
    at javax.baja.sys.BComponent.doInvoke(BComponent.java )
    at javax.baja.util.Invocation.run(Invocation.java)
    at java.lang.Thread.run(Unknown Source)

  2. #2
    Join Date
    Jan 2005
    Location
    USA
    Posts
    1,459
    Looks like the jace is trying to reach the time sync server on the supervisor and is unable to for what ever reason. I do not understand the setting back to February part. Here are some of my notes, maybe they will help.

    Supervisor to jace time sync
    1: check the supervisors NtpPlatformServiceWin32 service is enabled.
    2: be sure that windows is set to synchronize with internet time.
    3: Add if necessary a time sync service on the supervisor and open udp port 37 in the firewall
    4: Set up the time sync client on the jace and configure it to communicate with the supervisors time sync server. Make sure the ip addy is correct.
    "It's always controls"

  3. #3

    Confused

    Quote Originally Posted by skwsproul View Post
    Looks like the jace is trying to reach the time sync server on the supervisor and is unable to for what ever reason. I do not understand the setting back to February part. Here are some of my notes, maybe they will help.

    Supervisor to jace time sync
    1: check the supervisors NtpPlatformServiceWin32 service is enabled.
    2: be sure that windows is set to synchronize with internet time.
    3: Add if necessary a time sync service on the supervisor and open udp port 37 in the firewall
    4: Set up the time sync client on the jace and configure it to communicate with the supervisors time sync server. Make sure the ip addy is correct.

    Thanks for your input,

    the timesync feature wasnt enabled on the supervisor because they are using NTP as their time server (time.windows.com). the jace itself didnt have the ntp enabled because there is no outside internet to be able to communicate with a time server.

    it just didnt seem likely that the jaces time would be taht far off of the supervisors in a matter of a few days, even if the timesync wasnt syncing. which made me think that it was an issue with it resetting time

  4. #4
    and this jace has been commissioned an running about 6 months before this issue came up

  5. #5
    Join Date
    Jan 2005
    Location
    USA
    Posts
    1,459
    That is strange. I have had time drift on systems but usually by a few minutes a month. May want to check the battery backup. Also check your logs to see if there are any power issues.
    "It's always controls"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Comfortech Show Promo Image

Related Forums

Plumbing Talks | Contractor Magazine
Forums | Electrical Construction & Maintenance (EC&M) Magazine
Comfortech365 Virtual Event