Stephen Wong replied to the topic 'Indi on the rocks (a Rock64 to be exact)' in the forum. 5 days ago

wimvb,
Try upgrading the firmware of ASI120 from ASI website. That solves my problem.
What I encountered was, I was on a Pi3, having one SD card with ubuntu installed, and another one with raspbian.
The ubuntu works fine with the ASI120mm (usb2)
but Raspbian unable to connect.
Then I go upgrade the firmware.. then works fine in both OS
Stephen

Read More...

unfortunately it's a 32-bit. if there's anything I can do to get the debug info please let me know

uname -m
armv7l

Read More...

I'm capturing RAW with max resolution. The OS is a ubuntu 16.04 in RPi 3. I think it's 64bit and I'll have to recheck later tonight to make sure. I did switched on the Debug in the EKOS but all it captures was just a few lines.

If you can get me a debug version of 64Bit I can certainly put this and run the test and send you back the Debug info. Thank you.

Read More...

EKOS was able to connect to the ASI ZWO 183MM Pro.
But crashed on Preview or Capturing... anybody help? Here's the log, see below in RED



org.kde.kstars.indi: INDI: Starting local drivers...
org.kde.kstars.indi: Starting INDI Server: ("-v", "-p", "7624", "-m", "100", "-f", "/tmp/indififo332d64f8") -f "/tmp/indififo332d64f8"
org.kde.kstars.indi: INDI Server Started? true
org.kde.kstars.indi: INDI: INDI Server started locally on port 7624
org.kde.kstars.indi: Starting INDI Driver "indi_asi_ccd"
org.kde.kstars.indi: Adding managed driver "ZWO CCD"
org.kde.kstars.indi: INDIListener: Adding a new client manager to INDI listener..
org.kde.kstars.indi: INDI: Connecting to local INDI server on port 7624 ...
org.kde.kstars.indi: INDI server connected.
org.kde.kstars.indi: Connection to INDI server is successful
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififo332d64f8 "
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: listening to port 7624 on fd 3"
org.kde.kstars.indi: INDI Server: "FIFO: start indi_asi_ccd"
org.kde.kstars.indi: INDI Server: "FIFO: Starting driver indi_asi_ccd"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: pid=4146 rfd=4 wfd=7 efd=8"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Client 5: new arrival from 127.0.0.1:47212 - welcome!"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: Received new device ZWO CCD ASI183MM Pro
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: INDIListener: New device ZWO CCD ASI183MM Pro
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CONNECTION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DRIVER_INFO >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DEBUG >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < SIMULATION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CONFIG_PROCESS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < ACTIVE_DEVICES >
org.kde.kstars.ekos: 1 devices connected out of 1
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_EXPOSURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_ABORT_EXPOSURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_BINNING >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < FITS_HEADER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_TEMPERATURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_INFO >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COMPRESSION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD1 >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME_TYPE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME_RESET >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_RAPID_GUIDE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < TELESCOPE_TYPE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < WCS_CONTROL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < UPLOAD_MODE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < UPLOAD_SETTINGS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_VIDEO_STREAM >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < STREAM_OPTIONS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < FPS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_STREAM >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_FILE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_OPTIONS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_FRAME >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_ENCODER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_RECORDER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COOLER_POWER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COOLER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_CONTROLS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_CONTROLS_MODE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_VIDEO_FORMAT >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DEBUG_LEVEL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < LOGGING_LEVEL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < LOG_OUTPUT >
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] Toggle Debug Level -- Driver Debug "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] Toggle Logging Level -- Driver Debug "
org.kde.kstars.ekos.capture: Preparing capture job "Light" for execution.
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] ASIGetExpStatus failed (0). Restarting exposure... "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] ASIGetExpStatus failed (0). Restarting exposure... "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
*** stack smashing detected ***: terminated
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: stderr EOF"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: restart #1"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: pid=4165 rfd=4 wfd=8 efd=9"
org.kde.kstars.indi: INDI Server: "Child process 4146 died"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: INDI driver "indi_asi_ccd" crashed!

Read More...

Stephen Wong replied to the topic 'My Raspberry Pi 3 Setup' in the forum. 3 weeks ago

I got a LEGO case for my Rpi and with a piece of LEGO attached to a case of 5V lithium battery outfit, I can attach the RPi to the battery. Then mount it with a special made saddle on the counterweight side. The saddle also allows me to mount a large 12V lithium battery so I don’t need to carry a counterweight at all during the image session.

Read More...

Stephen Wong replied to the topic 'Strange Bias on Atik460EX' in the forum. 11 months ago

I tried the capturing problem is gone with v1.17

Read More...

Stephen Wong replied to the topic 'Strange Bias on Atik460EX' in the forum. 12 months ago

output of atik_ccd_test

ubuntu@ubuntu-standard:~$ atik_ccd_test

