Alain
Here are the screenshots.
I discovered I was unable to complete plate solving polar alignment in Kstars as the mount stopped after the first image (it takes 3 on one axis). I also noticed that when I connect the mount to the laptop for a test I am unable to manually drive more than about 10 degrees in either direction in both axes without re-pressing the direction key (mount control in Kstars) I wonder if these issues are connected? This is beyond my understanding.
Two more screenshots to come.

Andrew

Two more screenshots.
Andrew

Your manual slewing issue seems to not only happen to you, see:
onstep.groups.io/g/main/message/54120?p=...%2C2%2C0%2C101217608

Have a look on lessons learned on onstep.groups.io it can help to read users feedback.
In short, many people experience problems with "Terrans" but some return successes and even tweaked it.

latest firmware is: On_Step 10.17.f so many things could have changed between the two versions

Now to go ahead on your side I believe it is better you ask the help of a friend that has knowledge in electronics and programming to help you.
No way to get help from Terrans and from my side I am willing to help but without knowing your configuration it is just guessing.

<strong>Testing:</strong>
Testing a new OnStep directly in field is like plying roulette ...
Testing should be done step by step:
1) bench test: only connecting OnStep to computer but not the mount, run Kstars and using device manager connect to OnStep enabling full debugging to file and then run all tests you can do, "Connect/disconnect, Slewing, Syncing, Tracking, Parking/Unparking, Focuser operations, ... ) and then analyze your logs
2) If bench test are successful then connect the mount to OnStep (in house) and restart the same tests and see what is going wrong and see the logs
3) if everything is OK at this stage then you can reasonably start testing in field, if not you have to debug the stuff! that is look at Debugging and Tweaking

<strong>Debugging and Tweaking:</strong>
Check which version of hardware and firmware you have:
1) you already detected OnstepX 10.12e
2) Open you OnStep and identify: (<strong>with detailled pictures</strong>)
- Which Motherboard you have
- Which Processor is installed (should be ESP32 Wroom 3)
- Which drivers are installed for the 4 axes (DEC, RA, Foc1 and Foc2) (TMC2209?, TCM2130? ...)
3) Download OnStepX (git clone github.com/hjd1964/OnStepX)
4) Install arduino IDE (www.arduino.cc/en/software and download Arduino IDE 1.8.1)
5) based on the above detrieved informations edit the config file (see onstep.groups.io/g/main/message/53284?p=...0%2C2%2C0%2C97751477)
6) Compile and upload the firmware to your Onstep (again procedure depends on above informations)
7) then do testing again.

Sorry may be this does not help a lot but it is the only way to success in my experience.

PS: I've read this about "Terrans" great page openastronomy.substack.com/p/terrans-industry-onstep-v4-pro-kit

Hi Alain
Thanks you for your help so far, it has been a journey for me.
I will endeavour to work through the problems on my own. It seems the real problem is to edit the config.H file accurately when installing newer firmware.
Your latest edit includes the link: openastronomy.substack.com/p/terrans-industry-onstep-v4-pro-kit which looks helpful as it is the same kit as mine as I have taken out the board and photographed it.
I did try connecting to web interface via the unit's wifi and discovered it's mainly in mandarin. I have emailed the company to see if there is an English version.

Cheers
Andrew

Andrew,

nice to seen you don't lose motivation .
Yes you are right when you consider edit the Config.h file but to do this in the right way you really need to have an accurate knowledge of the underlying
hardware.
I am really willing to cooperate with you in this task because it could help to improve the driver also.
If you can share pictures of the hardware I would be really nice. The more information we have on this beast the better.

In particular it is extremely important to know if the "DS3231" chip is present on the board. (apparently there are free solder pads for it (and a warning about official firmware compatibility) see picture


For the WiFi (ESP8266 module) language issue there is definitively only one solution, re-flashing the module with the SWS firmware: github.com/hjd1964/SmartWebServer
unfortunately the later is soldered so flashing is certainly related to jumpers and so on, I will investigate.Seems the manual in the download is usefull: cdn.shopifycdn.net/s/files/1/0629/4411/6....23.rar?v=1682257315


If you succeeded to connect vi WiFi it gives you an alternative connection method via WiFi to Kstars (and also Android) see attachment
Even if I don't like WiFi and Android (for reliability issues) I encourage you to use both as helper for debugging.

One can rely on usbSerial for Kstars and as a feed back the Web access via WiFi.

Hi Alain
pictures of the board attached. Board isn't isolated from box so a bit obscured. I can send pictures of the isolated board if you want them.

Andrew

Wondefull, Pictuires are clear enough.

At least the good thing is that they match with the Flashing manual provided by Terrans on their download site.
Normally with the latest firmware you are on the safe side for flashing the ESP8206 (WiFi) and the ESP32 (OnStep) following the adequate manual.
They seem really accurate for what concerns the flashing procedure but it requires Windows (if you use their tools)
I am ready to assist you in this process.
The best is always to make a backup of the existing firmware, hoping they didn't burn the protection fuse bits.

I have a same problem with OnstepX 10.17g, since everything worked with the previous version, also the 0.5-2 guide doesn't work.
Ettore

You mean the "Communication: Ft# error, check connection" and with a "Terrans OnStep" ?

What do you mean by the "0.5-2 guide"?

Concerning "Communication :Ft# error, check connection."
I finally could reproduce the error with both Onstep and OnStepX.

To do it I modified the OnStep / OnstepX firmware code so that there is no correct response to the "Ft#" command.

<strong>in Onstep</strong> I changed false to true in Command.ino
// :Ft# Get focuser temperature
// Returns: n# temperature in deg. C
if (command[1] == 't') { dtostrf(ambient.getTelescopeTemperature(),3,1,reply); boolReply=true; } else

<strong>in OnStepX</strong> I changed false to true in Focuser.Command.cpp
// :Ft# Get focuser temperature
// Returns: n# temperature in deg. C
if (command[1] == 't') {
sprintF(reply, "%3.1f", getTemperature());
*numericReply = true;
} else

Once uploaded to the controller and connecting with Kstars I get the error message which is what is expected.
here the result with a terminal
so you can see OnStep answers 1 without the ending "#"

When I return to the original code the error message is not anymore present.
Here OnStep answers with 10.0 and the ending "#"

So there must definitively be something wrong with your respective firmware.

I really would like to see what is happening when you issue the ":Ft#" command within a terminal

or better use this really nice toolset github.com/kbahey/onstep-python

Hello Alan, Using the autoguider at speeds from 0.5 to 2x the mount moves only in one direction and does not reverse direction. If I use from 4 onwards everything is normal.

In Kstars the alignment procedure no longer works as it freezes after the first plate solving. I use OnStepX with Fystc S 6 V. 2.0

In fact it has nothing related to the "Ft#" error message but you experience trouble since you have upgraded OnStep to 10.17.g!
this version was released 2023-09-08.
lx200_OnStep driver last change was 1.19 for about 6 months as a consequence the error is not the cause of the driver but must come either from the Firmware, and update of Kstars ot other indi related things.
Stellarsolver has had some changes recently, kstars too now it depends which versions you are running