I tried the newer firmware and it causes the image download to fail on my DSI Pro:

2020-09-22T02:28:01: Driver indi_dsi_ccd: read even data, status = (0) Success
2020-09-22T02:28:01: Driver indi_dsi_ccd:     requested 388608 bytes 768 x 253 (even pixels)
2020-09-22T02:30:01: Driver indi_dsi_ccd: r 86 0                                  [dt=120001]
2020-09-22T02:30:01: Driver indi_dsi_ccd: read odd data, status = (-7) Argument list too long
2020-09-22T02:30:01: Driver indi_dsi_ccd:     requested 387072 bytes 768 x 252 (odd pixels)
2020-09-22T02:30:01: Driver indi_dsi_ccd: terminate called after throwing an instance of 'DSI::device_read_error'
2020-09-22T02:30:01: Driver indi_dsi_ccd:   what():  read odd data, status = (-7) Argument list too long
2020-09-22T02:30:01: Driver indi_dsi_ccd: stderr EOF
<delProperty device="DSI"/>
Child process 235489 died

Awesome, that's great! I can try it on my DSI Pro (I) later tonight.

-Ben

Read More...

If you have the pcap, could you please attach it? I'm trying to figure out exactly how many bytes are actually available from the camera. I don't understand why the driver is trying to download 1536x1050 pixels...even after looking at the code.

One thing that I did realize is that the ICX285 sensors are progressive scan CCDs rather than interlaced like the rest of the DSI families use. This is handled in the code by only using the "odd" field and setting the "even" field to 0.

The user that added support for the DSI III cameras had the Color version, not the Pro...though I would expect this aspect to remain the same between those two.

Thanks,
Ben

Read More...

It's possible that nobody has ever tried to use a DSI III Pro with the INDI driver before.

The data that you collected is excellent. After a little googling, it looks like the DSI III Pro uses the ICX285AL, which an active pixel array of 1360x1024. Even the total pixel array (1434x1050) doesn't quite match what the logs seem to indicate. I'll have to look at the code to be sure. But, I suspect that you're on the right track that the issue is the driver trying to download more data than is available.

I'll let you know what I find.

Thanks,
Ben

Read More...

Jasem already merged the change. I think the packages in his PPA get rebuilt nightly so I suspect that if you upgrade tomorrow that your camera should work. Enjoy!

-Ben

Read More...

That's great news! I've submitted the change to be included upstream. Once that happens (I'll update this thread) then yes, you should be able to do upgrades and have the camera just work.

Thanks,
Ben

Read More...

You could try installing libindi-dev (sudo apt-get install libindi-dev). I think that should do it.

Read More...

Sorry, for that step do:
git clone github.com/bgilsrud/indi-3rdparty.git

You can see the code change that I made here: github.com/indilib/indi-3rdparty/compare...el_name_fix?expand=1

The field programmed into your camera's EEPROM is wrong. I've made a change to check the CCD model or the camera model. Checking the camera model seems like the more obvious, direct way to identify the camera...but it's more difficult to guess what it should be since I don't have access to every DSI I, II, III in both mono (Pro) and color. The CCD names for these are less mysterious.

Thanks,
Ben

Read More...

If you're up for testing the change, here are the instructions:

sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev git

git clone github.com/bgilsrud/indi-3rdparty.git
cd indi-3rdparty
git checkout dsi_model_name_fix
mkdir -p build/indi-dsi
cd build/indi-dsi/
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../indi-dsi/
make
sudo make install

Then you could try to figure up ekos as you normally do (remember to select your normal profile!) and I'm hoping that it works. If you're able to verify this, then I'll submit the code change upstream.

Thanks,
Ben

Read More...

The problem is that the name of the CCD that's reported by the DSI is wrong! It says "IXC245AL"...the actual name is "ICX254AL". Unfortunately, the indi driver uses this name to determine what type of DSI it is (even though there's another field that we can read from the camera that describes what type of DSI it is!).

I'm not sure how your camera got to be this way, but I can make a change to the driver to check the both the CCD name and the device name (yours correctly identifies as a "DSI Pro"). It's a simple change and won't take too long.

Thanks,
Ben

Read More...

Sorry, I forgot that we need something to initiate the connection. Can you leave that running and then start ekos. You can create a new profile and select the "Remote" setting in the "Mode" section. Leave everything else as the default and save it. Then click the start button (play symbol) under "2. Start & Stop Ekos". Then I'm hopeful that you'll see some output in the terminal where you are running the indiserver command.

Read More...

Can you run this (close kstars/ekos first):

export LIBUSB_DEBUG=3
indiserver -v indi_dsi_ccd

Read More...

The permissions look good. Could you run:
touch /dev/bus/usb/002/005

and also:
fuser /dev/bus/usb/002/005

and:
dmesg | tail

Read More...