Yes, I'm writing a client.
I think I found the issue, it's a 16803 chip, I was bin by 1, it took 3 minutes to get it across the network.! Even with a 1GB network.
When I bin by 4, it seems to work reasonably well.

Thanks.
Dan

Read More...

Hi all,
Now I'm trying to make the FLI camera work.
I'm now taking images, it works fine.
I get an XML message:
"<message device=\"FLI CCD\" timestamp=\"2018-10-25T15:57:24\" message=\"Exposure done, downloading image...\"/>"
But it's unclear what I should do next. Is it something with a "blob" command?
Thanks.
Dan Gray
siderealtechnology.com/SLO

Read More...

Thanks Eric,
I think that was it. I was mixing the package and the source.
I did a complete make, and I think it's working now.
I do have an issue, I'll post it as a different topic...
Thanks again,
Dan

Read More...

I believe I downloaded the source and compiled it. I also installed by sudo apt-get etc.....

If I try to install again, it says everything is already up to date.

dan@DansLinux:~/Projects/indi$ sudo apt-get install indi-full kstars-bleeding
Reading package lists... Done
Building dependency tree
Reading state information... Done
kstars-bleeding is already the newest version (6:2.9.8+201808180747~ubuntu16.04.1).
indi-full is already the newest version (1.7.4~201807251706~ubuntu16.04.1).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
dan@DansLinux:~/Projects/indi$

Read More...

Hi all, I'm struggling along, trying to learn indi, I'm making some progress now, but I'm having trouble with my ubuntu 16 (kernel 4.15.?
This works on my rasberry pi 3.
indiserver -v indi_simulator_ccd

But on my linux box (ubuntu 16 (kernel 4.15.nn), I get this:
2018-10-23T17:36:53: Driver indi_simulator_ccd: indi_simulator_ccd: symbol lookup error: indi_simulator_ccd: undefined symbol: _ZN4INDI3CCD16ExposureCompleteEPNS_7CCDChipE
2018-10-23T17:36:53: Driver indi_simulator_ccd: stderr EOF
Child process 20013 died
2018-10-23T17:36:53: Driver indi_simulator_ccd: Terminated after #10 restarts.
2018-10-23T17:36:53: good bye

Any help would be appreciated..
Thanks
Dan Gray
Sidereal Technology.

Read More...

Figured it out! I was running the SiTechExe software one the windows machine in the debugger. When I run it standalone on the windows machine, I was able to connect from the linux box!
Thanks Jasem for helping me get started.

Dan Gray

Read More...

Hi all,
Thanks a million for helping me get the TCP Telescope working.
Now, I have another problem.
I took your suggestion, and looked at the Paramount telescope, and now everything is working on the local computer, connected to my software called SiTechExe.

Well, I expected that it would work no matter where the software was running.
If I connect to 127.0.0.1, and I have the SiTechExe running on the same machine as KStars and INDI, it works fine.
But if I'm running KStars and INDI on the linux box, and SiTechExe on my windows machine, I can't connect. It gets stopped in the connect() routine in connectiontcp.cpp.

Thanks for any help.
Dan Gray
Sidereal Technology.

Read More...

Thanks Oleg, very helpful stuff.

Jasem, this paramount.cpp and h is exactly what I needed, thanks a lot!
Dan

Read More...

Hi all,
So, I'm new to INDI, and I haven't used C++ for 30 years! Yes, giving away my age.....
My lifetime (seems like anyway) project is SiTechExe.exe, a windows/ascom telescope program that controls our brushed and brushless servo controllers (sidereal technology).

Ok, it's about time, lots of our customers want an INDI driver.
Here's where I am right now:

I've got QTCreator working, and compiling a new telescope called SiTechScope, or something. I based it on the telescope_simulator. It's working with KStars as a simulator, now I just need the driver to communicate with our SiTechExe software, instead of just simulating a telescope.

SiTechExe is a TCP server, and you can send it text, for instance, if you send (in my case)
TO: 192.168.51.51::1952
THIS: "GoTo 12.123 45.456"
Then SiTechExe will move the scope to that RA and Dec. You can also sync, park, track satellites, track comets, and many other things, as well as reading status of the mount.

So, I was looking at baseclient, and it seems to be specific for connecting to an INDI server, not to a hardware device (in this case another piece of software).
So, does this mean I should start from scratch using C++ library socket routines? This seems daunting, especially to keep it from blocking, for instance, I need another process?
Any ideas would be helpful.

The second question, In KStars, I'm able to set the IP address and port number for the telescope. How do I access these from my telescope driver?

I'm sure I'll have 3rd, 4th, and nth questions!

Thanks a million!
Dan Gray

Read More...