News:

  • September 12, 2025, 07:24:43 PM

Login with username, password and session length

« previous next »
Pages: 1 [2]

Author Topic: Time Server Issues  (Read 2698 times)

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6116
  • Yes Pinky, Do-more will control the world!
Re: Time Server Issues
« Reply #15 on: July 02, 2025, 03:48:40 PM »
You are sticking the value into a V, which is unsigned...65236 is the WORD unsigned rendering of -300. Displaying as Vn:S will show the right value.

The time sync packet is a UDP broadcast frame going to our standard programming port 28784 (0x7070). The last three bytes of the time zone capable packet are (for -300) 0xB2 0xD4 0xFE. If you have a bunch of devices though, there might be a lot of traffic on that port.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

rlp122

  • Sr. Member
  • ****
  • Posts: 89
Re: Time Server Issues
« Reply #16 on: July 02, 2025, 08:34:25 PM »
Something I haven't seen mentioned:

Is there any indirect addressing in the PLC?  If so, have you properly bounded it so that it can't get outside the proper area?
Logged

eman5oh

  • Sr. Member
  • ****
  • Posts: 57
Re: Time Server Issues
« Reply #17 on: July 03, 2025, 02:11:49 PM »
I do not have any indirect memory access or manipulation, at least that is intentional.   I just ran a test by setting the time zone on the PLC designated as the server to -360 and the clients now updated to 65176. I am viewing the time zone information in data view window showing the value of $TimeZone with the data set to native. This is not the V memory that I have set as the destination for the  time information. Any ideas of why this would be happening?
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6116
  • Yes Pinky, Do-more will control the world!
Re: Time Server Issues
« Reply #18 on: July 03, 2025, 02:55:14 PM »
The client $Timezone says that?
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

eman5oh

  • Sr. Member
  • ****
  • Posts: 57
Re: Time Server Issues
« Reply #19 on: July 03, 2025, 03:00:23 PM »
Yes the client $TimeZone shows 65176 and the server shows -360 when viewed in data window set to native.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6116
  • Yes Pinky, Do-more will control the world!
Re: Time Server Issues
« Reply #20 on: July 03, 2025, 10:39:51 PM »
Mine doesn't do that, but I'm thinking that had already been fixed a while back. I'll check the code when I get back in the office.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

eman5oh

  • Sr. Member
  • ****
  • Posts: 57
Re: Time Server Issues
« Reply #21 on: July 07, 2025, 02:34:36 PM »
Updating the OS from 2.10.1 -> 2.10.2 fixed the issue.
« Last Edit: July 07, 2025, 07:44:43 PM by eman5oh »
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6116
  • Yes Pinky, Do-more will control the world!
Re: Time Server Issues
« Reply #22 on: July 08, 2025, 10:17:18 AM »
Quote from: eman5oh on July 07, 2025, 02:34:36 PM
Updating the OS from 2.10.1 -> 2.10.2 fixed the issue.

Yeah, it was a sign extension problem and did get fixed for 2.10.2.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO
Pages: 1 [2]
« previous next »