norikyu replied to the topic 'indi-full : Depends: indi-nexstarevo but it is not installable' in the forum. 2 months ago

I tried again and it worked!
Thank you.

Read More...

norikyu created a new topic ' indi-full : Depends: indi-nexstarevo but it is not installable' in the forum. 2 months ago

Hi.

I installed INDI on a new PC, but I get an error.
Distribution is Ubuntu 17.10 & kernel 4.13.0.
Commands and logs are as follows.

$ sudo apt-add-repository ppa:mutlaqja/ppa
$ sudo apt-get update
$ sudo apt-get install indi-full
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 indi-full : Depends: indi-nexstarevo but it is not installable
E: Unable to correct problems, you have held broken packages.

I installed indi-nexstarevo.
$ sudo apt-get install indi-nexstarevo
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package indi-nexstarevo is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'indi-nexstarevo' has no installation candidate

Package not found.
The same error will occur even if "sudo apt-get update" is executed again.
Is Ubuntu 17.10 not supported yet?
Thank you.

Read More...

Paweł thanked norikyu in topic SkySafari middleware? 2 months ago
norikyu thanked Jasem Mutlaq in topic indi_canon_ccd segfault 4 months ago
norikyu replied to the topic 'indi_canon_ccd segfault' in the forum. 4 months ago

Hi.
I tried that.
It worked perfectly.
Thank you!

Read More...

norikyu created a new topic ' indi_canon_ccd segfault' in the forum. 4 months ago

Hi.
I ran Ubuntu on Intel Stick PC and installed INDI server and Kstars.
However, indi_canon_ccd crashes with a segmentation fault.
The environment and INDI log are as follows:

system environment:
Ubuntu 16.04
kernel 4.10
kstars-bleeding 5:17.04+201707240921~ubuntu16.04.1
libindi1 1.5.0+r3264~201708021121~ubuntu16.04.1

dmesg log:
[ 9415.292466] indi_canon_ccd[11557]: segfault at 120 ip 00007f160f37c0df sp 00007ffce0b62840 error 4 in libindidriver.so.1.5.0[7f160f348000+da000]
[ 9415.831970] indi_canon_ccd[11563]: segfault at 120 ip 00007fc314f010df sp 00007fffe97c8a70 error 4 in libindidriver.so.1.5.0[7fc314ecd000+da000]
[ 9416.361028] indi_canon_ccd[11570]: segfault at 120 ip 00007f169a1fd0df sp 00007ffdbc55a3b0 error 4 in libindidriver.so.1.5.0[7f169a1c9000+da000]
[ 9416.899617] indi_canon_ccd[11575]: segfault at 120 ip 00007f62e03d70df sp 00007ffccb1538f0 error 4 in libindidriver.so.1.5.0[7f62e03a3000+da000]
[ 9417.430640] indi_canon_ccd[11580]: segfault at 120 ip 00007fb14146a0df sp 00007ffd7fce3590 error 4 in libindidriver.so.1.5.0[7fb141436000+da000]
[ 9417.960241] indi_canon_ccd[11585]: segfault at 120 ip 00007f7e71d370df sp 00007ffdce58d310 error 4 in libindidriver.so.1.5.0[7f7e71d03000+da000]
[ 9418.492451] indi_canon_ccd[11590]: segfault at 120 ip 00007fc0534fe0df sp 00007ffd333a3790 error 4 in libindidriver.so.1.5.0[7fc0534ca000+da000]
[ 9419.029768] indi_canon_ccd[11597]: segfault at 120 ip 00007f6224f840df sp 00007ffed398a110 error 4 in libindidriver.so.1.5.0[7f6224f50000+da000]
[ 9419.593806] indi_canon_ccd[11602]: segfault at 120 ip 00007f8f498c80df sp 00007fff0927f820 error 4 in libindidriver.so.1.5.0[7f8f49894000+da000]
[ 9420.117321] indi_canon_ccd[11607]: segfault at 120 ip 00007fa3e948d0df sp 00007ffe8918a240 error 4 in libindidriver.so.1.5.0[7fa3e9459000+da000]

File Attachment:

File Name: log_11-43-58_2017-08-03-2.txt
File Size: 17 KB


Any idea?
Thank you.

Read More...

norikyu replied to the topic '"Aborting Autoguide" issue with Internal Guider' in the forum. 7 months ago

Hi.
I tested the sequence with the latest Ekos.
The auto guide using external lin_guider worked perfectly and dithering was successful.
The sequence was not aborted and worked Great!
thank you!

Read More...

norikyu replied to the topic '"Aborting Autoguide" issue with Internal Guider' in the forum. 7 months ago

Hi. knro.
I'm in trouble.
I think this problem is similar to the problem of the following thread.

indilib.org/forum/ekos/2254-aborting-aut...rnal-lin-guider.html

Is the total time of the guide capture timeout including the delay incorrect?
Is it the same when dithering is used with external lin_guider?

Read More...

norikyu replied to the topic '"Aborting Autoguide" issue with external lin_guider' in the forum. 7 months ago

Hi kcobby. thank you for advice.

I know at OAG that a small communication delay over the network worsens the guide.
Therefore, I use external lin_guider.

I would suggest turning OFF the dithering to measure the capture peculiarity.


I turned off dithering and tried it.
The sequence ended normally without being aborted.

I think that it is strange what to shoot a 128 pixel image.
I do not know what is the correct behavior.
Is this a bug?

Read More...

norikyu replied to the topic '"Aborting Autoguide" issue with external lin_guider' in the forum. 7 months ago

