I have ROS 3.11 on two RB133.

NTP client on node A shows lots of great details, like poll interval, active server, last update, etc.

NTP client on node B shows no details. Just mode, primary, and secondary ntp server address.

The only difference I can think of that would explain this is that node B also has the ntp package installed, since it is also an ntp server for other nodes, including node A.

I would expect that the full ntp package would add funtionality, not remove it.
Has anyone else encountered this? I really like the additional detail on the ntp client page. It is
very helpful when debugging ntp problems.

What kind of ntp problems you had to debug? I have never cared about it.

NTP client on node A shows lots of great details, like poll interval, active server, last update, etc.
NTP client on node B shows no details. Just mode, primary, and secondary ntp server address.

The only difference I can think of that would explain this is that node B also has the ntp package installed, since it is also an ntp server for other nodes, including node A.

You said it! The NTP package is installed hence the 'slimmed' down client. I used to install the NTP package by default until one day by accident I noticed all this additional information in the standard client.

Not sure what the thinking was behind this decision though.

there are two NTP clients. the integrated Simple-NTP client, and the normal NTP client that comes with the NTP package.

Normis,

Yes, we now understand that there are two NTP clients. Our surprise is that what you call the
"integrated Simple-NTP client" has MORE detailed information than the NTP client in
the "full" NTP package.

Can we expect to eventually get the extra details that are in the simple NTP client in the "full" NTP client?

you are right I will file this as a bug