As we all know, the Klipper firmware has the advantages of high printing speed, high precision, and the ability to use the web page to control the printer, etc. MKS PI is a high-end microcomputer board designed by makerbase to replace the Raspberry Pi for the convenience of 3D printing users to use the Klipper firmware. In terms of hardware, MKS PI has a powerful 4-core 64-bit SOC onboard, with 1GBytes of DDR3 memory, supports HDMI screen interface and PI-TS35 screen interface, provides Ethernet port, 3-channel USB interfaces (can be connected to a 3D printer main board, USB Wireless network card, USB camera, U disk, USB keyboard and mouse, etc.); In terms of software, Makerbase provides a complete Klipper firmware transplanted based on the Armbian desktop system, and directly supports klipperScreen. Users only need to download the image file provided by Makerbase, burn it to the TF card, without a lot of construction work, use the usb port or serial port to connect your main board, configure the parameters on the webpage, and you can use the Klipper firmware happily!
Hello! I'm Quinn, the developer behind OctoEverywhere.com.
I have had quite a lot of support tickets come in recently with users trying to install OctoEverywhere on MKS PI, but the install fails because the clock is so far out of sync that the SSL handshakes fail.
I'm sure some devices will be out of sync because they might never connect to the internet. But would it be possible to do an NTP time sync for devices that connect to the internet? I'm sure the wrong-time SSL error would also affect other things a user would try to do, so it would be great to fix it if possible!
Oh man, well thanks for letting me know @ColdBeer72! Oddly, the issue seems to be even worse than an out-of-sync clock; the clock seems to always re-sync itself to the 20-day old incorrect date!
Hello! I'm Quinn, the developer behind OctoEverywhere.com.
I have had quite a lot of support tickets come in recently with users trying to install OctoEverywhere on MKS PI, but the install fails because the clock is so far out of sync that the SSL handshakes fail.
I'm sure some devices will be out of sync because they might never connect to the internet. But would it be possible to do an NTP time sync for devices that connect to the internet? I'm sure the wrong-time SSL error would also affect other things a user would try to do, so it would be great to fix it if possible!