Russell Valentine replied to the topic 'Mesu Mount 200 Driver Request' in the forum. 3 months ago

Is there any support for the idea of incorporating what they had in their github repo into the 3rd-party repo of drivers that get built? Maybe with a warning that the driver is not self contained.
github.com/JeffRossMT/sitech-indi-driver

I know it requires a windows machine with their software running, but could be better than nothing and make it possible to still use very nice kstars/ekos/indi stack with it. I can understand if you are totally against the idea, but thought I'd ask.

I think I am about to try this next. I imagine it might need some modification since it hadn't been updated in a year, if I can fix it up, would a PR to include it be accepted?

Read More...

Russell Valentine created a new topic ' windi (ascom indi bridge) solve/guide issue' in the forum. 3 months ago

My setup to help explain my issue:

Using KStars/Ekos on a windows machine
Sitech mount with it's ascom driver installed
windi ascom to indi bridge is running on the windows machine
RPi running indiwebwebmanager is installed
SBIG camera with built in guide/AO is connected to the RPI


I use Ekos to connect through indiwebmanager setting sbig as the camera and set remote url to the windows windi server.

Imaging from the main sbig and guide cam works, syncing and slewing the mount works.

Whenever I try to guide or solve I get an error. For example when trying to solve it just errors before doing anything "Telescope aperture and focal length are missing. Please check your driver settings and try again." When I try to guide I get a similar error and I notice none of the info is there for focal length, apature, etc on the guide tab.

On the telescope tab if I set a apature and focal length and hit "save telescope info" Nothing happens. There is nothing in the drop down under configurations. I am guessing that the issue might be there. Maybe the windi indi bridge doesn't support storing that info? I am not sure.

Does anyone have a workaround? It would be nice if I can just overwrite those setting and not require it to be in the mount itself or something. Or maybe I don't understand that part about INDI. In anycase I am hoping someone can help.

Read More...

Russell Valentine replied to the topic 'Mesu Mount 200 Driver Request' in the forum. 4 months ago

@knro

