×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] Problems with IEQ45pro libindi v1+ for my ZEQ25

That code doesn't work, you're reading the reply before you send the command? Is anyone else experiencing this problem (latitude/longitude setting?) If you enable full debug logging, does it timeout after issuing the command?
8 years 5 months ago #5954

Please Log in or Create an account to join the conversation.

  • Posts: 47
  • Thank you received: 6
Tomorrow I will test the latest svn code on my mount and let you know.
Thank you.
8 years 5 months ago #5956

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19
I have attached two logs from runs with and without the usleep commands in the setStandardProcedure function. Below is the most minimal version of the function that will work for me. Sorry to be a pest with this but it's really bugging me.
*************************************************************************************
int setStandardProcedure(int fd, const char * data)
{
 char bool_return[2];
 int error_type;
 int nbytes_write=0, nbytes_read=0;
 
 DEBUGFDEVICE(lx200Name, DBG_SCOPE, "CMD <%s>", data);
 
 if ( (error_type = tty_write_string(fd, data, &nbytes_write)) != TTY_OK)
    	return error_type;
 
error_type = tty_read(fd, bool_return, 1, LX200_TIMEOUT, &nbytes_read);
 
usleep(10000);
 tcflush(fd, TCIFLUSH);
usleep(10000);
 
 if (nbytes_read < 1)
   return error_type;
 
 if (bool_return[0] == '0')
 {
     DEBUGFDEVICE(lx200Name, DBG_SCOPE, "CMD <%s> failed.", data);
     return -1;
 }
 
 DEBUGFDEVICE(lx200Name, DBG_SCOPE, "CMD <%s> successful.", data);
 
 return 0;
 
}
*******************************************************************************************************

File Attachment:

File Name: lx200zeq25...leep.zip
File Size:2 KB


--Jon
Last edit: 8 years 5 months ago by Jon.
8 years 5 months ago #5965
Attachments:

Please Log in or Create an account to join the conversation.

I added a custom setStandardProcedure for ZEQ25 as above, I think you can run svn up and test. The reason you see set longitude/latitude twice is because the first time it is loaded from the configuration file, and then KStars also send location updates automatically on start up. You can enable/disable that in KStars INDI options. It shouldn't matter though.
The following user(s) said Thank You: Piero, Jon
8 years 5 months ago #5967

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19
Thanks knro.....
Another thing I am wondering, I am getting 'object below horizon' messages no matter where I slew. The scope slews fine, i just keep getting the following message:

2015-11-22T15:31:18: CMD <:GR#>
2015-11-22T15:31:17: Object below horizon.
2015-11-22T15:31:17: Error Slewing to JNow RA 14:50:34 - DEC 74:05:27
2015-11-22T15:31:17: RES <1>
2015-11-22T15:31:17: CMD <:MS#>
2015-11-22T15:31:17: <Slew>

Since the RES is 1, doesn't that mean that 1 is being returned from Slew(PortFD)? Would it be safe to go with:
//int err=0;
        /* Slew reads the '0', that is not the end of the slew */
        if (Slew(PortFD) < 1)
        {
            EqNP.s = IPS_ALERT;
            IDSetNumber(&EqNP, "Error Slewing to JNow RA %s - DEC %s\n", RAStr, DecStr);
            slewError(err);
            return  false;
        }
rather than:
int err=0;
        /* Slew reads the '0', that is not the end of the slew */
        if (err = Slew(PortFD))
        {
            EqNP.s = IPS_ALERT;
            IDSetNumber(&EqNP, "Error Slewing to JNow RA %s - DEC %s\n", RAStr, DecStr);
            slewError(err);
            return  false;
        }
in the goto?

Thanks again.....

--Jon
8 years 5 months ago #5977

Please Log in or Create an account to join the conversation.

Seems ZEQ25 and Meade send different replies for the same command, so the ZEQ25 driver is using its own slew command now.
The following user(s) said Thank You: Piero
8 years 5 months ago #5980

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19
Beautiful!!! Thank you.....Working on both local and remote raspi. I will get out with this the next clear night and give it a go.

Thank you!

--Jon
8 years 5 months ago #5983

Please Log in or Create an account to join the conversation.

  • Posts: 47
  • Thank you received: 6
Everything seems to work just fine now!
Thank you all very much.

Ciao,
Piero
8 years 5 months ago #5989

Please Log in or Create an account to join the conversation.

  • Posts: 47
  • Thank you received: 6
Hi,
while grepping through the zeq25 driver code for other things, I noticed that the command for getting the slewing status is coded as ":SE#", whereas the iOptron protocol manual says it should be ":SE?#".
I haven't had the chance to verify if and possibly how this mismatch impacts the driver functions, just wanted to point it out for now.

Thank you.
Piero
8 years 5 months ago #6043

Please Log in or Create an account to join the conversation.

I am aware about that, but I also saw :SE# somewhere else, so please test and let me know if you get notification after a slew operation is complete. If you don't get notified then :SE# does not work and we can try :SE?#
Last edit: 8 years 5 months ago by Jasem Mutlaq.
8 years 5 months ago #6044

Please Log in or Create an account to join the conversation.

  • Posts: 47
  • Thank you received: 6
I've tested it and it doesn't seem to behave correctly, even though it doesn't seem to do any harm.
The incorrect behavior is that I get a "slew is complete" notification as soon as the slewing starts, no matter how long the slewing itself takes.
However, I've also tried to modify the code by putting a :SE?# command and things don't change, so there must be something else.
I will try to sniff and verify the response from the mount to a :SE?# command and let you know.
Tested on a SmartEQ Pro (8408 HC).

Thank you.
Piero
8 years 5 months ago #6051

Please Log in or Create an account to join the conversation.

  • Posts: 47
  • Thank you received: 6
The mount behaves as expected and accepts both a :SE# and a :SE?# command, replying with a 1 while slewing and with a 0 while not slewing.
8 years 5 months ago #6053

Please Log in or Create an account to join the conversation.

Time to create page: 1.815 seconds