Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. yesterday

Nice to see success with the driver :)

I was thinking that there is a couple of options here, the easiest option would be to keep your changes to the sx driver and rename the file to something like indi-sxv and register as a new driver in the xml-file, the drawback would be you have to recompile the driver now and then and also patch the xml-file every time there is a update from ppa.
The second option is to find a way to recognize the camera and use your patched way to read the pixels, maybe Jasem would accept the way to do it.

So how to recognize the specific camera, I don't know if there is a way to get the id of the ccd, that would be the easiest way, otherwise maybe check for the exact resolution of the ccd ?? but that can create problems if there is an other cam with the same resolution so that's a bad way to do it.
I also thought about checking the cam's firmware version and resolution but that can also be a gamble.. ??
I'm a bit puzzled when checking the log you posted because it looks like it identifies it self as a "SX CCD SXVR-M25C" in "sxGetCameraModel" ??

Well done!!

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 5 days ago

@AstroNerd
Yes, you are correct, the driver works perfectly for sx cameras and I'm using it too, but I think it should work for his cam too.

@bluthen
I wrote a quick start manual (if it can be called like that) for you so you can do some testing yourself :)

sudo apt install git build-essential cmake libindi-dev libnova-dev libgsl-dev libusb-1.0-0-dev libcfitsio-dev

git clone --depth=1 https://github.com/indilib/indi-3rdparty.git  (directory indi-3rdparty will be created)
cd indi-3rdparty
cd indi-sx
mkdir build
cd build
cmake ..                  (if some libs are missing then it tells you what's missing)
make                       (if there is no errors reported go for next command)
indiserver ./indi_sx_ccd    (have your cam connected and run this for testing the new driver)

I hope I didn't miss anything..

/Markku

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 6 days ago

I checked the driver source and found this.. your cam have usbid the same as the SXVR-M25C so that is a problem, but I don't know how to make a difference between two cams with the same usbid, and that's why it's recognized wrong.

File : sxccdusb.cpp

static struct
{
    int pid;
    const char *name;
    int seq;
} SX_PIDS[] = { { 0x105, "SXVF-M5", 0 },
                { 0x305, "SXVF-M5C", 0 },
                { 0x107, "SXVF-M7", 0 },
                { 0x307, "SXVF-M7C", 0 },
                { 0x308, "SXVF-M8C", 0 },
                { 0x109, "SXVF-M9", 0 },
                { 0x325, "SXVR-M25C", 0 },
                { 0x326, "SXVR-M26C", 0 },
                { 0x115, "SXVR-H5", 0 },
                { 0x119, "SXVR-H9", 0 },  (The list continues to cover rest of the SX cameras..)

The other thing is in the file : sxccd.cpp
Because of this line "else if (isICX453)" the driver reads the cam a wrong way ?? Well, I'm just guessing but Jasem is probably the right guy to sort this out.
void SXCCD::SetupParms()
{
    struct t_sxccd_params params;
    model             = sxGetCameraModel(handle);
    bool isInterlaced = sxIsInterlaced(model);
    bool isICX453     = sxIsICX453(model);
    PrimaryCCD.setInterlaced(isInterlaced);
    sxGetCameraParams(handle, 0, &params);
    if (isInterlaced)
    {
        params.pix_height /= 2;
        params.height *= 2;
        wipeDelay = 130000;
    }
    else if (isICX453)
    {
        params.width = 3032;
        params.height = 2016;
    }
    SetCCDParams(params.width, params.height, params.bits_per_pixel, params.pix_width, params.pix_height);

/Markku

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 7 days ago

Now we get somewhere.. sx_ccd_test recognizes the camera as a "SXVR-M25C" but seems to read the CCD as a "SXV-M25C" and that makes some confusion I guess.. or maybe the error from your first post "Driver indi_sx_ccd: sxReadPixels: libusb_control_transfer -> LIBUSB_ERROR_TIMEOUT" is the cause of this ?
I think Jasem is the guy for this little problem, so I hope he will chime in here and take a look..

/Markku

Read More...

Markku Siitonen replied to the topic 'Mounting external drive help needed' in the forum. 2 weeks ago

The log looks good to me :) and if it's working then no need to fix anything :)
Not sure if you did anything wrong but we can call it a glitch :)

Cs,
/Markku

Read More...

Markku Siitonen replied to the topic 'Mounting external drive help needed' in the forum. 2 weeks ago

First of all I don't use Stellarmate myself and is a bit confused why it says "you are not authorized to mount this device" ? If the USB3 cable is recognized by the system it should mount in /media/USERNAME/VolumeLable and should be visible as a disc drive.

Anyway, let's get some info from the device...

Start up your Pi without the disc..
Start a terminal window.. (maybe keyboard shortcut : Alt+Ctrl+T)
Enter the command : tail -f /var/log/syslog
Press a couple of "Enter" to get some new empty lines..
Insert the USB3 SSD and there will be some lines of text rolling by.. then when the text stops take a copy of all that text and paste in the forum.
That info will contain the info needed to see what is going on when Stellarmate is trying to mount the drive.

That's all for now :)

Read More...

Markku Siitonen replied to the topic 'Mounting external drive help needed' in the forum. 3 weeks ago

Hi,

I can think of 3 ways to do that quite easily..

1) Automatically mounted when Pi is booted : sudo nano /etc/fstab
2) Manually mounted : sudo mount /dev/sdb?? ~/directoryName
3) Mounted with a udev rule : /lib/udev/rules.d/

