[Ikeda, YamaT]

As reported in klog#36789, Pcal picomotors didn't work.
We found that it somehow occurs by the communication error between picomotors in the old PICO network and the Debian13 system.

Pcal picomotors are required for proceeding tomorrow's calibration of the integration sphere in YPcal.
So I downgraded k1script1 which is the secondary script server and processes for Pcal picomotors were moved back to it as the first-aid.
Another processes which works fine also on the Debian13 system are still on k1script0 which is the primary server.

Modification of the picomotor script, moving Pcal picomotors to the PICO network and/or update of picomotor driver firmware is required to make old script server retired.

-----
A reason why Pcal picomotors didn't work was a mismatch of the communication mode of Telnet between the picomotor script and its driver. Though picomotor drivers seem to support the char-mode, the picomotor script on the Debian13 system tries to connect as the line-mode for picomotors in the old PICO network in some reason. This issue didn't occur for picomotors in the PICO network. Script servers can access the PICO network directly. On the other hand, the old PICO network can be accessed only via k1gate. This is an only difference between these two networks. But a difference in L3 connection doesn't affect a mode negotiation of Telnet in normal. Because all picomotors had worked fine on the old script server and picomotor drivers in the old PICO network was able to be accessed from k1ctr which was the Debian12 system, it seems an issue only on the Debian13 system.

Although we haven’t identified the exact cause of this issue yet, I downgraded k1script1 which was the secondary script server and moved only the problematic picomotors on that server because Pcal picomotors are required for tomorrow's integration sphere calibration at YPcal. Another all processes which have no issue are still on k1script0 which is the primary script server.

The picomotor script connect picomotor drivers by using python3-socket package instead of telnet package. So IAC negotiation which is done at the beginning of Telnet connection must be implemented by ourselves. I'm not sure the firmware on picomotor drivers are kept modern ones, but anyway a versions of socket libraries and a python3-socket package on the Debian13 system is bumped up from ones on the old Debian systems. For this reason, some kind of incompatibility on a specification of Telnet negotiation expected by Debian13 and picomotor drivers. To make the old script server retired, this issue must be solved.