I see lots of great examples in the developers section of the website, but it has been quite a struggle for me to actually compile any of the examples on my own (the client specifically). What all do I need to get a simple example client compiled and running on Debian/Ubuntu? Is there a simple g++ command to compile these? I apologize if I sound ignorant, but I have been failing to compile the client example for the last couple of days. Thanks for all your help!
↧
Compiling Examples - by: sbm
↧
[SOLVED] SBIG Guide Chip Exposure Hangs - by: mrnetdes
I just installed Ubuntu 15.04, indi-full and kstars-bleeding to try out KStars/Ekos with INDI in the hopes of being able to setup a remote imaging solution using a Raspberry Pi. I have an SBIG ST2000XCM and I was able to use Ekos to capture an image from the main CCD chip but when I try to capture an image from the guiding CCD the download never completes and sometimes the indi_sbig_ccd driver crashes with a SIGSEGV in INDI::CCD::getMinMax().
I turned on logging in the INDI server and I can see that the driver is reporting bad values for the width and height of the guide chip. The guide chip in my camera is 657 pixels wide and 495 pixels high with each pixel being 7.4 x 7.4 u. In one case the driver, via the debug messages and via the INDI control panel, reported the guide chip was 46962 by 20096.
This sounds a little like bug report #62 (Device SBIG CCD guider). In that report the user was able to override the initial invalid values in the INDI Control Panel. I tried that but as soon as I started the guide exposure the values reverted back to the original invalid values.
I have attached a debug log from my last attempt. The log does say that the download completed, but I got the "KStars detected indi_sbig_ccd crash" message the the Capture radio button stayed yellow on the Guide tab.
The INDI library shows v1.1.0 and code $Rev$ Protocol 1.7
Has anyone else seen this or any ideas how I might be able to circumvent this?
Thanks
Mark
↧
↧
Canon EOS 1100D - Unable to connect - by: UlfG
I am testing the Distroastro ver 3.0.2 to see if it would work with my hardware and cameras. I have a Canon EOS 1100D camera, which I am not able to connect to
in Kstars/Ekos. In the Device manager in KStars, there is a status icon and log indicating that the camera is detected, see enclosed screen dump.
But when the Indi Control panel is opened, and I press Connect, I get the message "Can not open camera. Power Ok?"
Why is this and what can I do? The Canon camera is listed in dmesg and lsusb output as well.
Regards
Ulf
in Kstars/Ekos. In the Device manager in KStars, there is a status icon and log indicating that the camera is detected, see enclosed screen dump.
But when the Indi Control panel is opened, and I press Connect, I get the message "Can not open camera. Power Ok?"
Why is this and what can I do? The Canon camera is listed in dmesg and lsusb output as well.
Regards
Ulf
↧
Getting SBIG Drivers Working on Raspberry Pi - by: mrnetdes
I had trouble getting the SBIG drivers working on a Raspberry Pi model 1 B+ with Raspbian installed so I thought I would share my experience here in case someone else runs into the same issue I did. I installed the basic INDI library and the SBIG drivers (indi-sbig and libsbigudrv) using the libindi_1.1.0_rpi.tar package from this site. When I started the indiserver with the indi_sbig_ccd driver the server went into a loop with the following messages.
I had to halt the process with Ctl-c. If I executed the indi_sbig_ccd module from the command line I got a "Illegal instruction" message. I used gdb to run the indi_sbig_ccd driver and found that the problem was in the libsbigudrv library.
I ended up installing the libsbigudrv source package and building it on the Raspberry Pi. That resolved my issue and I was able to connect to the Raspberry Pi using KStars/Ekos on a laptop and successfully capture images from my SBIG camera attached to the Raspberry Pi.
If you are interested, here is what I did to download and build the libsbigudrv package. First, I had to add the mutlaqja repository manually since the apt-add-repository tool is not installed by default on the Raspbian distribution.
Create the followiing file /etc/apt/sources.list.d/mutlaqja.list
I used the "trusty" Ubuntu release since it was the oldest supported release on the repository site. The Raspbian distribution is based on Debian wheezy which is roughly equivalent to Ubuntu saucy (13.10).
Then you have to get the public key using the following command
Now to download and build the package.
The library is not really compiled from source, rather the cmake determines which of the supplied library files should be used for the current machine architecture. In my case, with a Raspberry Pi B+, it used the libsbigudrv_arm_v6.bin file which gets copied to libsbigudrv.so.2.1.0 file and linked as libsgibudrv.so.
I hope this helps.
I had to halt the process with Ctl-c. If I executed the indi_sbig_ccd module from the command line I got a "Illegal instruction" message. I used gdb to run the indi_sbig_ccd driver and found that the problem was in the libsbigudrv library.
I ended up installing the libsbigudrv source package and building it on the Raspberry Pi. That resolved my issue and I was able to connect to the Raspberry Pi using KStars/Ekos on a laptop and successfully capture images from my SBIG camera attached to the Raspberry Pi.
If you are interested, here is what I did to download and build the libsbigudrv package. First, I had to add the mutlaqja repository manually since the apt-add-repository tool is not installed by default on the Raspbian distribution.
Create the followiing file /etc/apt/sources.list.d/mutlaqja.list
I used the "trusty" Ubuntu release since it was the oldest supported release on the repository site. The Raspbian distribution is based on Debian wheezy which is roughly equivalent to Ubuntu saucy (13.10).
Then you have to get the public key using the following command
Now to download and build the package.
The library is not really compiled from source, rather the cmake determines which of the supplied library files should be used for the current machine architecture. In my case, with a Raspberry Pi B+, it used the libsbigudrv_arm_v6.bin file which gets copied to libsbigudrv.so.2.1.0 file and linked as libsgibudrv.so.
I hope this helps.
↧
Meade DSI, GPUSB &"dumb" mount problems - by: mdurkin
Hello,
I'm running into a problem which hopefully is just something simple that I have overlooked.
I am trying to repurpose and old laptop to use as a dedicated autoguider. I installed DistoAstro 3.0.1 which is based on Ubuntu 14.04 Trusty LTS. The hardware that I have: Meader DSI I, GPUSB, and a Celestron SCT with a "dumb" mount.
I start up Kstars (v 2.2.0), and bring up the Ekos menu. I start up INDI and connect the DSI and GPUSB. Then I select the Guide tab in order to calibrate. I select "Capture" and I get an image from the DSI. I select a guide star and then as soon as I press the buton to start calibration, I get an error message "CCD & Telescope info are missing. Please set the values in INDI control panel." I selected Telescope Simulator and CCD simulator, but even with that, I still get the same error.
My main imaging camera is a Canon DSLR. I have a programmable shutter control that I use for y DSLR, so I do not have it connecting to INDI. And since my mount is just a "dumb" mount with a port for a simple hand controller, I didn't see anything in the list of telescope options that looked appropriate, only the GPUSB option under Auxiliary.
Please let me know if any additional information is needed of if I have missed something simple in order to get Ekos to do autoguiding without a primary CCD camera or a computerized mount.
Thanks,
-Mike Durkin
I'm running into a problem which hopefully is just something simple that I have overlooked.
I am trying to repurpose and old laptop to use as a dedicated autoguider. I installed DistoAstro 3.0.1 which is based on Ubuntu 14.04 Trusty LTS. The hardware that I have: Meader DSI I, GPUSB, and a Celestron SCT with a "dumb" mount.
I start up Kstars (v 2.2.0), and bring up the Ekos menu. I start up INDI and connect the DSI and GPUSB. Then I select the Guide tab in order to calibrate. I select "Capture" and I get an image from the DSI. I select a guide star and then as soon as I press the buton to start calibration, I get an error message "CCD & Telescope info are missing. Please set the values in INDI control panel." I selected Telescope Simulator and CCD simulator, but even with that, I still get the same error.
My main imaging camera is a Canon DSLR. I have a programmable shutter control that I use for y DSLR, so I do not have it connecting to INDI. And since my mount is just a "dumb" mount with a port for a simple hand controller, I didn't see anything in the list of telescope options that looked appropriate, only the GPUSB option under Auxiliary.
Please let me know if any additional information is needed of if I have missed something simple in order to get Ekos to do autoguiding without a primary CCD camera or a computerized mount.
Thanks,
-Mike Durkin
↧
↧
first steps of a newbie - by: patdut
Hello all, here is Patrick from Gaillac France
I am a newcomer on this forum. I am very interested in developing some light applications around INDI. Those applications will be scripted in python. The goal is to have a toolbox on a odroid device.
So, as all beginners I tried directly to test the python interface with the example which is in "DBUS Scripting with KStars & Python".
After starting Kstars I launched the script and get the following message
ERROR:dbus.proxies:Introspect error on :1.269:/KStars/INDI: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownObject: No such object path '/KStars/INDI'
I don't understand what I have done wrong.
A subsidiary question: is it necessary to start Kstars, is it possible to start only the indiserver ?
Does somebody can tell me ?
Thanks
I am a newcomer on this forum. I am very interested in developing some light applications around INDI. Those applications will be scripted in python. The goal is to have a toolbox on a odroid device.
So, as all beginners I tried directly to test the python interface with the example which is in "DBUS Scripting with KStars & Python".
After starting Kstars I launched the script and get the following message
ERROR:dbus.proxies:Introspect error on :1.269:/KStars/INDI: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownObject: No such object path '/KStars/INDI'
I don't understand what I have done wrong.
A subsidiary question: is it necessary to start Kstars, is it possible to start only the indiserver ?
Does somebody can tell me ?
Thanks
↧
which histogram can I trust? - by: pauledd
Hi there
Before I start to capture a series of images I capture a preview (format set to fits) and look at the histogram. The maximum appears to be in the first fourth. So theoretical it should be possible to exposure a little bit more.
![]()
But when I take an image in native mode (cr2) and the same settings (iso,exposure) and I look at the histogram of the cr2 or the dcraw converted tiff the image seems to be nearly overexposed:
native cr2:
![]()
draw -W -6 -T:
![]()
so which histogram can I trust to determine a proper exposure/iso setting?
Before I start to capture a series of images I capture a preview (format set to fits) and look at the histogram. The maximum appears to be in the first fourth. So theoretical it should be possible to exposure a little bit more.
But when I take an image in native mode (cr2) and the same settings (iso,exposure) and I look at the histogram of the cr2 or the dcraw converted tiff the image seems to be nearly overexposed:
native cr2:
draw -W -6 -T:
so which histogram can I trust to determine a proper exposure/iso setting?
↧
Kstars crash at start up - by: gaetan
Hello,
Since a few days, Kstars crash when I start it.
When it began to do that, I search on the forum and found a file to remove to correct that. All work fine, but this morning, I have made my updates by the PPA, and now, when I start Kstars, it crash again.
I have Kubuntu 15.04 on my PC
The last update of Kstars-bleeding
and when I start it, after the splash-screen, I have a little text box where I can see 'below horizon' but nothing in ??? the only way is to clic to close the dialog box ... and I have a report to kill the app ???
Someone have the same trouble ?
![capture1.png]( "capture1.png")
![capture2.png]( "capture2.png")
Thank's for your answer.
Gaetan
Since a few days, Kstars crash when I start it.
When it began to do that, I search on the forum and found a file to remove to correct that. All work fine, but this morning, I have made my updates by the PPA, and now, when I start Kstars, it crash again.
I have Kubuntu 15.04 on my PC
The last update of Kstars-bleeding
and when I start it, after the splash-screen, I have a little text box where I can see 'below horizon' but nothing in ??? the only way is to clic to close the dialog box ... and I have a report to kill the app ???
Someone have the same trouble ?
Thank's for your answer.
Gaetan
↧
Periodic error correction - by: sarkkipas
Hi,
Would like to see PEC in Ekos and indi. Similar like in eqmod on ascom.
Is it possible to make a tool to record periodic error (perecorder like), tool to edit/filter pec curve (like pecprep) and a way to implement it to use with any mount supported in indi? Or is there existing tools for this allready?
Would like to see PEC in Ekos and indi. Similar like in eqmod on ascom.
Is it possible to make a tool to record periodic error (perecorder like), tool to edit/filter pec curve (like pecprep) and a way to implement it to use with any mount supported in indi? Or is there existing tools for this allready?
↧
↧
How to debug "Camera not found" errors for SBIG - by: seanhoughton
I'm trying to get my ST-8300M camera working with indiserver and the sbig driver. I'm using Ubuntu 15.04 running in a VirtualBox VM provisioned with Vagrant and hosted on OSX Yosemite.
The device shows up in lsusb:
When I try to connect to it on port "sbigusb0" I get the following message:
I've set every debug level to the maximum everywhere I can find it and I can't get any more information. I've also tried running indiserver in its own shell in super verbose mode (vvv) and there's no information other than the "Camera not Found" message.
Is there any way to debug this other than building the driver myself and stepping through the code with GDB? I'd like to help myself, but I seem to be the only person to have this problem as there are no other forum posts about it.
The device shows up in lsusb:
When I try to connect to it on port "sbigusb0" I get the following message:
I've set every debug level to the maximum everywhere I can find it and I can't get any more information. I've also tried running indiserver in its own shell in super verbose mode (vvv) and there's no information other than the "Camera not Found" message.
Is there any way to debug this other than building the driver myself and stepping through the code with GDB? I'd like to help myself, but I seem to be the only person to have this problem as there are no other forum posts about it.
↧
[SOLVED] Virtual Address Space AsiCam - by: Horand
Sry, I was on vacation last week,
Yes it is working as expected (didn't even notice the libraries![:P]( ":P")
) and you can mark it as resolved.
cs Markus
Yes it is working as expected (didn't even notice the libraries
) and you can mark it as resolved.cs Markus
↧
INDI Library for Raspberry PI - by: broadcastyourseb
Hi,
I tried to install indi library and the 3rd party but it seems that indi library are missing from libindi_1.1.0_rpi.tar.gz. On the website, we can read that the compress file contains INDI Library 1.1.0 including 3rd party drivers.
Extract folder contains this files :
atikccd-0.25-armhf.deb
fliusb-dkms_1.3_armhf.deb
fliusb-source_1.3_armhf.deb
indi-aagcloudwatcher_1.2_armhf.deb
indi-aagcloudwatcher-dbg_1.2_armhf.deb
indi-apogee_1.5_armhf.deb
indi-apogee-dbg_1.5_armhf.deb
indi-dsi_0.1_armhf.deb
indi-dsi-dbg_0.1_armhf.deb
indi-eqmod_0.2_armhf.deb
indi-eqmod-dbg_0.2_armhf.deb
indi-ffmv_0.1_armhf.deb
indi-ffmv-dbg_0.1_armhf.deb
indi-fishcamp_1.0_armhf.deb
indi-fishcamp-dbg_1.0_armhf.deb
indi-fli_1.0.0ubuntu3_armhf.deb
indi-fli-dbg_1.0.0ubuntu3_armhf.deb
indi-gphoto_1.3_armhf.deb
indi-gphoto-dbg_1.3_armhf.deb
indi-maxdomeii_1.0_armhf.deb
indi-qhy_1.4_armhf.deb
indi-qhy-dbg_1.4_armhf.deb
indi-qsi_0.4.1_armhf.deb
indi-qsi-dbg_0.4.1_armhf.deb
indi-sbig_1.5_armhf.deb
indi-sbig-dbg_1.5_armhf.deb
libapogee3_3.0.3179_armhf.deb
libapogee3-dev_3.0.3179_armhf.deb
libfishcamp_1.0_armhf.deb
libfishcamp-dev_1.0_armhf.deb
libfli1_1.8.ubuntu5_armhf.deb
libfli-dev_1.8.ubuntu5_armhf.deb
libqhy_0.1.5_armhf.deb
libqsi7_7.2.0_armhf.deb
libqsi-dev_7.2.0_armhf.deb
libsbigudrv2_2.1.0_armhf.deb
shoestring-0.8-armhf.deb
The website indicates that the file is 10.55MB but on my disk, it is 6.0MB.
In a previous setup with libindi_1.0.0_rpi.tar.gz file, everything was include in.
The question is, what is wrong ?
Sébastien.
I tried to install indi library and the 3rd party but it seems that indi library are missing from libindi_1.1.0_rpi.tar.gz. On the website, we can read that the compress file contains INDI Library 1.1.0 including 3rd party drivers.
Extract folder contains this files :
atikccd-0.25-armhf.deb
fliusb-dkms_1.3_armhf.deb
fliusb-source_1.3_armhf.deb
indi-aagcloudwatcher_1.2_armhf.deb
indi-aagcloudwatcher-dbg_1.2_armhf.deb
indi-apogee_1.5_armhf.deb
indi-apogee-dbg_1.5_armhf.deb
indi-dsi_0.1_armhf.deb
indi-dsi-dbg_0.1_armhf.deb
indi-eqmod_0.2_armhf.deb
indi-eqmod-dbg_0.2_armhf.deb
indi-ffmv_0.1_armhf.deb
indi-ffmv-dbg_0.1_armhf.deb
indi-fishcamp_1.0_armhf.deb
indi-fishcamp-dbg_1.0_armhf.deb
indi-fli_1.0.0ubuntu3_armhf.deb
indi-fli-dbg_1.0.0ubuntu3_armhf.deb
indi-gphoto_1.3_armhf.deb
indi-gphoto-dbg_1.3_armhf.deb
indi-maxdomeii_1.0_armhf.deb
indi-qhy_1.4_armhf.deb
indi-qhy-dbg_1.4_armhf.deb
indi-qsi_0.4.1_armhf.deb
indi-qsi-dbg_0.4.1_armhf.deb
indi-sbig_1.5_armhf.deb
indi-sbig-dbg_1.5_armhf.deb
libapogee3_3.0.3179_armhf.deb
libapogee3-dev_3.0.3179_armhf.deb
libfishcamp_1.0_armhf.deb
libfishcamp-dev_1.0_armhf.deb
libfli1_1.8.ubuntu5_armhf.deb
libfli-dev_1.8.ubuntu5_armhf.deb
libqhy_0.1.5_armhf.deb
libqsi7_7.2.0_armhf.deb
libqsi-dev_7.2.0_armhf.deb
libsbigudrv2_2.1.0_armhf.deb
shoestring-0.8-armhf.deb
The website indicates that the file is 10.55MB but on my disk, it is 6.0MB.
In a previous setup with libindi_1.0.0_rpi.tar.gz file, everything was include in.
The question is, what is wrong ?
Sébastien.
↧
indi_gphoto_ccd & canon RAW format - by: pschg
Hello Folks,
I have trouble getting images in Canon RAW format using KSTARS on a virtual machine and Indiserver running on a Ubuntu Mate Raspi. Telescope control and guiding cam (qhy5-II) work ok so far, getting images as jpeg using gphoto works, too.
Trying to get RAWs from an EOS 6D gives an error message as follows:
2015-07-18T09:26:44: Driver indi_gphoto_ccd: read_ppm: Expected (5472 x 3648) but image is actually (5496 x 3670)
Trying with an EOS 1100D leads to the same message (different image size values, of course).
Using gphoto2 directly like this
"gphoto2 --set-config eosremoterelease=Immediate --wait-event=1s --set-config eosremoterelease=4 --wait-event-and-download=2s --filename=shot.%C --force-overwrite"
works perfect for both cameras when I set them to BULB-Mode.
As said, jpeg download works fine, but when I change the image format to RAW, I get the error mentioned. Any idea whats going wrong?
Thanks in advance,
Peter
I have trouble getting images in Canon RAW format using KSTARS on a virtual machine and Indiserver running on a Ubuntu Mate Raspi. Telescope control and guiding cam (qhy5-II) work ok so far, getting images as jpeg using gphoto works, too.
Trying to get RAWs from an EOS 6D gives an error message as follows:
2015-07-18T09:26:44: Driver indi_gphoto_ccd: read_ppm: Expected (5472 x 3648) but image is actually (5496 x 3670)
Trying with an EOS 1100D leads to the same message (different image size values, of course).
Using gphoto2 directly like this
"gphoto2 --set-config eosremoterelease=Immediate --wait-event=1s --set-config eosremoterelease=4 --wait-event-and-download=2s --filename=shot.%C --force-overwrite"
works perfect for both cameras when I set them to BULB-Mode.
As said, jpeg download works fine, but when I change the image format to RAW, I get the error mentioned. Any idea whats going wrong?
Thanks in advance,
Peter
↧
↧
indi_gphoto_ccd & canon RAW format - by: pschg
Hello Folks,
I have trouble getting images in Canon RAW format using KSTARS on a virtual machine and Indiserver running on a Ubuntu Mate Raspi. Telescope control and guiding cam (qhy5-II) work ok so far, getting images as jpeg using gphoto works, too.
Trying to get RAWs from an EOS 6D gives an error message as follows:
2015-07-18T09:26:44: Driver indi_gphoto_ccd: read_ppm: Expected (5472 x 3648) but image is actually (5496 x 3670)
Trying with an EOS 1100D leads to the same message (different image size values, of course).
Using gphoto2 directly like this
"gphoto2 --set-config eosremoterelease=Immediate --wait-event=1s --set-config eosremoterelease=4 --wait-event-and-download=2s --filename=shot.%C --force-overwrite"
works perfect for both cameras when I set them to BULB-Mode.
As said, jpeg download works fine, but when I change the image format to RAW, I get the error mentioned. Any idea whats going wrong?
Thanks in advance,
Peter
I have trouble getting images in Canon RAW format using KSTARS on a virtual machine and Indiserver running on a Ubuntu Mate Raspi. Telescope control and guiding cam (qhy5-II) work ok so far, getting images as jpeg using gphoto works, too.
Trying to get RAWs from an EOS 6D gives an error message as follows:
2015-07-18T09:26:44: Driver indi_gphoto_ccd: read_ppm: Expected (5472 x 3648) but image is actually (5496 x 3670)
Trying with an EOS 1100D leads to the same message (different image size values, of course).
Using gphoto2 directly like this
"gphoto2 --set-config eosremoterelease=Immediate --wait-event=1s --set-config eosremoterelease=4 --wait-event-and-download=2s --filename=shot.%C --force-overwrite"
works perfect for both cameras when I set them to BULB-Mode.
As said, jpeg download works fine, but when I change the image format to RAW, I get the error mentioned. Any idea whats going wrong?
Thanks in advance,
Peter
↧
INDI DSLRs FAQ - by: knro
Would appreciate help if the community can develop a FAQ for DSLRs on INDI so I can put in the main website as well as in the devices page. It seems a lot of people are running into the same issues. So the most obvious questions are:
1. I cannot connect my Cannon/Nikon/etc, what to do?
2. I cannot capture an image in Raspberry PI? <---- this issue has to do with broken dcraw under Raspberry PI
3. How to capture a video preview? <---- INDI Main Control Panel, for Canon only.
4. How to store images on the remote machine (PC/rpi/..etc)? <---- Set "Upload Mode" in Options to "Both" to store on machine and in Ekos, Client only to store at Ekos side, and "Local" to store only at machine side.
5. ?
1. I cannot connect my Cannon/Nikon/etc, what to do?
2. I cannot capture an image in Raspberry PI? <---- this issue has to do with broken dcraw under Raspberry PI
3. How to capture a video preview? <---- INDI Main Control Panel, for Canon only.
4. How to store images on the remote machine (PC/rpi/..etc)? <---- Set "Upload Mode" in Options to "Both" to store on machine and in Ekos, Client only to store at Ekos side, and "Local" to store only at machine side.
5. ?
↧
Electronically Assisted Astronomy with LN300 cam - by: patdut
Hello,
I have just get a LN300 camera to be able to show DS objects to people around me and use it also as guider cam. I use a easy capture dongle to communicate with the notebook.
I have tested the camera with VLC and all works fine.
I have configured EKOS to be able to use a V4L2 camera. The cam is recognized on video 1. Sizes are correct. And all I get when I push on streaming on button is black window.
Did I missed something ?
Thanks for answering
I have just get a LN300 camera to be able to show DS objects to people around me and use it also as guider cam. I use a easy capture dongle to communicate with the notebook.
I have tested the camera with VLC and all works fine.
I have configured EKOS to be able to use a V4L2 camera. The cam is recognized on video 1. Sizes are correct. And all I get when I push on streaming on button is black window.
Did I missed something ?
Thanks for answering
↧
1000D and Serial Cable - by: dragonlost
Hello.
I am new to INDI / EKOS / kstars![:cheer:]( ":cheer:")
I own a Canon EOS 1000D. I am currently on Kubuntu 14.04.
The Canon EOS 1000D does not has a chip that can handle the USB Mirror lock-up.
I tried on windows before and I managed to use the Mirror lock-up like this:
I plug the USB camera
I also plug the serial cable.
I light EOS utility.
I light a software to capture as "FOCUS" or "GUIDMASTER" via the serial cable.
This way the software automatically downloads the catch on the computer and I can use the Mirror lock-up by turning on the DSLR.
Linux in KStars I can not find how to turn the Mirror lock-up and take screenshots with the serial cable.
In addition when I try to then start the fashion "liveview" I have a black screen and impossible to disable the screen without breaking the DSLR.
sorry for my english I'm a little rusty.
Thanks for your help
I am new to INDI / EKOS / kstars
I own a Canon EOS 1000D. I am currently on Kubuntu 14.04.
The Canon EOS 1000D does not has a chip that can handle the USB Mirror lock-up.
I tried on windows before and I managed to use the Mirror lock-up like this:
I plug the USB camera
I also plug the serial cable.
I light EOS utility.
I light a software to capture as "FOCUS" or "GUIDMASTER" via the serial cable.
This way the software automatically downloads the catch on the computer and I can use the Mirror lock-up by turning on the DSLR.
Linux in KStars I can not find how to turn the Mirror lock-up and take screenshots with the serial cable.
In addition when I try to then start the fashion "liveview" I have a black screen and impossible to disable the screen without breaking the DSLR.
sorry for my english I'm a little rusty.
Thanks for your help
↧
↧
Parking eqmod - by: vtanguay
Hi,
I'm hoping someone can help me with the following. I thought that if I parked eqmod, it would remember it's position next time I fire everything off. This does not seem to be the case.
Couple of notes about my setup:
Boot up the raspberry pi and other devices. Start indi server. Launch kstars and ekos. Start indi and connect devices. The mount had been parked so it is still parked. But kstars thinks it is pointing to ncp (I've defined my park position to be all horizontal to fit in the observatory). I have to manually set the scope near ncp and then I can do my things. When I park, it does park it in the correct position.
I thought if I parked it, it would not only remember that it is parked but also where it is parked.
Any help would be appreciated. Thanks
Vince
I'm hoping someone can help me with the following. I thought that if I parked eqmod, it would remember it's position next time I fire everything off. This does not seem to be the case.
Couple of notes about my setup:
Boot up the raspberry pi and other devices. Start indi server. Launch kstars and ekos. Start indi and connect devices. The mount had been parked so it is still parked. But kstars thinks it is pointing to ncp (I've defined my park position to be all horizontal to fit in the observatory). I have to manually set the scope near ncp and then I can do my things. When I park, it does park it in the correct position.
I thought if I parked it, it would not only remember that it is parked but also where it is parked.
Any help would be appreciated. Thanks
Vince
↧
gphoto driver error - by: max
the latest gphoto driver from PPA is not able to capture any image from the camera and just said :Please select a format before capturing an image.
No matter how you change setting in INDI control panel, always got the error message
No matter how you change setting in INDI control panel, always got the error message
↧
Qhy5ii - by: vtanguay
Hi all,
I've seen a lot of discussion on qhy CCDs here but was wondering if anyone has successfully gotten the qhy5-ii to work with indi on a raspberry pi? I could sure use some help.
Thanks
I've seen a lot of discussion on qhy CCDs here but was wondering if anyone has successfully gotten the qhy5-ii to work with indi on a raspberry pi? I could sure use some help.
Thanks
↧