version 1.16

list



-> AtikCamera::list(...)
'Atik 490ex' [0x20e7, 0xdf3a] found...
-> AtikCameraImpl::AtikCameraImpl(..., Atik 490ex, 2)
maxPacketSize = 25165824
<- AtikCameraImpl::AtikCameraImpl
<- AtikCamera::list 1

open Atik 490ex

-> AtikCameraImpl::open()
libusb_claim_interface() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
libusb_set_interface_alt_setting() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
-> AtikCameraImpl::writeFW()
cpu stopped 1
cpu started 1
<- AtikCameraImpl::writeFW 1
-> AtikCameraImpl::setPortDirection(0, 0x9f)
<- AtikCameraImpl::setPortDirection 1
-> AtikCameraImpl::setPortState(0, 0x80)
<- AtikCameraImpl::setPortState 1
-> AtikCameraImpl::i2cSetTimeout(50)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(50)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::i2cSetSpeed(0)
<- AtikCameraImpl::i2cSetSpeed 1
-> AtikCameraImpl::flush()
libusb_bulk_transfer -> LIBUSB_ERROR_TIMEOUT
0 bytes flushed
<- AtikCameraImpl::flush
-> AtikCameraImpl::i2cSetTimeout(5000)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::eepRead(3, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x03], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x3a 0xdf]
<- AtikCameraImpl::eepRead 1 [0x3a 0xdf]
-> AtikCameraImpl::eepRead(1000, ..., 5)
-> AtikCameraImpl::i2cWrite(81, [0x00 0xe8], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 5)
<- AtikCameraImpl::i2cRead 1 [0xff 0xff 0xff 0xff...]
<- AtikCameraImpl::eepRead 1 [0xff 0xff 0xff 0xff...]
colour = 1, offsetX = 0, offsetY = 0
pid = df3a
-> AtikCameraImpl::i2cSetTimeout(100)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(1000)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::parInit(9)
-> AtikCameraImpl::parInit(...)
<- AtikCameraImpl::parInit 1
<- AtikCameraImpl::parInit 1
-> AtikCameraImpl::ping()
ping -> 100
-> AtikCameraImpl::sendCommand(80, [0x64], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 101
<- AtikCameraImpl::ping 1
-> AtikCameraImpl::sendCommand(1, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
version: 3.37
model: ATIK-490ex
manufacturer: ARTEMIS CCD
flags: 0x158 PREVIEW SUBSAMPLE OVERLAP
pixel count: 3380 x 2704
pixel size: 3.7 x 3.7
max bin: 255 x 255
well capacity: 60
-> AtikCameraImpl::appInit()
-> AtikCameraImpl::sendCommand(44, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
DEBUG OFF

DEBUG ON
APPINIT completed
<- AtikCameraImpl::appInit 1
-> AtikCameraImpl::sendCommand(54, NULL, ..., 0, 2)
<- AtikCameraImpl::sendCommand 1 [0x01 0x00]
temperature sensor count: 1
-> AtikCameraImpl::getTemperatureSensorStatus(1, ...)
lock()
-> AtikCameraImpl::sendCommand(55, [0x01 0x00], ..., 2, 6)
<- AtikCameraImpl::sendCommand 1 [0x02 0x00 0x00 0x00...]
unlock()
<- AtikCameraImpl::getTemperatureSensorStatus 1
temperature sensor type: 2
-> AtikCameraImpl::sendCommand(52, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x1f 0x00 0xff 0x00...]
cooler: COOLER_SETPOINT
min cooler power: 0
max cooler power: 255
-> AtikCameraImpl::eepRead(5, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x05], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x93 0x7e]
<- AtikCameraImpl::eepRead 1 [0x93 0x7e]
-> AtikCameraImpl::eepRead(8, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x08], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x4f 0x5b]
<- AtikCameraImpl::eepRead 1 [0x4f 0x5b]
serial # 1531936403
-> AtikCameraImpl::i2cSetTimeout(200)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(2000)
<- AtikCameraImpl::setParTimeout 1
<- AtikCameraImpl::open 1

getCapabilities

-> AtikCameraImpl::getCapabilities(...)
<- AtikCameraImpl::getCapabilities 1

setPreviewMode

-> AtikCameraImpl::setPreviewMode(0)
not changed
<- AtikCameraImpl::setPreviewMode 1

set8BitMode

-> AtikCameraImpl::set8BitMode(0)
<- AtikCameraImpl::set8BitMode 1

getTemperatureSensorStatus

-> AtikCameraImpl::getTemperatureSensorStatus(1, ...)
lock()
-> AtikCameraImpl::sendCommand(55, [0x01 0x00], ..., 2, 6)
<- AtikCameraImpl::sendCommand 1 [0x02 0x00 0xa3 0x03...]
current temperature: 15.0
unlock()
<- AtikCameraImpl::getTemperatureSensorStatus 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x00 0x00 0x1f 0x00...]
cooler state: COOLING_INACTIVE
target temperature: -60.0
power: 0%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