But I think it would be better to use FAT32 instead of NTFS, just my opinion.
If I get some time tomorrow or the weekend I can give you a example to get you going.

Br,
/Markku

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 4 weeks ago

There is a small utility in INDI called : sx_ccd_test run in a terminal and see what it says.. when running that with my cams I get correct results.

I guess it doesn't hurt to try the resolutions..
I wish my obsy would be that far away from the city, I have about 20 minutes drive and the city lights can be a bit disturbing some nights.

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 4 weeks ago

Ok, so the resolution is a bit different then..
www.sxccd.com/handbooks/SXV-M25C%20handbook.pdf

I guess you already tried setting the resolution manually in INDI Controlpanel CCD Image settings ??
It could be something else too that messes up things, maybe you could try the cam on Windows and the software from sxccd.com and see if it works.

Cs,
/Markku

Read More...

Markku Siitonen replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 4 weeks ago

Hi,

From the logfile I found this..
[2019-09-23T22:02:28.050 CDT DEBG ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[DEBUG] Requested CCD Frame is (0,0) (21946 x 39648) "
[2019-09-23T22:02:28.052 CDT INFO ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[ERROR] Error: Requested image out of bounds (21946, 39648) "
[2019-09-23T22:02:28.057 CDT INFO ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[INFO] Device configuration applied. "
[2019-09-23T22:02:28.057 CDT DEBG ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[DEBUG] Configuration successfully loaded. "

But according to the manual for the camera : www.sxccd.com/handbooks/SXVR-M25C%20handbook.pdf
It should be : 3032 x 2016 pixel array. Each pixel is 7.4 x 7.4uM
So maybe the problem is there ??

Cs,
/Markku

Read More...

Markku Siitonen replied to the topic 'Can't unpark' in the forum. 4 weeks ago

Hi,

I'm at work now so I can't check this but in directory "~/.indi/" you can check your telescope file and there should be an entry in XML-format called "Parked" or similar, it probably says "True" but you can change it to "False", after that start up everything and see what happens.

Cs,
/Markku

Read More...

Markku Siitonen replied to the topic 'Missing text in KStars tool bar' in the forum. 1 month ago

That's great :)

A simple explanation would be that the first part "sudo updatedb" creates a database of all filenames and paths it can find in the system, the second part "locate kstarsrc" reads the database and get the filename and path to the file you specify.
The semicolon is there just to separate the two commands from each other.
Next time if no files are added or removed to the system you can just do a "locate filename" and find the specified file.
You can read more of the commands with : man updatedb and man locate

Fast and easy.

Cs,
/Markku

Read More...