Oh, I see there are 6 different driver documentation for skywathcer mounts. I think here is due some consolidation.
At least your "SkyWatcher Alt/Az (Dobsonian) " and "Skywatcher Virtuoso (Alt/Az)" documentatin should be merged, as these are about exactly the same driver. I think only the softPEC portion of the Virtuoso documentation should be kept, as these is the only extra information there.

The "Connection" section needs some improvements. It is too complicated, and sometimes technically not so precise. For ex: the cable is not FTDI-to-USB, it is TTL serial-to-USB. FTDI is a maker of one type of such chipset, but there are others too. The device file /dev/ttyUSB0 does not identify the USB port, it identifies the device (cable with converter chip in it in this case). It is not change if you plug the cable into a different USB port. It changes if you pull and plug other Serial-to-USB cables, as these are (by default) numbered in the order enumerated by the kernel. But if you have only one such device (one cable connected) it will always /dev/ttyUSB0, unles some error occure and some yet.-non-existent device stuck in the mind of the kernel. Also there are methods to lock the device name to a particular cable (by serial number), but these is clearly out of the scope of this documentation.
Actually the connection needed for our driver is exactly the same as the eqmod driver, so we can take merit from the eqmod documentation. For example there the cable needed is named "EQDirect cable", we should stick whit that.
Also you menion that one can connect through the handcontroller, but you does not mention that is must be done in "PC direct" mode. It is important, otherwise it will not work.

I will try to come up some replacement text suggestion, just need a bit of time for that.

I think trackin should be ON during plate solving. Otherwise how can you utilize the result? The solve tells you where the mount was pointing at the time of the picture taken. But not any more...

I have tried guiding recently (on 26 dec, I think). I don't think anything has changed in the code that involves guiding. Jasem explicitly said: "the guiding code is a mess, leaving for an other time". Has that other time arrived yet?
I don't think slew rate impacts guiding. In my understanding these are totally different things.

I have just realized what SoftPEC is, it is disabled in my setup, I will try to experiment with that.

Read More...