Ok, here is something to try for ASCOM windows
Note: Since I do not have an EQMOD, I disabled EQMOD logging as below and let ASCOM do logging.
CLick ASCOM Connect
(assumes have already done all setup for driver previously, ASCOM EQMOD knows your mount)
Expand EQMOD handbox window (Near top right, wrench>>>)
At far right middle, CommsLog, click the square box to disable internal logging)
Back on the Tookbox window, click ASCOM Disconnect
Now launch ASCOM Diagnostics
Start->ASCOM Platform X (X is your version)
Select ASCOM Diagnostics
Select 'Serial Trace Enabled'
Now back on the EQMOD Toolbox window
CLick ASCOM Connect
Do some stuff in the ASCOM handbox window
Back on the EQMOD toolbox window, click ASCOM Disconnect
Now on my system, ASCOM Diags are writing a serial log file to:
In this directory I see files, select one of the newest ones, you should see comms
Ex: (using my Nstep focuser as example)
08:40:32.336 New Worker thread synchronisation by: WaitForSingleObject
08:40:39.567 Port Set to: 9
08:40:39.567 Speed Set to: ps9600
08:40:39.567 ReceiveTimeout Set to: 2 seconds
08:40:39.570 Set Connected True
08:40:39.571 Set Connected Using COM port: COM9 Baud rate: ps9600 Timeout: 2000 DTR: True ForcedDTR: False RTS: False ForcedRTS: False Handshake: None Encoding: 1252
08:40:39.571 Set Connected Transmission format - Bits: 8 Parity: None Stop bits: One
08:40:39.577 Set Connected Reading COM port through Interrupt Handling
08:40:39.691 ConnectedWorker Port connected OK
08:40:39.693 ClearBuffersWorker Completed
08:40:39.693 TransmitWorker > #
08:40:39.696 TransmitWorker >
08:40:39.696 ReceiveCountedWorker 1 < S
08:40:39.703 TransmitWorker > :CS010#
08:40:39.713 TransmitWorker > :RQ0
08:40:39.714 ReceiveCountedWorker 7 < +000000
08:40:39.732 TransmitWorker > :RQ1
08:40:39.733 ReceiveCountedWorker 7 < +019864
08:40:39.750 TransmitWorker > :RQ2
08:40:39.751 ReceiveCountedWorker 7 < +000000
I followed your instructions but logging does not start and I don't know why. When I click to "ASCOM Connect" it creates a file in the log folder named i.e. "ASCOM.Serial.1803.204490.txt" but the content is only as follows:
18:03:20.449 New Worker thread synchronisation by: WaitForSingleObject
18:03:20.449 New Minimum Threads: 4 4
18:03:20.449 New Maximum Threads: 1000 1000
18:03:20.449 New Available Threads: 1000 1000
Nothing else is written or added.
I tried to save the comms trace log in the EQMod window that I disable first in your instructions, at least there's some info in it, that I attach. Am I missing something or doing something wrong?
Little update: I received the new EQMod cable. At first it seemed it solved the problem, as in the cold run there were no errors in the log, but I'm trying it right now on actual shoooting and I still see jumps... so cable is innocent!
Things you don't expect to happen: I had a good opportunity to upgrade the mount and got a wonderful HEQ5 with Rowan kit that came with a brand new EQMod cable and guess what? Still jumping!!! As I just tried to take some pictures, I didn't turn on the debugging log and decided to have a full reinstallation that I'm running right now, etching the SD for a lot of unexpected problems that still happen, such as the ASI 120 mini switching to 8 bit for no apparent reason.
As said, I'll try with a brand new install, anyway any suggestion on how to tackle the issue that is still here?
I wonder if the eqmod driver should reject large deltas that are reported from the mount. With the tracking or slew rate being known, a factor could be applied to ignore values outside of a possible range. I have seen jumping too, and went through a period of cable replacement, power supply replacement, etc. Mine doesn't do it often now, but it is very annoying when it does, and can even be dangerous to the mount and equipment when its actual location is different than what kstars shows.
12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT w/.8x for the light
Fedora Linux, 100% INDI
You're right Jim, that's it! If the mount is tracking, there's actually no real problem or consequences, except that you're forced to use the ST4 cable instead of pulse guiding, but if the jump happens during the slewing that's a real problem becase the mount movement goes out of control! It happened a lot of times during plate solving, and that's a problem because instead of micromovements done for correcting very small arcsec the mount starts slewing on larger distances, or also if it happens during near the meridian flip it can trigger it. What can be done?
Due to this discussion, i tried to go back to ST4 guiding. My calibration with eqmod looks a bit messy, with some clusters of points near the center, while it for ST4 looks very nice and with a perfect right angle. There guiding also seemed to be a bit better with ST4, but not much so it could just be me looking for gremlins....