Paul replied to the topic 'Guding gones wild in RA on Gemini 2' in the forum. 15 hours 1 minute ago

Magnus,

I can't say what happens with ST4 as my cable "broke" and I have not got around to repairing it as I decided to try Pulse Guiding.

It was not exactly obvious how to get it working but I managed and now I have no incentive to go back as it is one less cable to worry about.

Paul

Read More...

Paul replied to the topic 'Guding gones wild in RA on Gemini 2' in the forum. yesterday

Magnus,

I am using PHD2 as the guiding program and I attach to INDI using INDI mount. I have Pulse Guding enabled and although it has an issue where it will not maintain the driver setting - reported to PHD2, it works fine.

I notice you originally said that you had no problems under Windows, but I cannot see where you mention your operating system.

I am currently running Raspbian as the Ubuntu Mate version stopped recognising my QSI camera.

In the past I have found that wild swings are generally cuased by the software trying to handle the scope being too well balanced and contimually trying to correct it. You may be better off posting the question to the PHD2 forum as they have many years experience with this. I would try and unbalance the scope so it is slightly weigted east and either north or south and see if this has any effect.

Read More...

Paul replied to the topic 'Guding gones wild in RA on Gemini 2' in the forum. 2 days ago

Magnus,

I have experienced the wild swings, if you mean it suddenly slews to somewhere completely unrelated to where you want it to go - sometimes making the camera head towards the mount. I always make sure I can abort it from INDI, as I have found that when this happens the hand controller does not respond.

I have found that the best way to avoid this is to always perform a synch after a coldstart and then use align for the following slews.

I believe that it must be corrupting the model because the park at CWD still works correctly so it knows where it physically is. exactly what the problem is eludes me and is unpredictable. It means I cannot trust the mount when slewing and need to keep an eye on it. The only solution I have found is to perform a coldstart.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

Today, I rebuilt Ubuntu Mate from scratch on a new card and installed indi-full but it would not start up. After trying a number of things I decided to use the bleeding edge and kstars then started. After all this I am still having the same issue with my QSI538 not connecting.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

Further update.
Although I haven't finished my testing - the latest build on Raspbian is today recognising the QSI583 camera.

The apt-get version on Ubuntu Mate is still crashing.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

I have eliminated a number of things

1) It happens when the QSI583 is the only device connecting.
2) It happens when connecting all my devices mount/camera/guide camera/focuser and Wunderground.
3) It does not happen with older versions of kstars/INDI/ekos.
4) Every copy I have upgraded from a number of different versions (some about 6 months old) fail after the update.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

phomer60 wrote: I am going to do a complete build, however, I updated the Ubuntu Mate version today using apt-get to try and solve a problem with guidiing aborting after a few images.

Just to clarify the situation - the most recent apt-get update is now having the same problem with the QSI 583 camera but the lodestar is working.


Is this possibly just an ARM issue?

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

I am going to do a complete build, however, I updated the Ubuntu Mate version today using apt-get to try and solve a problem with gudiing aborting after a few images.

This is now having the same problem as the build I do my self.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

Built by running git pull and make install for indilib, 3rdpart and kstars.

Read More...

Paul replied to the topic 'QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

All devices are directly connected to the Raspberry Pi.

I assume something related to cameras has changed.

I get the following when trying to connect the QSI camera using the device manager.

2018-04-08T06:33:09: startup: /usr/bin/indiserver -v -p 7624 -f /tmp/indififoa931a3fe
2018-04-08T06:33:09: listening to port 7624 on fd 3
FIFO: start indi_qsi_ccd -n "QSI CCD"
With name: QSI CCD
FIFO: Starting driver indi_qsi_ccd
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=842 rfd=4 wfd=7 efd=8
2018-04-08T06:33:09: Client 5: new arrival from 127.0.0.1:33832 - welcome!
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 844 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #2
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=845 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 845 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #3
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=846 rfd=4 wfd=8 efd=9
Child process 846 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stdin EOF
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #4
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=847 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 847 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #5
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=848 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 848 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #6
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=849 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #7
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=850 rfd=4 wfd=8 efd=9
Child process 849 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 850 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #8
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=851 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #9
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=852 rfd=4 wfd=8 efd=9
Child process 851 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 852 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #10
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=853 rfd=4 wfd=8 efd=9
2018-04-08T06:33:09: Driver indi_qsi_ccd: indi_qsi_ccd: symbol lookup error: indi_qsi_ccd: undefined symbol: _ZN4INDI13DefaultDevice8SetTimerEi
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
2018-04-08T06:33:09: Driver indi_qsi_ccd: Terminated after #10 restarts.
Child process 853 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: stderr EOF
Child process 842 died
2018-04-08T06:33:09: Driver indi_qsi_ccd: restart #1
2018-04-08T06:33:09: Driver indi_qsi_ccd: pid=844 rfd=4 wfd=8 efd=9

