I got your code cloned and built.  I am trying to shoot some recognizable images with it but since it is mid-day here I need to do short exposures to avoid maxing out the pixel counts.  This means that the issue with short exposures that I mentioned before is rearing its ugly head.  I will try to get some properly exposed subframed and 2x2 binned images and/or captures tonight and let you know how that part of the code is working.  In the meantime though here is a packet capture of the problematic 0.25 second exposures.  I took a first exposure, which seemed to download just fine, then waited a few seconds and tried a second one.  The second one downloaded but it paused for a really long time during the download. Hopefully this capture has what you need to figure out why this is happening.  In any case though I will investigate the subframing/binning code tonight when it is a bit darker.

I pushed another branch called bin_no_deinterlace. This has the same changes as the other branch and an additional change to not deinterlace the frame if y-binning is enabled. I think this will work better, but I it would be nice if you could test both and find out for sure.

I Ben, I copied this file from the web repository into the above folder and everything seems to be working now. Great !

After an extended break from the G3 (a new ASI camera and not a lot of astro photography) I worked through the build of the indi-orion-ssg3 driver tonight and took a couple of test shots.
Not connected to a scope (it's raining here so that would not have helped much).

Very big thanks to those who stuck with this and got it working.

Looking forward to trying it on the sky sometime soon and see what it does..

hmm, strage. Yeah I did double check that I pushed it. If you do a "git log" the most recent commit should be "fix half-frame download issue". get-vidmateapp.com mobdro download

The driver is available in the standard indi release, so you shouldn't have to build it. I'm using Jasem's PPA and can install it by doing "apt-get install indi-orion-ssg3".

-Ben

Some notes which may relate to the earlier permission issue.
I went to setup the Camera driver on my primary control Raspberry Pi (trying to get two setups built) and of course didn't check back here first (Duh!).

I updated my 3rdparty repository and built from source then after hitting permission issues saw the comment that the package could be installed directly and tried that in the hope it would fix issues.
Permission issues still remained.

I found that I have several copies of the 99-orionssg3.rules file.
/etc/udev/rules.d/99-orionssg3.rules
/lib/udev/rules.d/99-orionssg3.rules
/home/astroberry/Projects/indi-3rdparty/indi-orion-ssg3/99-orionssg3.rules
I'm assuming run time issues would be in one of the first two and the repository one is just source for my build.

The copy under /etc Had an idVendor of 0722 and some specifics for the G3. The other two are generic for all Orion Camera with an idVendor 07ee. I've edited the /etc copy and added the general rule as well as changing the idVendor and am through the basics successfully.
The /lib and repository copies look like this
# All Orion Cameras
SUBSYSTEMS=="usb", ATTR{idVendor}=="07ee", MODE="0666"

The /etc copy was
ACTION=="add", ATTR{idVendor}=="156c", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"

SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0722", ATTR{idProduct}=="0502", MODE="0666", SYMLINK+="orionssg3.%n"

It's now
ACTION=="add", ATTR{idVendor}=="156c", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"

SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="07ee", ATTR{idProduct}=="0502", MODE="0666", SYMLINK+="orionssg3.%n"

# All Orion Cameras
SUBSYSTEMS=="usb", ATTR{idVendor}=="07ee", MODE="0666"

From lsusb
Bus 001 Device 007: ID 07ee:0502 Torex Retail (formerly Logware)

I've taken a couple of basic sitting on the desk shots to confirm something happens. Hoping to give this thing some work this weekend.

Changing usbfs_memory_mb should be not done by 3rd party udev rules, it's been moved to INDI, so this line can be removed. The other line is just to create symlinks, but why is this important? is this used in the driver? the line that matters is the last one, which is what is used in the INDI repo now.

Thanks Jasem. I've removed the usbfs entry.