I just talk with an engineer from ioptron and he said that CEM25 use the same protocol.

If it is then it should work with the current driver. Turn complete debug/logging to file on to diagnose any issues

Here are some screen grabs of the INDI and EKOS settings.
Also I am attaching the Log file.

please advise
thanks,
Malcolm

Thanks for the log, please try to enable the Scope Verbose log as well next time before you connect. Did you try to IEQPro/CEM60 driver? Please test with that driver and send the log.

thanks!
are the screen grabs of any value or shall I just send the log next time?

cheers,
Malcolm

Just the log

hi there, I think we are in business with the CEM60
It did a couple of good things, and a couple of weird ones.
The good news is, I was able to get RA/DEC from the mount once I synced on an object with the hand paddle.
I did not do the sync step ( I just unparked and slewed to an object) with the ZEQ25 driver so I will go back and experiment, maybe the ZEQ25 is a better driver, and my omission of the hand paddle sync step was the problem.
I was able to select a target, and successfully slew to it in Kstars with the CEM60 driver.
The strange behaviour was that the red target didnt follow the slew command to the new object.
When the slew was complete, I had to sync on the new object to move the target (in Kstars)
Also, it would not respond to a park command. I had to abort as it wasnt moving.
Are any of these issues configuration items where I can find a setting and fix it myself?
thanks very much,
Malcolm

You didn't enable Scope Verbose under Logging. At any rate, from the log all appear to be working fine. Also, please make sure the "red target" is not the new default KStars Telrad FOV indicator. There is a telescope crosshair and default Telrad crosshair (which you can turn off).

Please find attached a log file with all boxes checked.
The red indicator is the location indicator, not a telrad. Thanks for checking I may want to use telrad at some point.
The indicator does not follow the slew.
Using the real example, I first turned on the mount and did a one star alignment with the hand paddle.
I then slewed to Mercury (I'm indoors) with the hand paddle.
I then turned on the RPi2 and started Kstars/INDI.
In INDI I turned on the logging toggles first, then connected.
I got no lights in the INDI GUI by the RA/DEC fields.
When I first went in to Kstars, I expected the cross hairs to be on Mercury. They were nowhere near it.
I synced on Mercury, and the cross hairs moved into position.
I selected the sun, and slewed to it, but the cross-hairs didn't move, they stayed on Mercury. I synced on the Sun, and the crosshairs moved there,
After I had moved the scope, at shut down I noticed that I had a yellow light in the INDI GUI by the RA/DEC fields.
any thoughts?

thanks,
Malcolm

The log doesn't contain any further info, just basic debug info. Please check ALL boxes under Logging _before_ you connect.

I don't know what to tell you.
Please see the attached screen grab.
Is this not the page where I set the logging activity? Is there another page I should be going to for log settings?
Have I checked all the boxes? I don't see anymore boxes on this page to check off.
After clicking the boxes I clicked save.
As before, I clicked connect after I turned on logging.
What does this line mean?
INFO 36.155989 sec : Mount UTC offset is 0.00. UTC time is 1999-11-30T00:00:00
I selected my location in KStars. Should I be setting my UTC offset manually somewhere else?
Does Kstars not get date and time from the OS?
Since the mount is not aware of location, I sync on the starting object.
The crosshairs then are on the object where they belong, and I can slew to another object from there.
As I said before, I then have to sync on the second object to get the mount crosshairs to reflect the move and be centered on the new ogject.
It has become apparent to me that the mount has slewed to the new object, but is not tracking.
So I right clicked on the object, and under CEM60 I selected track. I assumed this would turn on tracking. (I have no idea why it would be off).
The mount immediately slewed into the pier when I clicked track, at which point I had to literally unplug the whole thing by diconnecting the power to prevent damage.
Obviously, by doing so I lost my log and started over. So I don't know if tracking is even on, and I can't check for drift because its the daytime so I will have to verify after dark tonight.
Thanks again,
Malcolm

Yeah the checks look right. Do you have TeamViewer? I can login to check it out.