The Orion version of the IMX269c is said to be a rebrand of the ToupCam IMX269c cameras but uses different SDK and cannot use the ToupCam drivers in INDI. Can anyone confirm this please? INDI does appear to have StarShootG drivers - but can anyone confirm that they communicate and do so properly with the Orion G21? Thanks!
Any advice re parameters in the INDI driver and EKOS is appreciated! Number of clicks?
I am unable to plate solve or capture images with the Camera CCD Simulator in MAC EKOS 3.5.8 with GSC installed despite different gain settings of zero to 100 as well as different exposure times up to 5 seconds with Binning 1:1 or 2:2. Any suggestions?
Apparently it is a stellarsolver mismatch. The PPA apparently did not have the correct version (2.2) which caused issues. The newest PPA now works.
Suggest purging KStars completely and then reinstalling to make sure correct stellarsolver is being used.
For Clarification: Interestingly, the crash does NOT occur when running the 3.5.8 Stable release in Linux Mint native on my Thinkpad. The above crash occurs when I load the Sim profile. It contains the Telescope Simulator and CCD and Guide simulators and my Sharpstar scope and ZWO guidescope entries. This is the same setup that I have tried in the native LInux setup vs. the Virtualbox Linux install - but the crash did NOT occur on the Virtualbox install with the prior 3.5.8 beta nightly installation (but did occur with the 3.5.7 stable install) so I am now obviously angry with myself that I 'updated' to the Stable release from the beta.
No sure what to do at this point. I wanted to run KStars in LInux because I wanted to connect my devices directly to the laptop rather than having to use Stellarmate version and the WIndows version cannot run Indi and I wanted to also run Sharpcap without having to reboot to Windows from Linux. My current work-around was to use Virtualbox in Linux, load Windows into Virtualbox and then install Sharpcap into my Windows inside Virtualbox but having the ability to run KStars in Linux inside VIrtualbox would still be nice. Any suggestions are appreciated!
I Had a problem with KStars crashing with Simulators which was solved by installing the nightly build 3.5.8 beta. I got a notification that 3.5.8 Stable had been released so I attempted to install the Stable release instead of the Beta think this would be a good thing. However, The Stable release repository download was actually 3.5.7 which was causing the crash so I went to the nightly build repository again and when I installed KStars-blueing, the 3.5.8 Stable release installed BUT, now it crashes again with the Telescope and CCD Simulators. ????? What to do????
I have Kstars 3.5.7 installed on a Virtualbox in my Lenovo Thinkpad running Windows 10. I have also run Kstars from my Ubuntu Linux Live USB and the same things occurs.
I have the appropriate Index files installed. When I try to use the Simulator (Telescope Simulator, CCD Simulator, Guide Camera Simulator), I can go to say M31 and then, when I run the Align Module with Capture and Save and Slew to Target using either the Primary CCD or the Guide CCD (simulators of course) and no FW or with FW, Binning 2x2 or 4x4 Primary Scope set to FL 268 and f 4.4 (Sharpstar 61 w/ reducer), with all running fine in INDI Server, KStars crashes. The crash does NOT occur on my Mac also running KStars 3.5.7 with the same parameters as above. Please help.
Apparently this has something to do with Virtualbox - I retried the installation using Parallels as the VM and all goes fine so any help in VirtualBox settings would be appreciated, Thanks!
I have installed various version of Ubuntu into a VM Virtualbox on my windows machine.
I use the following
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
When I try to install Kstars-bleeding with Indi-full or Indi-full gsc, it will install but will not run.
That is, the icon is there and the app is in the list of apps but it will not start up.
When I hit click on the app, nothing happens.
However, I CAN get a functioning Kstars if I use the intall Kstars instead of install Kstars-bleeding, but when using only Kstars, v 3.4.3 is installed.
Jasem (not James)... OOPS Sorry.
Thanks for your reply!
I WAS able to get it working this morning with the EQMOD cable and the EQMOD driver. Not at all sure why I could not get it to work yesterday...
Who knows. Perhaps it was not having the serial ports configured correctly on my PC???
Anyhow, it works now, so thanks for confirming that you had gotten it to work which prompted me to retry - with success!!
James. Thanks very much for the quick reply! I have tried several times to get the wireless thing to work and have tried it with both the Hot Spot and the alternate configuration. I have not been successful in either approaches. Regarding the 'preferred' method using the Station Mode, I could connect to the mount with my phone app and then modify the Station mode with the Stellarmate IP of 10.250.250.1 and PW. However, after APPLYING the configuration to the mount, it does not seem to save it correctly in that after that, when I change my phone WiFi to the Stellarmate Wifi address, I cannot access the mount via SynScan on my phone and when I go back again to using the SynScan Wifi and re-connecting with the mount, I CAN connect again but the mount does not seem to save the Station configuration. Also. after again re-setting the mount to Station Mode at the Stellarmate IP and PW and again applying (via my phone of course), when I update the configuration in EKOS with the AZGTi driver, EKOS will not connect to the mount.
I saw a subsequent post by Mr. Wilson indicating that the EQMOD driver works with the serial cable that I have and this morning, I re-set it up using the cable and after deleting any other configurations in EKOS and re-setting ups a new one and then setting the serial port for the EQMOD as directed, it WORKS now (using the connect to Stellarmate from my PC and the Stellarmate Wifi on my PC). I have NO idea why I could not get it to work yesterday (which was a day of frustration), but it does work today (so who knows what I was doing incorrectly). So I can get EKOS to communicate with the EQMOD driver and EQMOD serial cable, but I am not able to get the wireless connection scheme to work by either Station mode or Hot Spot mode...
Not sure what I am doing incorrectly and not sure why the mount will not save the Station configuration. But thanks for the help.
So far as updating my EKOS in Stellarmate, I have not been able to figure that out at this time. I can connect to Stellarmate via my phone app but I don't see any place to update to the latest version of EKOS. Sorry for my ignorance. If you can provide a screen shot of an iPhone app and where to do the update, that would be great. Also, I have my Stellarmate connected to an HDMI monitor and keyboard/mouse but do not find anyplace to update with that method as well.
Hi. I am unable to find a driver for my AZ-GTi mount in EQ mode connected to Stellarmate via an EQMOD USB cable direct from the mount to the computer.
I can control the mount without difficulty with the SynScan Pro app wirelessly.
However, I would like to use EKOS with Stellarmate.
I can connect to Stellarmate via stellar mate.local and my ZWO cameras, connected via USB to the Stellarmate device (RasperryPI running Stellarmate).
I have tried every choice in the EKOS list for device drivers: AZGTi, SynScan and SynScan Legacy, Skywatcher Adventure, and all the Skywatcher drivers as well as EQMOD driver itself.
None of the drivers allows a connection.
I CAN connect to my iOptron Cub and CEM40 but no matter which driver I choose, I am unable to connect to the AZGTi.
Using my SynScan app and wireless connection, the app is able to give me the choice of AltAz or EQ mode and after choosing EQ mode, I am able to control the mount from the SynScan app.
It seems very strange that given the popularity of the AZ-GTi mount and the numerous posts of using it in EQ mode, there would not be a suitable driver for this in EKOS.