Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 15748 articles
Browse latest View live
↧

FTDI chipset, mount disconnects - by: supernov

May 31, 2017, 1:56 pm
$
0
0
This evening I switched from using a PL chipset to a cable with a FTDI chipset and am experiencing the problem that it is being recognized by Linux (looking at dmesg) and connected to TTYUSB0, but shortly after that it disconnects without a clear reason. On Windows it works fine (though it got assigned COM port18 which EQMod couldn't see, so I forced it to use 16). It might be an old problem, but I couldn't find a clear answer to it. Any ideas?

Thanks.
↧
Search

Kstars clock and UTC offsets - by: jevans

May 31, 2017, 4:37 pm
$
0
0
I'm running the latest indi RPI image to control a Celestron CPC800, QSI 583 CCD, Starshoot autoguider and Microtouch focuser.

I'm connecting to KSTARS through EKOS VM 1.6 and note some discrepancies in the Kstars clock, vs. Ekos VM, RPi, WIndows and my telescope.

I think the UTC offsets in KStars are off/backwards. My current location is in the US Pacific time zone. With Daylight Savings time, the UTC Offset is currently -7.
During Standard time it is -8. I have verified the time/time zone settings on my Raspberry Pi, Windows PC and in Ekos VM are correct, however when I define a custom site in KStars with a correct offset of -7, the Kstars time is one hour ahead of the rest of the clocks I am using. If I set the offset to -8, my telescope then thinks it is located in the Mountain time zone.

I'm sure this can't be very good for accuracy. Any idea what may be going on or how I can remedy this? I have attached a screen grab shoing the time difference btween Kstars/Ekos

Thanks
↧
↧

Question about update and error with fliusb - by: maudy

June 1, 2017, 2:53 pm
$
0
0
I have meant to ask this for some time when updating my ubuntu-mate 16.04 RPI3.

When running sudo apt-get update & sudo apt-get dist-upgrade

The below error is obtain.

Is this something to correct or ignore?

Setting up fliusb-dkms (1.3+r3115~201706011729~ubuntu16.04.1) ...
Loading new fliusb-1.3+r3115~201706011729~ubuntu16.04.1 DKMS files...
dpkg: warning: version '*-*' has bad syntax: version number does not start with digit
It is likely that 4.9.28-v7+ belongs to a chroot's host
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Setting up libfli1 (1.8.ubuntu5+r3115~201706011721~ubuntu16.04.1) ...

Thank you
↧

Ekos gives me monochrome FITS when using a DSLR camera - by: avilqu

June 2, 2017, 4:13 am
$
0
0
Hi all,

I see Ekos has the option to take the image in native format or FITS. When I select native format and use my Canon 5D2 with Gphoto INDI driver, I get the nice colorful raw images I expect. However, if I chose the FITS option, I get monochrome .fits files. Is there a reason for this? Does this mean I actually only get the R, G or B in the form of a FITS file?
In other words, is this monochrone FITS containing ALL the information recorded by the CMOS captor, or only one of the colours?

Thanks!
↧

Controlling a Losmandy Model 492 with INDI - by: avilqu

June 2, 2017, 4:15 am
$
0
0
Hi all,

I've been unsuccessfully trying to control a Losmandy mount with INDI. The computer board of the mount says "Model 492". I can't even connect to the mount with the Losmandy Gemini driver. Only driver that seems to connect to it is LX90, but it doesn't seem to be able to move the mount.

Has anyone had better success with this particular mount?

Thanks
↧
↧

Eqmod and image capture - by: tseckler

June 2, 2017, 8:00 am
$
0
0
Last night while trying to capture 1200 sec subs kstars would lock sometimes before the capture was finished and sometimes while downloading. I noticed the spinning gear indicating the capture in progress would spin at an uneven pace. At first it would spin at a fast pace then as the capture progressed it would spin slower and more erratic.Today while testing I noticed that this behavior only happens when eqmod is connected. I have tried different eqmod cables with no change. Attached are the eqmod and kstar logs.
↧

issue with exposure over 1s on DSLR - by: Vox45

June 2, 2017, 8:31 am
$
0
0
I use a DSLR Canon 1000D and the DSLR INDI driver

- I made sure that my camera was set to AV, and [autoexposuremode] in the driver configuration also set to AV
- I can expose up to 1s, if I go beyond that, it fails.
- I changed [autoexposuremode] to "BULB" in the driver setting and when I set the exposure to anything more then one seconds, it always exposes for 30"

Here is the extract from the debug log that shows the issue. The complete log is attached. I made multiple attempt increasing the exposeure time and decreasing to validate that it was the fact that I go beyond 1s that causes the issue.

Although I already set to AV on both the camera and the configuration, I still get message below clearly state that I should set to BULB or AV...

===================================================
DEBUG 41.148998 sec : Starting exposure (exptime: 1 secs, mirror lock: 0)
DEBUG 41.149076 sec : Mutex locked
DEBUG 41.149107 sec : Setting radio/menu widget iso: 5 (1600)
DEBUG 41.154796 sec : Setting new configuration OK.
DEBUG 41.154863 sec : Setting radio/menu widget imageformat: 7 (RAW)
DEBUG 41.161232 sec : Setting new configuration OK.
DEBUG 41.161344 sec : Using camera predefined exposure ranges.
DEBUG 41.161378 sec : Finding optimal exposure setting for 1 seconds in shutterspeed (count=1)...
DEBUG 41.161405 sec : Best match: -2 seconds Index: 0
DEBUG 41.161436 sec : Setting radio/menu widget shutterspeed: 0 (auto)
DEBUG 41.167446 sec : Setting new configuration OK.
DEBUG 41.167591 sec : Using predefined exposure time: -2 seconds
DEBUG 41.167659 sec : Exposure started
INFO 41.167681 sec : Starting 1 sec exposure
DEBUG 42.168077 sec : Reading exposure...
DEBUG 42.448578 sec : Exposure complete
DEBUG 42.448666 sec : gp_file_new_from_fd result: 0
DEBUG 42.448698 sec : Downloading //capt0000.cr2
DEBUG 42.465276 sec : Downloading result: 0
DEBUG 42.465356 sec : Downloaded 0x0 (preview 0x0)
DEBUG 42.465392 sec : Capture target is INTERNAL RAM.
DEBUG 42.465422 sec : Deleting.
DEBUG 42.465449 sec : Retval: 0
DEBUG 42.465481 sec : Setting radio/menu widget iso: 5 (1600)
DEBUG 42.477933 sec : Setting new configuration OK.
DEBUG 42.478017 sec : Setting radio/menu widget imageformat: 7 (RAW)
DEBUG 42.484059 sec : Setting new configuration OK.
DEBUG 42.484111 sec : Setting radio/menu widget shutterspeed: 0 (auto)
DEBUG 42.490504 sec : Setting new configuration OK.
INFO 42.490585 sec : Exposure done, downloading image...
DEBUG 43.039491 sec : read_libraw: raw_width: 3948 top_margin 18 left_margin 42 first_visible_pixel 71106
DEBUG 43.039568 sec : read_libraw: rawdata.sizes.width: 3906 rawdata.sizes.height 2602 memsize 20326824 bayer_pattern RGGB
DEBUG 43.049785 sec : read_libraw: memsize (20326824) naxis (2) w (3906) h (2602) bpp (16) pattern (RGGB)
DEBUG 43.069839 sec : Uploading file. Ext: fits, Size: 20329920, sendImage? Yes, saveImage? No
DEBUG 43.122346 sec : Upload complete
DEBUG 47.685122 sec : Requested CCD Frame is ( 0, 0) (3888 x 2592)
DEBUG 47.685848 sec : Starting exposure (exptime: 1.1 secs, mirror lock: 0)
DEBUG 47.685917 sec : Mutex locked
DEBUG 47.685947 sec : Setting radio/menu widget iso: 5 (1600)
DEBUG 47.698065 sec : Setting new configuration OK.
DEBUG 47.698166 sec : Setting radio/menu widget imageformat: 7 (RAW)
DEBUG 47.704261 sec : Setting new configuration OK.
WARNING 47.704354 sec : Camera auto exposure mode is not set to either BULB or MANUAL modes (AV). Please set mode to BULB for long exposures.
DEBUG 47.704381 sec : Using internal bulb widget:bulb
DEBUG 47.704400 sec : Setting toggle widget bulb: 1
DEBUG 47.713482 sec : Failed to set new configuration value (GP result: -1)
DEBUG 47.713571 sec : Exposure started
DEBUG 47.713593 sec : Time left: 1099
D713611 sec : Starting 1.1 sec exposure
DEBUG 48.714516 sec : Reading exposure...
DEBUG 48.813697 sec : Time left: 0
DEBUG 48.813817 sec : Closing shutter
DEBUG 48.813842 sec : Using widget:bulb
DEBUG 48.813866 sec : Setting toggle widget bulb: 0
DEBUG 48.842417 sec : Setting new configuration OK.
DEBUG 48.842568 sec : Exposure complete
DEBUG 48.857934 sec : Unknown event.
DEBUG 48.867358 sec : Unknown event.
DEBUG 49.875248 sec : Event timed out #1, retrying...
DEBUG 50.884041 sec : Event timed out #2, retrying...
DEBUG 51.893057 sec : Event timed out #3, retrying...
DEBUG 52.901125 sec : Event timed out #4, retrying...
DEBUG 53.927759 sec : Event timed out #5, retrying...
DEBUG 54.944055 sec : Event timed out #6, retrying...
DEBUG 55.947453 sec : Event timed out #7, retrying...
DEBUG 56.948434 sec : Event timed out #8, retrying...
DEBUG 57.949454 sec : Event timed out #9, retrying...
DEBUG 58.950418 sec : Event timed out #10, retrying...
ERROR 58.950619 sec : Exposure failed to save image... Unspecified error
===================================================
↧

A looping camera mode? - by: bj0

June 3, 2017, 9:28 am
$
0
0
PHD2 and byEOS have a looping capture mode so you can see what you're pointed at when you are doing setup/goto stuff. I keep PHD2 running in the background just for this purpose, but it can sometimes cause issues. I noticed there is something similar in the new polar alignment tool, but it would be really nice if there was a place where you could just go and turn this one in Ekos. Does anything like that exist?
↧
Search

EQMOD - Park and Home Position setting? - by: myxlflik

June 3, 2017, 10:02 am
$
0
0
I have an annoying issue (which I am almost certain is a settings problem and not a bug) with regards to the home and park positions on my Sirius Pro mount. Basically, I want the home and park positions to be with the counterweights down and the OTA pointed straight to the north. I connect to my Sirius Pro with the EQMOD adapter and drivers in Ekos. When I first start up, it seems like the mount is showing random coordinates. It could be the last object I slewed to, but I am not 100% certain there. It's probably because I don't currently park the mount before turning it off. My guess is that the mount uses it's last known coordinates as the coordinates it starts up with. Currently, if I park the mount, it ends up 'pretzeling' itself around the OTA. Fortunately it is not crashing the OTA or anything, but it's definitely doing wonky things when I park it.

My question is two fold
1 - How do I set the Home/Park position in the EQMOD options to counterweights down and OTQ pointing north?
2 - If I lose power or have to restart the mount, is there an easy way to tell the mount what it's approximate coordinates are when turning it back on so I don't have to do a bunch of work to get it back on track?

I suspect this is an easy problem to solve and I just haven't looked into the EQMOD options in Ekos enough to figure out what to set yet. Any ideas would be appreciated.
↧
↧

APN image green - by: rmor51

June 3, 2017, 1:01 pm
$
0
0
I capture last day M13 with a Canon 450D and Ekos. The image on the screen, into the FIST Viewer, was green. Curiously the FITS image downloaded is black and white, with very little signal . In fact I can see anything and I have to improve the signal with Photoshop in order M13 appears.

So why green ?
And why such difference between the fits viewer and the fits image ?

Thank you for your support.
↧

KStars crashes during session - by: Kaczorek

June 3, 2017, 1:53 pm
$
0
0
I'm constantly getting KStars crash after a few images are captured with Ekos. I cannot debug it due to the following error:


I have reports from my mates of the same issue.
phonon4qt5-backend-gstreamer has been replaced with phonon4qt5-backend-vlc was installed. So I assume that it's not notifications issue.
There's nothing meaningful in the KStars logs.

When running from terminal KStars segfaults with the following:


Any ideas?

UPDATE: I have just found out that setting delay in Ekos capture module (e.g. 10s) between images keeps the session stable. Are we facing a race condition somewhere in the code?
↧

Kstars aborts after selecting 'View in what's interesting' - by: phomer60

June 3, 2017, 10:12 pm
$
0
0
Running on a Raspberry Pi 3 using Ubuntu Mate.
↧

Issues with Bluetooth Joystick - by: petarm

June 3, 2017, 10:52 pm
$
0
0
Hi All,

I bought a bluetooth joystick to use with my heq5/eqmod setup under INDI. I want to be able to make minor adjustments to my mount when doing an alignment and to centre the target before an imaging session without touching my laptop.

The controller is a generic BT single stick controller. See ebay site



INDI sees it as VR BOX version 131328 joystick with 2 axes and 15 buttons. It connects ok (see images below), gives me East/West slewing. I have changed the 2 buttons that work to give me faster and slower slew rates

But it wont slew North/South. Also it gives me access to only 2 of the 15 available bottons.

Could this be an issues with the joystick or is it a compatibility issue?

Any suggestions are welcome.

regards
↧
↧

Fits viewer issue - by: Christian

June 4, 2017, 3:39 am
$
0
0
hi Jansem, i just tested le last github repository and i found an issue with the fits viewer. When i open an fits from the harddrive and than i click on the show equatorial gridlines button the program crash.

I've only selected auto wcs on fits menu (all others are unchecked). This issue appear only when i connect indi driver (simulator) else it work fine.



Have a nice day.
↧

Stellar magnitude vs DSO magnitude - by: oopfan

June 4, 2017, 12:22 pm
$
0
0
I recently imaged M57. A catalog that I use says that it is magnitude 9.0 and a size of 2.5 arcmin. I took a single 30-second exposure and compared it to a star chart. The nebula is visible but it is rather dim. Not too far away is a 9th magnitude star that is burnt in and bright. In my primitive mind I rationalize this by saying that if I were to add up the number of photons in the larger area of the nebula and compress it into the smaller area of the star then I might say they are equivalent magnitude.

Somewhere in my mind a formula exists that relates star magnitude to DSO magnitude given the size of the DSO. I applied what I learned from undergraduate courses in Astronomy and Physics from 40 years ago, and came up with an equation that produces unsatisfactory results.

You see, this is the question I would like answered: If a single, unstacked, 30-second image shows stars down to the 13th magnitude then what is the magnitude of the faintest DSO that I can see in that image given its size in arc minutes?

Has anyone heard of such a calculator, or is there a rule of thumb?

Thanks so much.
↧
Search

TCP client/server communication Indi driver and another program - by: loiclej

June 6, 2017, 9:26 am
$
0
0
Hello

I use SimpleScope tutorial two Indi Driver.

RA and DEC will be calculated by another program. I should want the Indi driver to be the TCP client and the another program to be the TCP server.

I should want to use zeromq TCP client/server. For linking, it's necessary to write -lzmq in the command line.

Is it possible to create the Indi driver using zmq dynamic library ? How to add -lzmq option ?

Thank you
Loic
↧

Custom Driver CMakeLists.txt Question - by: ColoradoSolar

June 6, 2017, 1:44 pm
$
0
0
I am very new to CMake and I am at a bit of a loss.

I need the indiclient lib in my project but if I try find_package(indiclient REQUIRED) CMake cannot find it but I just include indiclient in my target_link_libraries line it works fine but I'm thinking that is not the correct way to do that.

Can anyone shed any light in the subject for me?

Thanks,
Eric
↧
↧

Having trouble with eqmod pointer not matching view of the sky - by: xsnrg

June 8, 2017, 6:32 am
$
0
0
note: this is a fresh look at an issue previously mentioned in another thread, but moved here to clean things up.

I have a Sirius EQ-G, and the scope pointer in kstars does not match the location in the sky. That is, when I slew to an object, it is usually off by an amount that seems to be constant, and I am then correcting to where I want with plate solving. I have not been able to find a way to sync the red reticle to the actual sky view, and have just been using it with plate solving and ignoring it. It would be nice to have it in sync. Said a different way, once I am done with centering/solving, the white rectangle that shows my sensor view of the sky is accurate, but the red eqmod reticle will be off.

I tried clearing the alignment data from the AlignData.xml, as well as clearing from the mount model in Ekos and the align info in the INDI control panel and starting fresh. This seems to have moved how far away the eqmod pointer is in kstars, but did not resolve the issue.

video and logs attached
↧

EQ6 with MCU-Upgrade problems with Indi_lx200basic driver - by: linuxer

June 9, 2017, 1:51 am
$
0
0
hi Guys

I bought an EQ6 about 15 years ago and upgraded with Rajiva's MCU-Upgrade Kit.
If I run the EQ6 with Skychart the internal driver and the control of the mount works without problems.
If I use the Indiserver indi_lx200basic with Kstars then i've got the connection to the driver but more does not happen.

I can still remember a libindi version that worked. But that has been many years ago.
I have run on the server the latest PPA from Jasem and connect with Kstars from the client.

In the "sync" of an object, I see the cross for a second, but immediately disappears. If I want to "slew" on a object, nothing happens.

This is the Kstars Indi-Control output

2017-06-09T08:42:21: Object below the minimum elevation limit.
2017-06-09T08:42:21: Error Slewing to JNow RA 2:44:12 - DEC 3:18:21
2017-06-09T08:42:12: Synchronization successful.
2017-06-09T08:41:56: LX200 Basic is online.


What should I do to run the EQ6 with the Indi_lx200basic driver?
I would like to use ekos, but as long as the assembly does not work it is useless.

I have already read that many EQ6 users with MCU upgrade, have problems with this driver.

Is there a solution for this problem?
If there no driver specifically for the eq6 with mcu-upgrade kit?

If I can help to solve the problem, so let me know how i can help.

Sorry for my bad english but google ist my friend ;)

Best regards
Thomas
↧

INDI for Java still alive? - by: Andreas_Roerig

June 9, 2017, 7:57 am
$
0
0
Hi,

my name is Andreas and I am new to this forum.

A while ago I have built my own mount controller based on a RaspberryPi and an Arduino Due.
I have already written an ASCOM driver for it and it works fine. Now I would like to write an INDI driver for my controller.
As I am an experienced Java developer I would like to do that in Java. So I looked at the INDI for Java website and the corresponding Sourceforge repository. It looks as if there has not been much activity recently. Has this project come to halt? Does it still make sense to use it or would it be better to use the standard C/C++ approach?

I have downloaded the distribution 1.5 and tried to start the server (via the i4j-server-interactive script) but when I tried to connect to it from CdC I get the following message:

Debugger failed to attach: handshake failed - received ><getProperties< - expected >JDWP-Handshake<

Any input would be appreciated.

Best regards
Andreas
↧
Viewing all 15748 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>