Ken Self replied to the topic 'ST4 CAMERA RISING TECH compatble INDI??' in the forum. 3 days ago

Naburko wrote: That's good to know. oaCapture support also ARM architecture so I think it would be good solution for ToupCam, Altair and also Rising Tech camera users.

I have SDK from RisingTech and it seems drivers are written in C so maybe it could be used with Raspberry Pi. I can send it to developers of INDI

Apologies for any confusion as I was responding to sk_vishnawath's issues with the ToupTek downloads. The ToupTek drivers are only available for x86 and x64

Read More...

Ken Self replied to the topic 'indi-eqmod always shows side of pier: WEST' in the forum. 3 days ago

I suspect this reflects EQMOD's ASCOM origins. In ASCOM SideOfPier is acknowledged as a misnomer. It more closely represents the position of the declination axis. On the Dec axis there are two sets of coordinates ranging from -90 to +90 so a given declination could be in two different places (which in turn can affect RA). So ASCOM Side of Pier indicates whether the declination is the one to the east of the pole or west of the pole.
I'm not sure what INDI expects the SideOfPier to indicate.

Read More...

Ken Self replied to the topic 'ST4 CAMERA RISING TECH compatble INDI??' in the forum. 5 days ago

I've got a rebadged version f the same camera - USB product id is b134
To get it to work with ToupLite I had to replace libtoupcam.so with a version provided by the retailer. Also added a line to the udev rules file for product id b134.
Also got it to work with oacapture. Once again I had to replace the libtoupcam.so provided with oacapture with the retailer supplied one.
If you want to you could try by downloading from www.myastroshop.com.au/guides/prostar/do...ToupLite-1_0-x64.tgz
You have to expand the download, uninstall any current version of ToupLite (from /usr/local/ToupLite run the uninstall script), then install the downloaded version. I found the ToupLite app installed from there just hangs. So I copied the two .so files from /usr/local/ToupLite then uninstalled ToupLite. I then reinstalled ToupLite from the ToupTek website then overwrote with the two files I saved. And for good measure edited 99-toupcam.rules to add product id b134. After that ToupLite worked.
For oacapture, after installing I replaced its version of libtoupcam.so with my saved version and it too started to work.
I'm wondering if the oacapture code could be adapted into an INDI driver for the ToupCam camera? It is written in C. Indeed, if the author could be persuaded to support INDI drivers from oacapture it could be a win-win. oacapture gets a much bigger range of cameras to use and INDI can support the various Touptek / Altair / Rising Tech cameras.

Read More...

Jasem Mutlaq thanked Ken Self in topic Indi on AAEON UP 2 weeks ago
Ken Self replied to the topic 'Indi on AAEON UP' in the forum. 2 weeks ago

Tonight I connected the Active USB3 cable via a USB2 hub to the UP and now everything connects. This adds credence to my hypothesis that it is the Active cable at fault. That wont be a problem once I mount the UP on the scope. But until then I wont be able to test how well the USB3 works. Nevertheless, saving a test image to the eMMC drive was much faster than on my desktop - even using just USB2. A couple of small decisions to make regarding the overall setup as to: whether to use a Pi3 to control mount, guide cam and PHD2 or load it all onto the UP or run PHD2 on the client. At present I'm leaning towards everything on the UP as it seems to have more than enough capacity.. And should I capture images to the eMMC drive or to a removable USB stick so its quicker to transfer to the desktop for processing. And thirdly - how to arrange the network.
What I can say so far is that the AAEON UP has been a breeze to set up. Somewhat easier than the Pi3 in main due to being able to use regular Ubuntu instead of Mate. So far I've only installed Ubuntu 16.04 as that is what the instructions said to use.

Read More...

Ken Self replied to the topic 'Indi on AAEON UP' in the forum. 2 weeks ago

Indeed there are. The trick was to find one with a USB3 port and which is x86 based. I've got one camera whose Linux driver is only available on x86 and I'd like to operate the ASI1600 on USB3.

Read More...

Ken Self replied to the topic 'Indi on AAEON UP' in the forum. 2 weeks ago

Connected to UP to a powered USB3 hub with all devices connected through that via an active USB3 cable and running headless through x11VNC. Everything seems to connect EXCEPT the ASI120MM-S. For some reason it isn't showing up in lsusb.
It does show up on my Windows 10 machine when the active cable is connected to a USB2 port , and in turn on the Ubuntu VM on that machine. The USB3 port on the Windows machine always seemed a bit flakey, which is why I connect through USB2. But now I suspect the active cable as the culprit.

Read More...

Ken Self replied to the topic 'Indi on AAEON UP' in the forum. 2 weeks ago

Noone? So I bit the bullet and ordered the AAEON-UP Core with 4Gb memory and 64GB eMMC www.up-board.org/upcore/
No real problems setting it up but some things to watch for:
It needs a 5V power supply and up to 4A capacity through a standard 5.5/2.1mm barrel plug.
If you want the two USB2 ports you need the 10pin to 2xUSB2 adapter cable . Otherwise there is just the one USB3 port.
The onboard wifi does not work by default. You need to install the drivers first. So to do that you need some other sort of network connection via USB.
Also the wifi module has no antenna so it has a very short range. I've ordered an external antenna with UFL connector. In the meantime I just sit it right next to the access point.. Alternatively I can use an external Wifi dongle till I get the antenna.
Bluetooth is also not enabled by default. Took a bit of trial and error to get it working.
Apart from the above it all installed pretty easily and is noticeably faster than the Pi3. I've installed indi-full and phd2 on it so next step is to test as an indi server. In particular I want to see how it goes with the ASI1600 over USB3

Read More...

Ken Self replied to the topic 'Unguided RMS?' in the forum. 3 weeks ago

With PHD2, if you've done a calibration already you can use the Auto-restore calibration option.
If you have never done a calibration before you would have to manually enter some calibration parameters or do a proper calibration. Otherwise it will automatically start to calibrate.
A proper calibration is needed if you want to see the profiles for RA and Dec as it needs to know how the camera is oriented.

Read More...

Ken Self created a new topic ' Indi on AAEON UP' in the forum. 4 weeks ago

Is anyone using Indi on an AAEON UP? I'm interested in an x86 device with USB3 and this looks like a good option - as long as it works.

Read More...

Ken Self replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 3 months 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. 3 months 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. 3 months 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. 3 months 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. 3 months 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. 8 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. 9 months ago

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

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!