You're viewing a single thread.
The train is using a week counter internally that overflowed. 17.11.2003 is exactly 1024 (2^(10)) weeks ago.
But this would mean the epoch here would be the 2 April 1984 or maybe the 1st, if you respect the time as well, which sounds a tiny bit random lol. But so would be to use a week counter in the first place :D Especially since those trains are from the early 2000s.
EDIT: Other times in 2003 are also possible apparently https://twitter.com/TAltgeld/status/1646386165006716928?ref_src=twsrc^tfw|twcamp^tweetembed|twterm^1646386165006716928|twgr^99a8805bbdf28d116a3a7037dc24347da978e819|twcon^s1_c10&ref_url=https%3A%2F%2Fwww.kreiszeitung.de%2Flokales%2Fbremen%2Fsorgt-fuer-spott-im-netz-geniale-loesung-der-db-der-zug-aus-der-vergangenheit-92212981.html
How did you get to that epoch? I haven't seen any images of this happening earlier than 2003, so the overflow must have happened late last year or early this year, and whatever week 0 is is some time around 2002/2003. That would also fit with your comment that they were introduced in the early 2000s.
Maybe they just didn't expect the trains to last 20 years 😄
undefined> 20 y
Well, I did shown_date-1024 weeks=epoch. Your explanation sounds correct, though.
The only thing is, I've seen 2003 date before 2023 in random trains. Could also be a weird glitch when time sync fails or something.
It could be that the epoch is the start of 2003, so any train with a reset week counter shows 2003, and now they all do since the counter has overflowed late last year.
The fact that they use a week counter in general is something I remember from someone familiar with the onboard computer system, but I don't remember how it's set up specifically unfortunately.
Damn you're good
Ever heard of the 2048 bug? If no i suggest taking a look at the wikipedia page. I think it is a fun read
2038! I develop embedded systems and we’ve been testing for this for years now. There’s also a similar 2036 GPS bug
You mean the Year 2038 problem?