Time and date set within closed network DHCP/NTP/24h vs 12h etc
Is there a way to set the time on on Coreone that is in a private network without a gateway ?
It has a NTP server and is served by the DHCP server. Works well with other devices on the net.
Right now all the files are stamped 12/31/2097 11:59 PM *1 Annoying to know which revision has been the latest upload.
*1 this is even if the 24h selector in the settings is enabled.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
I think you can set time manually in the menu. Never tried it though.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
There's no way to do it with the menu...
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
A firmware request may be the only way to get it fixed.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
A firmware request may be the only way to get it fixed.
From what I understand, the Core One firmware currently tries to reach prusa3d.pool.ntp.org to sync the time. In a private network, it should be possible to set up an NTP time server and DNS name server (e.g. on a Raspberry Pi -- if they are not running on some existing computer already), and then map prusa3d.pool.ntp.org to the local NTP server via a static DNS entry.
It's a somewhat complex hack, but I don't see how Prusa could do fundamentally better with the existing hardware: There is no realtime clock with battery backup power in the Core One. So, unless you want to manually set the time every time after powering the printer, it will need to get the time from an NTP server. I.e. you would need to have one available in your local network. The only thing Prusa could simplify in a firmware update is to allow us to set the NTP server's name or IP address, which would avoid the need for a local DNS and the static DNS entry for the current, fixed NTP name.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
That is what the OP asked for. A way to set a private NTP server. I have two NTP servers on my internal network. For privacy and security, all network activity should be able to configure from the menu. There should never be a need to use personal hardware on a public network.
It is a firmware request for an enhancement or a but as a security issue.
Another option is to remap the DNS requests for NTP to your local NTP through the firewall.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
There is no realtime clock with battery backup power in the Core One.
This is not correct. Look at the top right corner of the image of the board here and you'll see the battery for the real time clock.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
The OP already has a local NTP server running. All they need to do is to set up the DNS entry, right? The only Prusa-specific knowledge required for that is the mentioned NTP server name which the firmware wants to connect to.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
There is no realtime clock with battery backup power in the Core One.
This is not correct. Look at the top right corner of the image of the board here and you'll see the battery for the real time clock.
Oops -- I stand corrected, thank you for catching this. If there is indeed an RTC powered by that battery (and what else would it be?), it would indeed seem like an obvious firmware enhancement to allow manual setting of the time.
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
I will try to hack the dns... Interesting way.
The best would be to comply to DHCP option 042 and use that to set the time. I have all my equipment in UTC... So I won't have to play with DST.
Where do we ask the folks for that to be available or at least a setting entry in the menus ?
RE: Time and date set within closed network DHCP/NTP/24h vs 12h etc
UTC time on systems is an issue in lots of cases. Octoprint has a request to deal with that.
It would be here. Just select the correct category. Then select the issues tab. In this case it is an enhancement and I would point out both security and privacy.