Hi Heinz,
I'm pretty sure the main troubles will come from
#0:VX# command. It's used to read LFEP state and everything else moves around it.
Current solution is an ASCOM server making multiple connections possible.
Because of this choice there is the need to manage commands coming from many clients.
Just for example you won't focus while moving the mount. If only one software was used to control LFEP, the software itself will never send a focusing command while the mount is moving since the same software will have sent the GoTo command and will be waiting for the end of the GoTo...
But if an ASCOM server solution is adopted then the ASCOM server has to take into account a client can ask to focus while the mount is moving because of a GoTo command sent by another different client...
Furthermore you can control your LFEP also by handbox! And this is the reason why the server has to poll LFEP internal settings to know and refresh LFEP state to exclude possible issues...
#0:VX# is the command periodically sent to LFEP to know its state.
The answer is binary and each bit has its own meaning...
I think #0:VX# command or an equivalent command is implemented in 5.xx firmware. There is the need to test it in different conditions to reverse engineer the binary answer...
Maybe because of missing features in LFEP 5.xx FW the answer length is different too...
I'm willing to participate in some tests, but I'm not an IT specialist. Furthermore I'm not sure if these tests are possible, because my laptop didn't connect to the LFEP by using the original LFEP driver (error message: „Please select COM/LAN settings in SETUP first“).
If you try the ASCOM driver for 6.xx FW, you have to set the COM port number (by a click on setup) before being able to connect to LFEP...
As soon as you connect the LFEP by USB cable a new serial port is available; you can figure out its number by Windows control panel...
Then, after executing the LFEP ASCOM launcher, you have to click on setup to set the right port number. Then a click on connect will start communication by using the appropriate port...
I think the same is valid also for the old driver...
Port choice is saved; so setting the port number is required only for the 1st connection after the driver has been installed or, obviously, in case of port number change...
The software FocusMax was yet unknown to me. Thank you for that tip.
I suggested this solution since with no efforts and without an ASCOM server solution (i.e. by a simple ASCOM LX200 driver) thanks to FocusMax you'll be able to communicate to LFEP by many clients ...
CS
Armando