Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 6 days ago

After another look the mount control is working fine. I did have a long delay before the first move and after that it worked well. Some operator error as well as I was holding down the buttons rather than toggling. I did get a timeout error early on but that may be due to holding down the button.
I see that the Telescope Simulator labels the slew speeds as Max/Find/Center/Guide rather than 1x/2x/3x/4x which is more accurate. Maybe that can be incorporated into the driver. Odd that the lx200_telescope driver does not do this by default.
If I make changes can I submit with a pull request? No issue if you prefer to keep it inhouse for now - just offering to help where I can.
Maybe Jasem can also advise on coding conventions. I tend to overload virtual methods to customize whereas the new driver seems to write a parallel method and invoke it. I prefer get/set terminology to the query... naming used.

Read More...

Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 7 days ago

I did have them set from ASCOM but the Slew speed was still slow. I'm a developer too so I'll dive into the code. When do you think you'll move the code to a branch of INDI?

Read More...

Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 7 days ago

Looking into things a bit more. I see that the StarGo ASCOM driver sends guiding pulses as %05d format versus the lx200 default of %04d. Not sure if this is a problem for the mount or not.
Also noticed that using the mount control, slewing even at highest speed was slow. I need to look deeper into this as I thought the default behaviour was that the 4 speeds correspond to Guiding, Centering, Finding and Slewing at the speeds set for each of those.
At face value, the INDI driver fixes an issue I'm having on ASCOM whereby there is often a long wait after a guide pulse is sent before PHD2 is informed that guiding has completed. I believe this is a bug in the ASCOM driver.

Read More...

Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 weeks ago

Aha. Just saw Wolfgangs code where 4 means Moving at low speed to refine. That makes sense. In any case no problem for PHD2 as it only polls for IsGuiding on ASCOM mountsand even then it is apparently not reliable.

Read More...

Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 weeks ago

Great to see this work taking place. I am keen to help out if I can. I've had to revert to Windows since getting my M-Uno

CanisUrsa wrote: I have the ability to set the tracking rates and slewing rates. I haven't figured out how to query what the currently selected tracking rate and slewing rate is. One status command you might be interested in is :X34# it will return something like m00# where the first 0 is for RA, second 0 is for DEC. The higher the number, the faster that axis is moving. m10# indicates RA tracking only while m54# would indicate a fast slew on RA, and slightly slower slew on DEC.

I don't think that is quite right. I've been chasing down an issue in the ASCOM driver where it fails to notify PHD2 when a guiding pulse is complete till very late. So in response to a guiding command Mg (followed by n/e/s/w for direction and nnnnn for duration in ms) e.g. Mge00678 a follow up X34 command returns m40 meaning the mount is guiding in RA. Once guiding is complete the X34 command returns m10. At least thats how it looks.

Read More...

Ken Self replied to the topic 'Polar Alignment with QHY Mini-Guidescope and QHY 5II-M' in the forum. 6 months ago

Try capturing an image with the QHY 5II-M and plate solve that directly to see if that works. It might be just the plate solve settings.

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

Still getting errors with the "Unrecognized error code"
Not able to disconnect except by closing down Kstars

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

I built libindi on the VM and TCFS driver no longer crashes. However, it seems to have problems processing commands.
Kstars and Indi logs attached.
BTW - is it possible to change INDI log filenames to change ":" to some other character? Windows can't open the files when it contains ":"

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

At least now I can reproduce the error at will. Attaching gdb backtrace

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

Acting on a hunch I renamed the Optec TCFS config file to effectively disable it. After that I renamed it back and the driver failed so the issue is related to reading the config file.
Attaching the offending file (with .txt extension added to keep the forum software happy) just in case it helps

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

I ran indiserver on my x64 Ubuntu VM.
Like on the RPi3 it runs ok until the config file is saved from Ekos. Then it wont start ever again. Attaching the output from gdb (only marginally more helpful than on the RPi3) plus indi and kstars logs. I can view the indi logs in the VM but attempts to copy them result in a "protocol error" and I cannot extract or view anywhere else.
I cannot connect to the driver because it crashes before the listener starts up.

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

I'll give that a try and take notes as I go. Ran out of time tonight so will try tomorrow

Read More...

Ken Self replied to the topic 'TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

Not sure if this is very helpful other than that it confirms a segfault. What's odd is that it worked the first time.

Read More...

Ken Self created a new topic ' TCFS focuser stopped working - driver fails to load' in the forum. 6 months ago

I just got myself a nice new Optec TCF-Si focuser.
Hooked it all up and tested on windows with no problems.
So next test was to use it with INDI last night.
I was using Kstars on my Windows 8.1 PC connecting to a Raspberry Pi3 running Ubuntu Mate
Got the drivers started on the Raspberry Pi - all good.
Minor issue connectinf to the TCF as I think it was initializing In due course it connected. So far so good.
Saved the config file as per the warning.
It was connected to ttyusb0 as I had forgotten to reconnect the EQ6 cable. So EQMOD at first failed then I got it connected to ttyusb1.

Next I tried the focuser module. Unfortuantely I forgot to turn on Ekos logging for that module.

Anyway it seemd to be working ok until Kstars crashed.

On estarting I could not get the TCFS driver to load. All other drivers loaded ok (EQMOD, ZWO_CCD, ASI_WHEEL)
Tried starting indiserver with just the TCFS driver and no good.
Tried to direct output to a log file but nothing produced.
There is also no INDI driver log for TCFS or even a folder - there are folders and logs for all the other drivers

Attached are the Kstars logs from Windows and the command line output from indiserver trying to start the TCFS driver
Could it be some sort of permissions problem?

Read More...

Ken Self replied to the topic 'indi_sx_ccd crashing' in the forum. 7 months ago

I'm guessing its related to the implementation of the Sky Quality Simulator 3 days ago. XML file missing perhaps?

Read More...

Ken Self replied to the topic 'indi_sx_ccd crashing' in the forum. 7 months ago

Thats the same error I'm getting with the indi_asi_ccd driver. It also crashes straight after the snoop on SQM SKY QUALITY

Read More...

Ken Self created a new topic ' indi_asi_ccd crashing' in the forum. 7 months ago

Tried to start indiserver but it kept failing on loading the indi_asi_ccd driver.. I thought it was working less than a week ago after the upgrade to latest asi driver. I did a sudo apt-get dist-upgrade and sudo apt-get -f install but there was nothing to update. Even tried sudo apt-get --reinstall indi-full to no avail
This is on a Raspberry Pi3 running Ubuntu Mate 16.04
EQMOD and indi_asi_wheel drivers are ok
indiserver -vvv output attached

File Attachment:

File Name: indi_asi_ccderror.txt
File Size: 35 KB


Read More...

Ken Self replied to the topic 'Live Preview - ASI1600MM-Cooled via RPi' in the forum. 7 months ago

Is it a bandwidth problem? May need to set the USB limit lower

Read More...

Ken Self replied to the topic 'Cone Error Correction assistant.' in the forum. 7 months ago

Cone error is fairly easy to measure with any of the polar alignment tools that work in the polar region. Once you identify the centre of rotation; any cone error is the component of the offset of the centre of rotation fom the centre of the sensor that is orthogonal to the declination direction. It is unaffacted by polar alignment. The Static PA module I just added to PHD2 has the functionality to display cone erro but is disabled. Something similar could possibly be added to Ekos polar alignment

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!