setCooling

-> atikSetCooling(-10.0)
lock()
-> AtikCameraImpl::sendCommand(56, [0x6c 0x02], ..., 2, 2)
<- AtikCameraImpl::sendCommand 1 [0x01 0x00]
unlock()
<- AtikCameraImpl::setCooling 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x00 0x00 0xdf 0x00...]
cooler state: COOLING_SETPOINT
target temperature: -10.0
power: 0%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

initiateWarmUp

-> AtikCameraImpl::initiateWarmUp()
lock()
-> AtikCameraImpl::sendCommand(57, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
unlock()
<- AtikCameraImpl::initiateWarmUp 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0xf4 0x00 0x7f 0x00...]
cooler state: WARMING_UP
target temperature: -10.0
power: 95%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

readCCD (short)


3380x2704 rounded to 3380x2704

-> AtikCameraImpl::readCCD(0, 0, 3380, 2704, 1, 1, 0.500000)
lock()
-> AtikCameraImpl::setParTimeout(30000)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::sendCommand(2, [0x00 0x00], ..., 2, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(4, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(5, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(6, [0xf4 0x01 0x01 0x00...], ..., 16, 0)
<- AtikCameraImpl::sendCommand 1 NULL
<- AtikCameraImpl::readCCD 1

getImage

-> AtikCameraImpl::getImage(..., 9139520)
libusb_bulk_transfer -> LIBUSB_ERROR_IO
elapsed 0.101154 s
-> AtikCameraImpl::setParTimeout(1000)
<- AtikCameraImpl::setParTimeout 1
unlock()
<- AtikCameraImpl::getImage 0 [0x00 0x00 0x00 0x00...]

close

-> AtikCameraImpl::close()
<- AtikCameraImpl::close

Atik 490ex test failed: Failed to get image
ubuntu@ubuntu-standard:~$

Read More...

Stephen Wong replied to the topic 'Strange Bias on Atik460EX' in the forum. 12 months ago

pi3 ubuntu.. arm

Read More...

Stephen Wong replied to the topic 'Strange Bias on Atik460EX' in the forum. 12 months ago

I tried 1.16 and the download problem came back... EKOS just keep "Downloading...." and does not move after the capture is done on the 1st frame

Read More...

Stephen Wong replied to the topic '[bug]Load seq file, start capturing,goes Completed right away' in the forum. 12 months ago

Sorry you're right, I unchcecked remember job progress and that solves the problem. Thanks!

Read More...

Stephen Wong created a new topic ' [bug]Load seq file, start capturing,goes Completed right away' in the forum. 12 months ago

Updated to the latest KStar Ekos, When I load the sequence file from disk, start capturing, the progress will go into "Complete" right away.
This does not happens if I add the sequence from the capturing module manually inputting the parameters

Read More...

Stephen Wong replied to the topic 'Are Ekos settings suppposed to be saved on exit?' in the forum. 1 year ago

Thank you! Saving at the .esq file works for me. The "Apply settings" would certainly be one of my items on the wish list.
Thanks again!

Read More...

Stephen Wong replied to the topic 'Are Ekos settings suppposed to be saved on exit?' in the forum. 1 year ago

I certainly tried the save settings on the camera setup, which EKOS did save the config on the xml under ~/.indi folder, and loading it is fine also... but the settings only applies to the camera option tab, but not being populated into the CCD/camera shooting tab.....

Read More...

Stephen Wong replied to the topic 'What would you like to see in Ekos in 2017?' in the forum. 1 year ago

May be Something like "Bahtinov grabber" that measures the focus accuracy from a bahtinov mask?

By the way, the current preview window in the focus function do not have zoom in/out buttons, this is a bit inconvenient. Although scrolling the mouse middle button would zoom but mostly I take notebook computer for imaging session and I'd use touchpad, which is not convenient when I want to zoom in/out

Read More...

Stephen Wong replied to the topic 'Are Ekos settings suppposed to be saved on exit?' in the forum. 1 year ago

I have a problem... the latest EKOS do not save the Upload (Client, Remote, Both) and the remote path settings during exit. I have tried many times and yet it's defaulted as "Client" every time I started EKOS

I'm using ubuntu 16.04 on Raspberry Pi 3.

The biggest problem I've encountered is that I've spent a night session shooting the FITS using my Atik CCD, but NONE of the frames were written on the disk. It seems that the reason was due to the Upload settings were defaulted as "Client" - which only put the FITS to shows on the preview window and have not write the files to the Directory settings.

So every time I launch EKOS I have to remember to change the Upload to Both or Local in order to write the file on disk. Hopefully there's a way to make the Upload settings persist so I do not have to change it before every image shooting session....

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!