Read More...

Paul created a new topic ' QSI and Lodestar cameras not able to be found' in the forum. 2 weeks ago

Current build on Raspbian.

Nothing is being written to the log files but the following is displayed. Other devices are being found.

2018-04-08T11:42:06 Unable to establish the following devices:
+ QSI CCD
+ SX CCD
Please ensure each device is connected and powered on.
2018-04-08T11:42:04 WunderGround is online.
2018-04-08T11:42:03 Losmandy Gemini focuser is online.
2018-04-08T11:42:03 Guider port from Losmandy Gemini is ready.
2018-04-08T11:42:02 Losmandy Gemini is online.
2018-04-08T11:42:02 Microtouch focuser is online.
2018-04-08T11:42:00 INDI services started on port 7624.
2018-04-08T11:42:00 Starting INDI services...
2018-04-08T11:41:34 INDI services stopped.
2018-04-08T11:41:32 Microtouch is disconnected.
2018-04-08T11:41:32 Losmandy Gemini is disconnected.
2018-04-08T11:41:32 WunderGround is disconnected.
2018-04-08T11:41:32 Disconnecting INDI devices...
2018-04-08T11:34:29 WunderGround is online.
2018-04-08T11:28:35 Unable to establish the following devices:
+ QSI CCD
+ SX CCD
Please ensure each device is connected and powered on.
2018-04-08T11:28:32 WunderGround is disconnected.
2018-04-08T11:28:32 Losmandy Gemini focuser is online.
2018-04-08T11:28:32 Guider port from Losmandy Gemini is ready.
2018-04-08T11:28:32 Losmandy Gemini is online.
2018-04-08T11:28:31 Microtouch focuser is online.
2018-04-08T11:28:30 INDI services started on port 7624.
2018-04-08T11:28:29 Starting INDI services...
2018-04-08T11:28:02 INDI services stopped.
2018-04-08T11:27:59 Microtouch is disconnected.
2018-04-08T11:27:57 Losmandy Gemini is disconnected.
2018-04-08T11:27:57 Disconnecting INDI devices...
2018-04-08T11:22:56 Losmandy Gemini focuser is online.
2018-04-08T11:22:55 Guider port from Losmandy Gemini is ready.
2018-04-08T11:22:55 Unable to establish the following devices:
+ QSI CCD
+ SX CCD
Please ensure each device is connected and powered on.
2018-04-08T11:22:54 Losmandy Gemini is online.
2018-04-08T11:22:52 WunderGround is disconnected.
2018-04-08T11:22:51 Microtouch focuser is online.
2018-04-08T11:22:50 INDI services started on port 7624.
2018-04-08T11:22:50 Starting INDI services...

Read More...

Paul replied to the topic 'Guding gones wild in RA on Gemini 2' in the forum. 3 weeks ago

Magnus,

I was thinking of the settings under options - calibration and guide.

My problem at the moment is that I don't have my camera and don't know how to bring up my settings without it.

Read More...

Paul replied to the topic 'Guding gones wild in RA on Gemini 2' in the forum. 3 weeks ago

Magnus,

I have used PHD2 and INDI guiding on a Raspberry Pi without issues with a Lodestar X2.

What camera are you using and what software settings are you using?

Read More...

Paul replied to the topic 'New rpi3 B+, would it be a straight SD card swap...?' in the forum. 3 weeks ago

It would be if you were running Raspbian and did an update first but Ubuntu Mate does not run.

Read More...

Paul replied to the topic 'Astroberry Server' in the forum. 4 weeks ago

If you have the Raspberry Pi 3 B+ I don't believe Ubuntu Mate currently supports it - at least that is what my testing has shown.

I have been compiling under Raspbian and although build errors occur the software seems to be working, although it is not my production system, which is using Ubuntu Mate with a Raspberry Pi 3 B and I have a Raspberry Pi 2 as back up. On those machines I have not experiencd any errors with updates using apt-get from the command line.

In the past, when using Raspbian and the update utility I always had space type errors but overcame them by switching to apt-get at the command line.

Regards

Paul

Read More...

Paul replied to the topic 'Changing focal length setting' in the forum. 1 month ago

Jasem,
Thanks, you have solved it.
I had forgotten that I set it up there.

Read More...

Paul replied to the topic 'Changing focal length setting' in the forum. 1 month ago

When I set the focal length that way it gives an error and does not change the setting. I tried on the mount control page and that holds until i disconnect and it goes back the 600mm setting when connecting again.

I will post a fuller description when I have access to the equipment again.

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!