Meant to ask, what are the clear dimensions that you are using for the opening? I am looking at doing something similar but I am having trouble deciding how much clearance I need. Is there some relationship you are using? For example, how long is the longest point of your setup (i.e. the length from the tip of the counter weight shaft to the top of the scope.) How much clearance did you leave? Thanks and I hope you are making progress with your network.....

--Jon

Read More...

How long is that extension cord? I used one during an experiment and found it to be causing poor signal. Maybe you could try losing the extension cord and try a longer ethernet cable temporarily as an experiment.

Read More...

I am using the TP-LINK AV1200 powerline adapters and they have been pretty solid performers. Make sure you're not feeding them through surge protectors or powerstrips or you will likely have issues as these devices tend to pull the signal down and may cause frequent drop outs. As a matter of fact, you don't even want any of those devices on the same circuit if possible. They are affectionately known as signal suckers!

--Jon

Read More...

Outstanding......I just read through your build thread and I say kudos to you on a magnificent job!

Read More...

Thanks Peter. 32 bit version is working. The only issue I see is that when selecting a target and choosing 'Track" from within kStars, after the scope slews to the target, the kStars message window still indicates "slewing" rather than "tracking" after it completes the slew to target. It does seem to be tracking though. My real scope is out of commission at the moment with a bad worm gear. Once I make the repairs, I'll try it out under the stars.
When using an ASCOM camera within EKOS, as I mentioned earlier, there is no option to select the type of image such as light, dark, etc. Again not a major problem but thought I should point it out.
Thank you for all of your efforts with this. It is a great compliment to kStars and INDI in general.

--Jon

Read More...

I did test the 64 bit version and it seems to be working......

--Jon

Read More...

Do you have 32 bit version? The 32 bit link isn't working....Thanks.

--Jon

Read More...

Sorry about that...I have been having some issues with this thread and replies, I don't know what happened...

--Jon

I have attached the log from INDI server for windows as well as kStars log. There is no option in EKOS control panel to enable logging for ASCOM telescope sim....

--Jon

Read More...

I've had some time to play around with this the past couple of days and am seeing a few issues.

1. When connecting to the telescope simulator from EKOS, the site longitude gives an error "Property SiteLongitude The property value is out of range " the actual site longitude is -77:32:42 but EKOS uses 282:33:52. I can manually set the longitude in the control panel however. Even after manual correction, the scope crosshairs never move in kStars.

2. The scope simulator never moves when trying to track an object in kStars. i.e. Right click on target and select track and nothing happens.

--Jon

Read More...

Are we talking about the same camera? I wasn't aware that the DSCI II had a controllable fan. Anyway, I pretty much abandoned working on the driver since INDI Server for Windows gave me access to the ASCOM driver for the camera.
I do have a firmware dump for the DSCI II camera but was never really clear on if I could freely post it here.

--Jon

Read More...

Jasem,
When using the INDI Server for Windows (from the Linux VM), the ASCOM CCD (Simulator or real camera) isn't allowing me to choose a type. (Light, Flat, etc.) The dropdown is disabled.

--Jon

Read More...

We have a winner!!! It is working now! THANK YOU!!

--Jon

Read More...

The really strange part of this is that I never have installed this until 9/5/2016 which was version 2.2. So, I don't know where version 2.0 would have come from.

--Jon

Read More...

I don't know what it could be. I just downloaded it on a different pc and it also shows 2.0. The file name is INDI_Server_32_2.2.2.exe

--Jon

Read More...

After manual clean, the same result; no download. The about dialog still shows 2.0 but the add/remove programs dialog shows 2.2.2. Maybe a good idea to append the version info into the log file initialization?
Would it be possible to pass in a 'dummy' temperature for these cases so get_CCDTemperature still returns something?

--Jon

Read More...

Let me do a clean uninstall re-install of it by manually removing files. Maybe the older version isn't being removed completely for some reason. I will report back soon....
About dialog is showing 2.0?
--Jon

Read More...

Looks like this camera just isn't going to cooperate....still no download. Thank you for trying.

--Jon