thank you for the advice.
It helps me a lot.

Sequence aborting still occurs.

  • Set to use external lin_guider.Internal guider is not used.
  • Make a shooting sequence. (Ex. Exposure 15 sec, Count 5, Delay 5 sec)
  • Start autoguide and sequence.
  • First shot. success.
  • Dithering execution. success.
  • Suddenly, an image of 128 pixels is taken.
  • Guide is aborted.
  • An image of 128 pixels and a full size image are taken.
  • The sequence is aborted.
why?
What is a 128 pixel imagese?

Read More...

norikyu created a new topic ' "Aborting Autoguide" issue with external lin_guider' in the forum. 7 months ago

Hello.
I am using the latest Ekos by "apt-get upgrade".
When guiding with the external lin_guider, shooting aborts every single shot.

It is a guide log right after aborting.

2017-05-23T12:33:10 Autoguiding aborted.
2017-05-23T12:33:09 Exposure timeout. Aborting Autoguide.
2017-05-23T12:33:06 Exposure timeout. Restarting exposure...
2017-05-23T12:33:04 Exposure timeout. Restarting exposure...
2017-05-23T12:33:01 Guiding resumed.
2017-05-23T12:33:01 Dithering completed successfully.
2017-05-23T12:32:06 Autoguiding started.

Exposure processing is running in the external guide.
Is this a correct process?

Read More...

Jasem Mutlaq thanked norikyu in topic SkySafari middleware? 7 months ago
norikyu replied to the topic 'SkySafari middleware?' in the forum. 7 months ago

Hi.
I made a patch corresponding to commands <SG>, <SL>, <SC> from SkySafari.
This patch can set the time information from SkySafari to the corresponding mount.
Turn on "Set Time & Location" of SkySafari.
You will be able to set the latitude, longitude and time using the GPS of the smartphone.

It worked with Celestron AVX and SkySafari 5 Plus (Android).
Someone please test this patch.

Read More...

norikyu replied to the topic 'SkySafari middleware?' in the forum. 7 months ago

I tested it with RPi3 INDI server and celestron AVX.
I could use SkySafari 5. Great!

Does "Set Time & Location" in "Common Setting" of SkySafari work?
This option is useful for initial setting to AVX.

Read More...

norikyu replied to the topic 'Dithering is not executed with external lin_guider' in the forum. 9 months ago

Hello rumen.
Thank you for the new lin_guider announcement.

I tried dithering with a combination of lin_guider 4.2.0 and kstars 2.7.6.
It worked so perfectly!
I appreciate lin_guider and ekos, two great software.
Thank you.

Read More...

norikyu replied to the topic 'Dithering is not executed with external lin_guider' in the forum. 9 months ago

Hi, knro.
You are welcome. Thanks for the hint.
I modified it using raw data as you suggested.
This is going very well.

The patch is as follows.
/kstars/ekos/guide/externalguide/linguider.h

 private:
     void sendCommand(LinGuiderCommand command, const QString &args = QString());
     void processResponse(LinGuiderCommand command, const QString &reply);

     QTcpSocket *tcpSocket;
+    QByteArray rawBuffer;

/kstars/ekos/guide/externalguide/linguider.cpp
 LinGuider::LinGuider()
 {
+    rawBuffer.clear();
     tcpSocket = new QTcpSocket(this);



 bool LinGuider::Connect()
 {
     if (connection == DISCONNECTED)
     {
+        rawBuffer.clear();
         connection = CONNECTING;


 bool LinGuider::Disconnect()
 {  
+    rawBuffer.clear();
     connection = DISCONNECTED;
     tcpSocket->disconnectFromHost();



void LinGuider::readLinGuider()
{
    while (tcpSocket->atEnd() == false )
    {
        rawBuffer += tcpSocket->readAll();

        while(1)
        {
            if (rawBuffer.count() < 8)
                break;

            if (Options::guideLogging())
                qDebug() << "Guide:" << rawBuffer;

            qint16 magicNumber = *(reinterpret_cast<qint16*>(rawBuffer.data()));
            if (magicNumber != 0x02)
            {
                emit newLog(i18n("Invalid response."));
                rawBuffer = rawBuffer.mid(1);
                continue;
            }

            qint16 command = *(reinterpret_cast<qint16*>(rawBuffer.data()+2));
            if (command < GET_VER || command > GET_RA_DEC_DRIFT)
            {
                emit newLog(i18n("Invalid response."));
                rawBuffer = rawBuffer.mid(1);
                continue;
            }

            qint16 datalen = *(reinterpret_cast<qint16*>(rawBuffer.data()+4));
            if (rawBuffer.count() < datalen + 8)
                break;

            QString reply = rawBuffer.mid(8, datalen);
            processResponse(static_cast<LinGuiderCommand>(command), reply);
            rawBuffer = rawBuffer.mid(8+datalen);
        }
    }
}

To solve multiple command responses and fragments, I added a buffer using QByteArray as a private member of the LinGuider class.
And, I rewrote LinGuider::readLinGuider().

Also, I modified LinGuider::processResponse ().
 void LinGuider::processResponse(LinGuiderCommand command, const QString &reply)
 {
 :
     case DITHER:
-        if (reply == "OK")
+        if (reply == "Long time cmd finished")
            emit newStatus(GUIDE_DITHERING_SUCCESS);
        else
            emit newStatus(GUIDE_DITHERING_ERROR);
This fix is not the best, but it is necessary for dithering to work for the time being.
A better answer is as proposed by rumen.

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!