I originally thought I could use INDI with a Sitech controller in an LX200 compatible mode. However I notice that mode is just a layer in front of the windows app. And the driver on github still expects the windows driver to be running (maybe it can be done through wine if mono didn't work? It would still launch their UI, but maybe better than nothing.)

Last I heard you didn't have any of the hardware, would it help if you had the hardware? Maybe I can contribute in part to a fund to help in the cost of one of the controllers? If you are not interested going that route, it is okay, was just thinking.

Thanks!

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 4 months ago

@knro

Ok using 7cc5083cc152aeaa4edc9b6fd824771945a95f60 checkout in indi-3rdparty. Red is blue and the other colors look pretty gray in the KStars FITS Viewer.

The fits file:
drive.google.com/file/d/1kevYZIeXffF76uE...MRk/view?usp=sharing

I can look into what might be happening sometime tomorrow probably.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 5 months ago

I took some images tonight and viewed them through the fits viewer. I took a picture of that same color chart with the pin hole setup. The colors for sure are off. I notice right off the bat red shows as green. I'll be able to look specifically what is going on with the bayer matrix Thursday evening and will reply with my findings.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 5 months ago

I've maybe misunderstood your message. If your recent bayer change is in, I can try it next time I'm out.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 5 months ago

I've had a hard time finding any good information of how the bayer matrix should be with these cameras. Some forums like on cloudy nights implied that each chip could possibly have a different one (I kind of find it hard to believe).

I did have good luck with color. I made a pinhole lens with foil and a color chart with construction paper. So if for example I force RGGB and up-bottom orientation in Siril(I believe this setting used to be called kstars-ekos/pixinsight compatibility) and some white balancing, I get the attached image.

I've also taken a test image of M33 and the colors seemed pretty good this way. I've had some set backs with my setup so that is as far as I got. I hope to get back on track after all these holidays.

I'm not an expert on maxim but maybe it has something to do with the up-bottom orientation?



Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 7 months ago

So I've been able to take home the camera to try some more things. It really just is the timeout the whole time that was the issue. Unbinned it takes 14 seconds to transfer the image with the original chunk size. The timeout was 10s. I will make a pull request to increase the BULK_DATA_TIMEOUT to 20s.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 7 months ago

On my drive home I was thinking, maybe it isn't about chunk since, maybe this older model is just slower and needs a much much longer timeout. Next time I'll try increasing BULK_DATA_TIMEOUT.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 7 months ago

Thank you for the help so far. I've had some success but lets see if I can explain it. In sxccd.cpp I change the resolution but that did not solve the issue. I thought maybe I get a timeout in the read because it is trying to still get too much pixels, so I wanted to see which pixel would it timeout on. So I modified the size of each fetch of data and added that info to the debug log. What I discovered is that pretty much any resolution can work. If it is bigger than the actual size, the data will just be zero for those pixels. What was causing the problem is the chunk size in the usb read.

By default it tries to get all the data in one read. I've found that I can't reliable get the image data if the read chunk size is too big. The size that works for me is pretty darn small actually and I'd assume makes transfers take longer than it normally would (A guess).

1024 I still get time outs toward the end. The value I've been able to reliably use is 512. It also seems like values that are not a power of 2 cause a LIBUSB_ERROR_OVERFLOW. In any case, I'm really happy we've gotten this to work. I'm not sure how many of these older cameras are out there, so not sure if it is worth a patch or a config parameter where you can specify smaller chunk size or something. What do you guys think? Should I also post this as a git issue?

Just in case I also tried commenting out the debug statement in case it was a timing issue, but 512 still works with the debug statement commented out. And size 512 with that debug statement is a lot of statements!

Below is my diff:

diff --git a/indi-sx/sxccdusb.cpp b/indi-sx/sxccdusb.cpp
index 8f08b78..4f89b64 100644
--- a/indi-sx/sxccdusb.cpp
+++ b/indi-sx/sxccdusb.cpp
@@ -736,11 +736,12 @@ int sxReadPixels(HANDLE sxHandle, void *pixels, unsigned long count)
     while (read < count && rc >= 0)
     {
         int size = count - read;
+        size=512;
         if (size > CHUNK_SIZE)
             size = CHUNK_SIZE;
         rc = libusb_bulk_transfer(sxHandle, BULK_IN, (unsigned char *)pixels + read, size, &transferred,
                                   BULK_DATA_TIMEOUT);
-        DEBUG(log(true, "sxReadPixels: libusb_control_transfer -> %s\n", rc < 0 ? libusb_error_name(rc) : "OK"));
+        DEBUG(log(true, "sxReadPixels: libusb_control_transfer -> %s, %lu/%lu t%lu\n", rc < 0 ? libusb_error_name(rc) : "OK", read, count, transferred));
         if (transferred >= 0)
         {
             read += transferred;


Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 8 months ago

I agree. If I was using a SXVR I bet there would be no problem.

Yes the PID it shows is 0x325 which I think is the same as the SXVR according to here:
www.sxccd.com/80-support

lsusb with the SXV-M25C
===============================================================
Bus 001 Device 005: ID 1278:0325 Starlight Xpress SXV-M25C
===============================================================

Interesting that in the linux usbids file PID 0325 is the SXV-M25C not SXVR-M25C. I guess because it was first.

Looks like maybe my next step will be to try to get my own build going and understand the driver more.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 8 months ago

Yeah. I'm not sure what all is the difference between the two cameras but I guess they are slightly incompatible. That would be easy if it is just width and height issue. Can maybe just add a overwrite flag that one can toggle. If I can figure out how to make indi use my own build of the sx driver I could try it. It would be a lot easier if I can take the camera home. The club really didn't want anyone leaving the observatory with it, but maybe I can ask for an exception to play with it for a week during next full moon.

Read More...

Russell Valentine replied to the topic 'Failure to take exposure with Starlight SXVR-M25C' in the forum. 8 months ago

On windows with the Starlight software says the resolution of the camera is 3000x2000, however the fits images it saves are 3040x2024

  • 3000x2000 - Nope
  • 3032x2016 - Nope
  • 3046x2016 - Nope, does not let me says it is out of bounds.
  • 3040x2024 - Nope, does not let me says it is out of bounds.

sx_ccd_test output:
sx_ccd_test version 1.13

sxList: 'SXVR-M25C' #1 [0x1278, 0x325] found
sxList() -> 1

testing SXVR-M25C -----------------------------------

sxOpen: libusb_open -> OK
sxOpen: libusb_get_config_descriptor -> OK
sxOpen: libusb_claim_interface(1) -> OK
sxOpen() -> 1

sxGetCameraModel: libusb_control_transfer -> OK
sxGetCameraModel: libusb_control_transfer -> OK
sxGetCameraModel: NON-INTERLACED MONO model 25
sxGetCameraModel() -> 89

sxGetCameraParams: libusb_control_transfer -> OK
sxGetCameraParams: libusb_control_transfer -> OK
sxGetCameraParams: chip size: 3000 x 2000 x 16, pixel size: 7.80 x 7.80, matrix type: fff
sxGetCameraParams: capabilities: STAR2K
sxGetCameraParams: serial ports: 2
sxGetCameraParams(..., 0,...) -> 1

sxSetTimer: libusb_control_transfer -> OK
sxSetTimer(900) -> 1

sxGetTimer: libusb_control_transfer -> OK
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer() -> 900

sxGetTimer: libusb_control_transfer -> OK
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer() -> 0

sxClearPixels: libusb_control_transfer -> OK
sxClearPixels(..., 0) -> 1

sxLatchPixels: libusb_control_transfer -> OK
sxLatchPixels(..., 0, ...) -> 1

sxReadPixels: libusb_control_transfer -> OK
sxReadPixels() -> 1

1787 1795 1819 1834 1802 1788 1833 1798 1822 1799 
1815 1805 1787 1829 1802 1821 1811 1795 1810 1849 
1829 1789 1855 1813 1829 1807 1795 1827 1831 1823 
1837 1810 1819 1823 1819 1808 1815 1790 1841 1807 
1793 1807 1832 1811 1797 1839 1818 1813 1821 1810 
1812 1821 1843 1791 1825 1831 1850 1830 1817 1819 
1841 1826 1817 1818 1807 1795 1829 1830 1803 1819 
1789 1791 1795 1807 1835 1838 1801 1811 1828 1815 
1820 1819 1831 1823 1815 1817 1807 1790 1787 1797 
1815 1808 1838 1791 1795 1789 1827 1806 1803 1779 

sxClose: libusb_close
sxClose() 


Read More...