![]() ![]() While I have always been interested in this subject, it's been almost forty years since I was fortunate enough to take a first year Astronomy course at the regional College (now a University) where I live. In any event, I thought it would be convenient to have some astronomy software for regular Puppy releases also -for those of us who have a passing interest in this area but who don't need to run a release that is devoted entirely to this science. Much of the software in that release is rather dated, and I don't know the status of the project -though I found a download page for a version 1.01 here. My ultimate goal is to clean up the abstractions enough, that other drivers will be able to integrate the alignment subsystem with no changes to the code other than inheritance.It's been nearly five years since this announcement of a Pup for those who are interested in Astronomy. When I have all the issues figured out using this setup, then I'm going to re-do the temma driver for my NJP, which doesn't fit in the corner in my office. Hopefully I'll have more time later today, and can figure this one out.Īnd yes I know, we dont really need yet another variation on drivers for the skywatcher mounts, but my neq3 fits neatly in the back corner of my office, so I'm using it as the test case to integrate the alignment subsytem. Now it all works fine, so, this must be something in the initialization of the name property. So I changed my script to add -n\"SynScan\" which is exactly the same as the device default name. Using indistarter, the command going in is thisĮcho start indi_synscan -n\"NEQ3\" > /tmp/indififo When I started my test build, the command going into the fifo was this:. The command variations that cause this are below I am using 3.1 which came from your ppa, and using the 'connect and get device list' function to select from the drop down. Is there anything else that indistarter would be doing, that causes it to work with skychart, where a 'naked' startup like I'm doing causes it to fail ? indi_simulator_ccd -n \"testccd\" > /tmp/indififoĮcho start. When I do it thru the pipe, it's a pretty simple script.Įcho start. I'm trying to figure out what the difference is between the way I start things, and the way it's done by indistarter. BUT, if I start the exact same driver code using indistarter, the skychart connects and uses it just fine. The telescope connect panel shows the initial driver messages, then says 'server disconnected' and a few seconds later asks 'Is driver SynScan running'. Same if I start an indi server with a pipe, then start the driver thru a pipe. If I start my indi server from the command line, with synscan driver and a couple others, when trying to connect from skychart to the synscan mount, it starts to connect, then closes the connection to indiserver. One of the issues I ran into today, which has me a bit befuddled, regarding the synscan driver for a skywatcher mount using the handset. I am working with telescope drivers in development phases, and testing with a few different apps. I have a question regarding skychart, and indistarter. But this is probably not your issue because the clients give an explicit error in this case. If this still not work look at the port the server is listening. In the last version eqmodgui-0.1.0-7 I add an option in the Setup to set this device name, so you can change the value to "EQMod" for better compatibility. The device name can be changed to allow you to load two time the same driver for two different telescope for example.įor eqmod the default device name is "EQMod Mount", if you start the server from the command line with "indiserver indi_eqmod_telescope", this is what eqmodgui expect by default.īut the device name is "EQMod" if the server is started by Kstars, INDIstarter or another application that read the driver.xml file. The parameter that can make a client unable to find the driver is the device name. (The next version of Skychart will use INDIstarter for better compatibility) Kstars and Skychart for example have different default options. ![]() The reason you cannot connect from some client is probably because you not always start the server on the same way. There is also one in Eqmodgui if you press the "INDI setting" button. I suppose you meant the standard INDI GUI presentation as present in client like Kstars, DCD or other. OK, but there is no GUI delivered with the Indi Eqmod telescope driver, INDI is very clean about the separation between the base process (server, driver) and the clients.įor INDI Eqmodgui is a client, just like Kstars or Skychart, except it is specialized to manage the basic Eqmod operation. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |