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

INDI Driver for IPX800 server - by: Spiritchaser

October 15, 2019, 4:04 am
$
0
0
Hi all,
i'm trying to write indi drivers for a domotic server called "IPX800"...
I don't understand how to get IP adress and port from Connection Tab...(from a class derived from Dome)
Also how can I send special http request....which procedure should I use ?
I don't found example...
My C++ is a bit "rusty"...

Thanks for your help.

Regards.
↧
Search

Horizontal lines in captured image atik CCD from indi 3rd party - by: sywong2000

October 15, 2019, 5:49 am
$
0
0
I've compiled indi 3rd party from the source code and found that the captured image from my Atik 490ex contains 3 horizontal lines. See screen. This didn't happen in Artemis software nor the ppa distribution.
T
2019-10-1520_44_24-192.168.1.19raspberrypi-VNCViewer.png
he OS is rapsbian buster. I tried it on both rpi3 and rpi4, same.
Any clues?

2019-10-1520_25_20-Window.png

2019-10-1520_44_24-192.168.1.19raspberrypi-VNCViewer.png
↧
↧

Live stacking methods? - by: knro

October 15, 2019, 10:51 am
$
0
0

han.k wrote: The ASTAP commandline is specified here:

www.hnsky.org/astap.htm#astap_command_line

Han


Thank you Han! I just have to say again I'm in love with both HNSKY & ASTAP! The functionality in ASTAP puts KStars FITSViewer to shame. I have a couple of questions if you don't mind. I love the stacking feature. Do you think your star alignment routine can be used to perform *live* stacking?
↧

Standard capture and transfer format properties? - by: knro

October 16, 2019, 3:22 am
$
0
0
Currently INDI camera drivers transfer their images in FITS format. The only exception is the DSLR driver which can also send images in their native captured format.

I was thinking of expanding this to a standard property so other driver can make use of it. For this, I believe we need two standard properties.

1. CCD_CAPTURE_FORMAT
2. CCD_TRANSFER_FORMAT

For the CCD_CAPTURE_FORMAT, it selects what file format the image should be captured in natively from the device. For DSLR cameras, this can be JPG/CR2/...etc (whatever format natively supported by the camera). For CCD/CMos cameras, this can include RAW-8/RAW-16/RGB/etc..

Now the CCD_TRANSFER_FORMAT simply designates the format which INDI clients receive the captured blob as. These can be:

1. RAW (as is, native)
2. FITS (default)
3. XISF (future implementation perhaps)
4. ..etc

This is already realized in the DSLR driver. That is, you can captured a JPEG image and transfer it as FITS or as RAW, or capture RAW CR2 and transfer it as FITS..etc. So what is suggested here is to standardize this further and make it available for other driver to implement in a standard consistent way.
↧

canon mirror lockup - by: astropaul

October 16, 2019, 1:10 pm
$
0
0
Hi all.
I noticed that if I not set the mirror lockup on my canon eos 50D , after the first shot all other shots are a black frame.
So my question is if I must alway s et the mirror lockup on canon or if there is other option to set on ekos.
Some days ago I tried to use a canon 1100D (with baader filter), but this camera has not the mirror lockup function and I'm not able to take shots.... fore hre previous reason (after the first shot all others are a black frame).

Any suggestion?

Thanks in advance.

Paolo
↧
↧

First time autoguiding - by: wbarsuhn

October 16, 2019, 6:40 pm
$
0
0
Last weekend was my first attempt to use the internal autoguider since I usually use PHD2. I saw that I could export the guiding data so being the geek that i am, i downloaded the from the 100 minutes of capturing M27. During the imaging session I was capturing 1 minute subs. When i opened the data and charted it in Excel I noticed there was a significant spike in the RA error every 10 minutes of the capture session. Any idea what I should be doing to correct or at least minimize this? I am using an older Meade LXD55 mount if that helps.

RAError.jpg
↧

Any news on QHY294C support? - by: sypeskder

March 1, 2019, 8:01 pm
$
0
0
Hello,

I was wondering if QHY294C support is in the works? I tried the new indi library 1.7.6 with kstars but it is still unable to detect the QHY camera.

I have tested the camera on Windows systems to ensure that it is not due to camera faults/hardware failure.

Regards,
sypeskder
↧

Can't unpark - by: Frodo 57

September 21, 2019, 12:55 am
$
0
0
I’m running Stellarmate on a RPi and have been really pleased with the functionality that has been brought together in one package. I have though been frustrated by a problem with getting the mount to connect and when it does, unparking it. I’m using the Synscan WiFi dongle on the mount which Stellarmate seems happy enough to connect to.

Four nights ago I gave the mount (HEQ5 pro) a test as I yet to use this kit to its full potential having only just acquired it and am getting used to how it works. I would add I’m a complete Ubuntu noob although happy enough with using command lines from messing about with windows computers. The test ran well I went from object to object with no trouble, everything connected as it should and performed as expected. So having visually notched up a few more Messier objects I thought the next night, I would photograph them.

The following night I set up the kit and powered up connected to the mount camera and guidescope with no problem but would the mount unpark NO it just sat there like an oversize paperweight. Ok, so applying the principal that power down and power up should sort it out that is what I did. Now the mount wouldn’t connect. After a few more attempts which included shutting everything down I managed get the mount online but still it wouldn’t unpark. Looking on the forums there seem to be a few mentions of unparking but none that seemed to relate to the issue I was having.

The third night was a night off at the astro society but even there a friend who’d put me on to using the RPi couldn’t fathom the problem. At least I got a look at the sky through the 12” Newtonian we have.

So the fourth night and I’m late to the ‘scope but again connect everything up and at first can’t even see the Synscan dongle so after a bit of tinkering I check the RPi’s connection is to the Synscan and by disconnecting and reconnecting, everything runs perfectly again. The mount slewed from object to object and even parked correctly so a success. Unfortunately the weather has turned and we have lost the clear nights for now.

Apart from the weather does anyone have any idea why having successfully connected to the mount I can’t then unpark it?
↧
Search

QHY drivers - by: patdut

October 17, 2019, 4:39 am
$
0
0
I have a question to owners of QHY163M cameras.
Is there still issues with the linux QHY drivers for INDI and this caméra on X86 and ARM platforms ?
Thanks for your answers.
↧
↧

How to use the Focus Module to focus on a galaxy - by: arminpro

October 17, 2019, 7:24 am
$
0
0
Hi,

what I did up to now is to focus manually or with auto focus on a star, which works fine!
But which settings to focus on a great object like M31 galaxy?

Sub frame or full frame?
Focus the center of the galaxy or the stars at the edge of the galaxy?

Regards,
Armin
↧

Exposure cannot be continued, ASI1600 - by: biker.fm

October 17, 2019, 9:32 am
$
0
0
When I set the exposure time to 1 second with the ASI1600 (main camera), the image is captured. After completion, the exposure cannot be continued. I set the following anytime (even the same time 1s), when the exposure time does not start, disconnect / reconnect the camera also does not help. Just close EKOS and KStars and then restart everything. When I need to set 2s or more, the problem is not reflected. I do not know if it is just ASI1600 or other cameras from ZWO (I have no other available). The problem with exposure is sometimes, not everywhere.
↧

Trying to get Stellarmate running on Raspi4 - by: bemart

October 17, 2019, 12:52 pm
$
0
0
I will start with saying how much Stellarmate impresses me every time I use it! WE have 3 observatories for teaching purposes - one equipped with a Paramount MX, one with a custom build GEM - each carrying large telescopes and a smaller observatory with an HEQ5 and Stellarmate used for various small refractors (SV 102, SV70 etc). Under good conditions I routinely get rms guiding errors between 0.7" - 1.1". For 50 bucks and a Raspi3 this is outstanding. You can see some of the images taken with this setup at martin.kcvs.ca/astro/course/gallery.html

I am now attempting to use a new Raspi4 (4G) but am unable to get the most current build (StellarMateOS_1.4.4_rpi3.img.xz) to run. It burns fine onto an SD card (using Etcher) but when installed in the Raspi does not boot. I have tried several sd cards with the same result. The Raspi4 is running fine under Raspbian. Anyone have experience and success with Stellarmate on the Raspi4?
↧

Lakeside Focuser Firmware Version - by: GN2000

October 17, 2019, 3:02 pm
$
0
0
Hi,

ive started to to get to grips with KStars and EKOS using stellarmate OS and the only issue im having at present is with my Lakeside Focuser, this is my return to astrophotoraphy after a 7 year break and the lake side is hence about 6 years old. The firmware is version 1.03 and quite dated.

I can connect fine but, any changes to the backlash, or reverse settings give a buffer read error and then usually cause a crash. The focusser will move from within EKOS but any attempt to use presets again causes a crash.

I tried to enable debug but unfortunately this enables then imediately disables, so no joy there. Im assuming that its the firmware that is the issue as the INDI drivers were probbably for later revision, but it could of course be an issue with the controller itself, from other threads im finding that people are using the lakeside with INDI and id like to if anyone had any success with a similar level of firmware ?.

Glen
↧
↧

vap0 and 19.04.2 - by: AradoSKYindi

October 17, 2019, 5:47 pm
$
0
0
Hello,

Looks vap0 is no longer working. I started from check-wlanconn.

Virtual Access Point STARTED
astroberry@astroberry:~$ sudo /usr/local/bin/astroberry_wireless
Checking if connected to AP.......... Not connected
Trying to connect to known AP
command failed: No such device (-19)
Starting Virtual Access Point
command failed: No such device (-19)
SIOCSIFADDR: No such device
vap0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
vap0: ERROR while getting interface flags: No such device
vap0: ERROR while getting interface flags: No such device
Configuration file: /etc/hostapd/hostapd.conf
Could not read interface vap0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=vap0 disabled_11b_rates=0
Could not read interface vap0 flags: No such device
nl80211 driver initialization failed.
vap0: interface state UNINITIALIZED->DISABLED
vap0: AP-DISABLED
hostapd_free_hapd_data: Interface vap0 wasn't started
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
Virtual Access Point READY

I was just starting to use new settings. I normalized all conf files and noting changed except for dnsmasq.conf. The interface=vap0 was missing after an update. I added it back and restarted. I still do not have wireless.

astroberry@astroberry:~$ systemctl status dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Thu 2019-10-17 20:34:50 EDT; 7min ag
Process: 2199 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAI

Oct 17 20:34:50 astroberry.local systemd[1]: Starting dnsmasq - A lightweight DH
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: dnsmasq: bad option at line 667
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: bad option at line 667 of /etc/d
Oct 17 20:34:50 astroberry.local dnsmasq[2199]: FAILED to start up
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Control process ex
Oct 17 20:34:50 astroberry.local systemd[1]: dnsmasq.service: Failed with result
Oct 17 20:34:50 astroberry.local systemd[1]: Failed to start dnsmasq - A lightwe

I am still investigating the mashup of the latest Ubuntu-mate update. I forgot to add the "=" sign.
↧

Trying to connect a Raspberry Camera V2.1 - by: domdomz

October 17, 2019, 7:53 pm
$
0
0
Hello, I am quite new in all the areas I am playing with (Tinkerboard, Indi, astrophotography, ...), but I have a strong computer background, being retired after 40+ years as a computer engineer...

So, I am trying to connect a Raspberry Camera V2.1 on my Tinkerboard. I am using Armbian OS but when trying to start the indi server, this is what I got:

$ indiserver -m 100 -vvv indi_v4l2_ccd
2019-10-18T02:40:22: startup: indiserver -m 100 -vvv indi_v4l2_ccd
2019-10-18T02:40:22: Driver indi_v4l2_ccd: pid=10488 rfd=3 wfd=6 efd=7
2019-10-18T02:40:22: listening to port 7624 on fd 4
2019-10-18T02:40:22: Driver indi_v4l2_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2019-10-18T02:40:22: Driver indi_v4l2_ccd: Using default decoder 'Builtin decoder'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: Supported V4L2 formats are:
2019-10-18T02:40:22: Driver indi_v4l2_ccd: Y16
2019-10-18T02:40:22: Driver indi_v4l2_ccd: NV21
2019-10-18T02:40:22: Driver indi_v4l2_ccd: BA81
2019-10-18T02:40:22: Driver indi_v4l2_ccd: YU12
2019-10-18T02:40:22: Driver indi_v4l2_ccd: NV12
2019-10-18T02:40:22: Driver indi_v4l2_ccd: YV12
2019-10-18T02:40:22: Driver indi_v4l2_ccd: BYR2
2019-10-18T02:40:22: Driver indi_v4l2_ccd: RGB3
2019-10-18T02:40:22: Driver indi_v4l2_ccd: RGGB
2019-10-18T02:40:22: Driver indi_v4l2_ccd: GRBG
2019-10-18T02:40:22: Driver indi_v4l2_ccd: JPEG
2019-10-18T02:40:22: Driver indi_v4l2_ccd: MJPG
2019-10-18T02:40:22: Driver indi_v4l2_ccd: RGBO
2019-10-18T02:40:22: Driver indi_v4l2_ccd: RGBP
2019-10-18T02:40:22: Driver indi_v4l2_ccd: YVYU
2019-10-18T02:40:22: Driver indi_v4l2_ccd: YUYV
2019-10-18T02:40:22: Driver indi_v4l2_ccd: GREY
2019-10-18T02:40:22: Driver indi_v4l2_ccd: VYUY
2019-10-18T02:40:22: Driver indi_v4l2_ccd: UYVY
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties Telescope Simulator EQUATORIAL_EOD_COORD
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties Telescope Simulator TELESCOPE_INFO
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties Telescope Simulator GEOGRAPHIC_COORD
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties Focuser Simulator ABS_ROTATOR_ANGLE
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties CCD Simulator FILTER_SLOT
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties CCD Simulator FILTER_NAME
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on CCD Simulator.FILTER_NAME
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read getProperties SQM SKY_QUALITY
2019-10-18T02:40:22: Driver indi_v4l2_ccd: snooping on SQM.SKY_QUALITY
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defSwitchVector V4L2 CCD CONNECTION Idle rw
CONNECT='Off'
DISCONNECT='On'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defTextVector V4L2 CCD DRIVER_INFO Idle ro
DRIVER_NAME='V4L2 CCD'
DRIVER_EXEC='indi_v4l2_ccd'
DRIVER_VERSION='1.0'
DRIVER_INTERFACE='2'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defNumberVector V4L2 CCD POLLING_PERIOD Idle rw
PERIOD_MS='1000'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defSwitchVector V4L2 CCD DEBUG Idle rw
ENABLE='Off'
DISABLE='On'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defSwitchVector V4L2 CCD CONFIG_PROCESS Idle rw
CONFIG_LOAD='Off'
CONFIG_SAVE='Off'
CONFIG_DEFAULT='Off'
CONFIG_PURGE='Off'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defTextVector V4L2 CCD ACTIVE_DEVICES Idle rw
ACTIVE_TELESCOPE='Telescope Simulator'
ACTIVE_FOCUSER='Focuser Simulator'
ACTIVE_FILTER='CCD Simulator'
ACTIVE_SKYQUALITY='SQM'
2019-10-18T02:40:22: Driver indi_v4l2_ccd: read defTextVector V4L2 CCD DEVICE_PORT Idle rw
PORT='/dev/video0'

and it is stuck here ... I have to stop it by Ctrl-C

And here is the output for "media-ctl" which shows that my camera is detected and I have been able to grab both videos and pictures.

$ media-ctl -p
Media controller API version 0.1.0

Media device information
driver rkisp1
model rkisp1
serial
bus info
hw revision 0x0
driver version 0.0.0

