| Products > Test Equipment |
| Time sync system clock R&S RTB2004 |
| << < (7/9) > >> |
| Kean:
Time zone data is quite big (for an embedded system) at more than 500kB compressed. Maybe not a lot for recent hardware, but it does make the user interface for tz selection non-trivial. It also changes quite frequently, with 197 commits and 71 releases over just the last 8 or 9 years (tzdata-info on github), so now you have an ongoing maintenance issue. So what seems like a quite simple problem, actually becomes a reasonably complex problem to correctly address for all potential users. I wish we could do away with summer/winter time changes. |
| tooki:
--- Quote from: Kean on February 17, 2024, 11:30:42 am --- I wish we could do away with summer/winter time changes. --- End quote --- I agree 100000%. |
| 2N3055:
--- Quote from: Kean on February 17, 2024, 11:30:42 am ---Time zone data is quite big (for an embedded system) at more than 500kB compressed. Maybe not a lot for recent hardware, but it does make the user interface for tz selection non-trivial. It also changes quite frequently, with 197 commits and 71 releases over just the last 8 or 9 years (tzdata-info on github), so now you have an ongoing maintenance issue. So what seems like a quite simple problem, actually becomes a reasonably complex problem to correctly address for all potential users. I wish we could do away with summer/winter time changes. --- End quote --- It is a case of overthinking. A simple manual time offset (+2h UTC, or -4h UTC) and user need to twice a year set it right would address 99.99% of problems. Point in fact, it would be faster than searching linear list for your town/coutry/region setting.. |
| Kean:
--- Quote from: 2N3055 on February 17, 2024, 01:51:01 pm ---It is a case of overthinking. A simple manual time offset (+2h UTC, or -4h UTC) and user need to twice a year set it right would address 99.99% of problems. Point in fact, it would be faster than searching linear list for your town/coutry/region setting.. --- End quote --- Yes, in fact this is what I typically implement on embedded systems. Sometimes there is a central server that pushes out TZ offset changes. Where possible, we just use UTC. And the UTC time is usually spot on due to NTP or GPS sync. But R.J. complained about both lack of time sync and TZ offset correction - his image shows the time on the scope as 59 minutes fast. |
| R.J.:
There are scopes who sync there internal OS-clock with the router on it's network!!! :P https://siglentna.com/application-note/datalogging-with-the-four-channel-sds1000x-e-oscilloscope-models/ So this is what I want to see in the R&S RTB200x....... :o When powering the scope, it's syncs the internel clock. That's all. |
| Navigation |
| Message Index |
| Next page |
| Previous page |