Device topology
- entity 1: rkisp1-isp-subdev (4 pads, 5 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev0
pad0: Sink
[fmt:SBGGR10_1X10/800x600 field:none
crop.bounds:(0,0)/800x600
crop:(0,0)/800x600]
<- "rockchip-sy-mipi-dphy":1 [ENABLED]
pad1: Sink
<- "rkisp1-input-params":0 [ENABLED]
pad2: Source
[fmt:YUYV8_2X8/800x600 field:none
crop.bounds:(0,0)/800x600
crop:(0,0)/800x600]
-> "rkisp1_selfpath":0 [ENABLED]
-> "rkisp1_mainpath":0 [ENABLED]
pad3: Source
-> "rkisp1-statistics":0 [ENABLED]

- entity 2: rkisp1_mainpath (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video0
pad0: Sink
<- "rkisp1-isp-subdev":2 [ENABLED]

- entity 3: rkisp1_selfpath (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video1
pad0: Sink
<- "rkisp1-isp-subdev":2 [ENABLED]

- entity 4: rkisp1-statistics (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video2
pad0: Sink
<- "rkisp1-isp-subdev":3 [ENABLED]

- entity 5: rkisp1-input-params (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video3
pad0: Source
-> "rkisp1-isp-subdev":1 [ENABLED]

- entity 6: rockchip-sy-mipi-dphy (2 pads, 2 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev1
pad0: Sink
[fmt:SRGGB10_1X10/1920x1080 field:none]
<- "imx219 2-0010":0 [ENABLED]
pad1: Source
[fmt:SRGGB10_1X10/1920x1080 field:none]
-> "rkisp1-isp-subdev":0 [ENABLED]

- entity 7: imx219 2-0010 (1 pad, 1 link)
type V4L2 subdev subtype Sensor flags 0
device node name /dev/v4l-subdev2
pad0: Source
[fmt:SRGGB10_1X10/1920x1080 field:none]
-> "rockchip-sy-mipi-dphy":0 [ENABLED]

Any help would be much appreciated.

Please excuse my english as I am french (nobody is perfect ;-0)
↧
Search

Installing library Indi-Bin under Raspbian fails - by: hzimmer3

October 16, 2019, 6:44 am
$
0
0
Today I tried to install indi lib Indi-Bin onm my RaspBerry Pi3 with Raspbian/IndigoSky to add support for SestoSenso focuser, but installation failed with missing library dependancies
as follows:
sudo apt-get -y install indi-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-bin : Depends: libcfitsio2 (>= 3.370) but it is not installable
Depends: libindi1 but it is not going to be installed
Depends: libnova-0.14-0 but it is not installable
E: Unable to correct problems, you have held broken packages.

What can I do to resolve this problem?
Any help is highly appreciated.

Thanks in advance
Helmut
Cologne/Germany
↧

New mount RA/DEC PWM Number for mount balancing - by: dolguldur

October 18, 2019, 5:03 am
$
0
0
Dear all,

First of all, thank you a lot for all the work done with indi. This tool really amaze me everyday, and makes so many new things possible for amateur astronomer !
I am now coming with a new requirement I hope will be considered in the future, at least for the mount simulator.

Let me explain, many german equatorial mounts provide a solution to assess the balance of the mount, Losmandy, 10microns, probably plenty of other brands.
I am particularly interested in the Losmandy driver and the simulator, because it is the one I own, and I would like to be able to programmatically retrieve the "balancing" values you can see on the hand controller there:
www.gemini-2.com/hc/En-balance.php
EN-balance.jpg


They provide Dec axis duty cycle in percentage as Y and RA axis duty cycle in percentage as X. I would love to have access to those values within indi when available.
Having this feature also available in the simulator, and every other mount that provides this type of value, would be really awesome!

Thank you in advance for your help
↧
↧

Canon DSLR connect error to Astroberry/Ekos/INDI - by: hzimmer3

October 18, 2019, 10:14 am
$
0
0
Hello Fellow Astronomers,
I just have installed Astroberry/Indilib/Kstars/Ekos on my Raspberry Pi and ZWO Asi camera, EQMod mount, guide camera, focuser are working flawlessly.

Now I wanted to setup my Canon EOS 80D DSLR as well. In the INDI server I loaded the Canon DSLR driver, in Ekos I configured the CCD as Canon DSLR.
The DSLR is connected to the Raspi via USB connection. USB connection under Windows works without problems. When I connect Ekos to the DSLR I get
"green light" for th connection, however when I try to take a capture, I get error message that capture is not possible and The DSLR displays a message
on its LCD screen: "Error! Switch off the camera and switch on again".

In a n Ubuntu terminal, when doing a "gphoto2 -a" I get the info:
Abilities for camera: USB PTP class camera
Serial port support: no
USB support: yes
Capture choice: Image, Preview
Configuration support: yes
Delete selected files on camera: yes
Delete all files on camera: no
File preview (thumbnails): yes
File upload: yes

gphoto2 --auto-detect gives:

USB PTP class camera USB port usb:001,005

When I try to take an image ina terminal with "gphoto2 --capture-image" then the shutter is released, an image is taken but then the image is not
stored on the camera SDHC card, the camera says "busy" and in the terminal after a minute I get the error message:

*** Error ***
Canon EOS full press failed (0x2019: PTP device busy)
ERROR: could not capture image
ERROR: could not capture

Has anyone successfully connected Canon DSLRs with Astroberry/Indi ?

I would appreciate any hint on what I can do tho overcome this problem.

Clear night skies !

Helmut Zimmermann
Cologne/Germany
↧

Capture module - Save images only in the camera SD - by: JorgeHdz242

October 18, 2019, 11:42 am
$
0
0
Hi, i have a problem my microsd with ekos is full with indexes for plate solving , and i need to save my captured images only on the camera's SD, this is possible?
Thanks in advance.!
↧

Kstars/Ekos setup for Pegasus PPB - by: mjsmira

October 18, 2019, 5:02 pm
$
0
0
Hi,

I have a Stellarmate in a RPI4 connected to my setup that includes a Pegasus PPB. On Stellarmate I can select that device on Ekos profile editor.

But from windows the Ekos profile editor doesn't have the Pegasus PPB.

I checked the file C:\Program Files\KStars Desktop Planetarium\bin\data\kstars\indidrivers.xml and I found the entry for it (indi_pegasus_ppb).

Is there anything I can do to enable that device on the Auxiliary devices combo box?
↧
Viewing all 15748 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>