Releases: Scdouglas1999/Fujicom
Release list
Fujicom v3.0.1
Fujicom 3.0.1 is a bug-fix release for the 3.0.0 connection failure reported in #8 (Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')), seen in NINA with the X-T4 and X-H2S. It affects every supported body on 3.0.0, so all 3.0.0 users should update.
What was wrong
3.0.0 exposed both ASCOM gain modes at once: Gain returned the ISO value while Gains also returned the list of fixed ISO values. ICameraV3 allows only one mode to be active. NINA treats a populated Gains list as authoritative and reads Gains[Gain] → Gains[800], which threw inside NINA during connection. Earlier releases avoided this only because their XSDK_CapSensitivity call had the wrong native signature, failed, and left the list empty; correcting that in 3.0.0 exposed the problem.
Fixes
- The driver now uses a single ASCOM gain mode, Gain Value:
Gainis the ISO number,GainMin/GainMaxgive the range the body reports, andGainsthrowsPropertyNotImplementedException. FITSGAINremains the ISO value, as in 2.x. - Setting
Gainto a value inside the range but between the camera's fixed ISO steps now selects the nearest supported ISO instead of passing an unsupported value to the SDK. - Added core tests for the nearest-ISO mapping and a regression guard that the driver exposes exactly one gain mode.
Downloads
Fujicom.Setup.v3.0.1.exe— recommended Windows x64 installer; registers the ASCOM driver automatically.Fujicom-v3.0.1-runtime.zip— complete portable/runtime payload (x64 native wrapper, Fujifilm SDK runtime,XSDK.DAT, LibRaw, dependencies, all 18 configurations).Fujicom-v3.0.1-symbols.zip— managed and C++/CLI PDBs for troubleshooting.SHA256SUMS.txt— SHA-256 hashes for the three binaries above.
Validation
- 10/10 core driver regression checks passed.
- The managed ASCOM server and x64 C++/CLI
LibRawWrapper.dllcompiled successfully on Windows Server 2022. - All 18 camera configurations and required release payload files were verified.
- 25 Fujifilm XAPI exports, 7 LibRaw exports, and 5 native signature/constant contracts passed verification.
CI cannot emulate Fujifilm's USB camera protocol, so please confirm on your own body and reopen #8 if NINA still fails to connect.
Fujicom v3.0.0
Fujicom 3.0.0 is a major overhaul of the Fujifilm ASCOM camera driver, incorporating the camera-control and RAW-processing lessons developed in the NINA Fujifilm Native Plugin.
Highlights
- Rebuilt the exposure lifecycle for reliable timed, T-mode, and bulb captures.
- Added working
AbortExposureandStopExposure, with stale-frame cleanup and generation-safe polling. - Corrected the Fujifilm SDK sensitivity signature, RAW compression constants, release constants, and optional property calls.
- Filters Auto ISO and values outside ASCOM CameraV3's signed 16-bit gain range.
- Repeatedly polls for RAW readiness, recognizes rotated RAW codes, and skips JPEG/HEIF companion frames.
- Adds X-Trans-to-synthetic-RGGB compatibility conversion while preserving native GFX Bayer data.
- Crops Fuji/LibRaw optical-black columns so returned arrays match the advertised active dimensions.
- Reference-counts shared ASCOM client sessions and closes the hardware only after the final disconnect.
- Synchronizes and validates 18 X/GFX camera configurations, including GFX100 II, GFX100RF, GFX100S II, GFX50S II, and X-S10.
- Adds reproducible Linux and Windows CI, native DLL contract verification, and a source-controlled Inno Setup release build.
Downloads
Fujicom.Setup.v3.0.0.exe— recommended Windows x64 installer; registers the ASCOM driver automatically.Fujicom-v3.0.0-runtime.zip— complete portable/runtime payload, including the rebuilt x64 native wrapper, Fujifilm SDK runtime,XSDK.DAT, LibRaw, dependencies, and all 18 configurations.Fujicom-v3.0.0-symbols.zip— managed and C++/CLI PDBs for troubleshooting.SHA256SUMS.txt— SHA-256 hashes for all three downloadable binaries.
Validation
- 8/8 core driver regression checks passed.
- The managed ASCOM server and x64 C++/CLI
LibRawWrapper.dllcompiled successfully on Windows Server 2022. - All 18 camera configurations and required release payload files were verified.
- 25 Fujifilm XAPI exports, 7 LibRaw exports, and 5 high-risk native signature/constant contracts passed verification.
- The published installer, runtime archive, and symbols archive match
SHA256SUMS.txt.
Physical-camera validation is still recommended before unattended imaging, particularly with both one GFX Bayer body and one X-Trans body, because CI cannot emulate Fujifilm's proprietary USB camera protocol.
v2.3
Release v2.3: Includes missing X-S10 configuration files that were preventing that model from connecting.
v2.2
After some trial and error, I have compiled this new version which removes the possibility of the Camera Busy error appearing. Previously, if you left the camera alone for some period of time (usually a few minutes), the camera would go into a state which required a driver command to wake it up.
What this meant was if it went into this state and you went to take an exposure, you would receive a busy error and your exposure would fail. Now, the driver sees this error and simply waits a moment, taking the exposure just after the error gets thrown. You'll now not even see the Busy error appear, and your command will be executed by the driver, intelligently handling the error in the background.
The older v2.0 version will still function, but this Busy error may be thrown at times. Given the 2.2 error exhibits no instability I can see, I would recommend replacing your current version with this new one.
v2.0
This release introduces a new feature which will be supremely helpful to X-Trans sensor Fuji users.
Previously, X-Trans cameras would send raw sensor data to NINA, which would package the data as a FITS/XISF or whatever file type you choose. The issue is that this file does not contain any identifying information telling software how to deal with that very strange bayer pattern. What this would lead to is very strange colors that are simply debayered wrong, leading to unusable images. In order to solve this, Juan Conejero over at Pixinsight is currently coming up with a script to rewrite the XISF metadata in the NINA files so that Pixinsight sees them as x-trans correctly and debayers properly.
You may now realize, this is exclusive to Pixinsight users, which didn't sit right with me entirely, as much as I love Pixinsight, because many Fuji users may not have the money/experience/want to buy Pixinsight in order to take advantage of this. So, this new release incorporates a new checkbox in your ASCOM settings, shown below:
This new button labeled "Save .RAF to SD Card" will do exactly what it says, save a native Fuji raw file to your SD card. NINA will still get its file, allowing full NINA functionality to continue, but you'll get a set of native Fuji raw files to work with in processing just like any other DSLR user. Of course, the only catch is they're on the SD card, not your computer, but these are the limitations of the Fuji SDK and I cannot overcome them as far as I'm aware.
Please use this version if you wish to have Fuji RAF files saved to your camera in conjunction with the NINA functionality. Don't hesitate to contact me if you need help setting up the driver or if this release has any issues.
v1.0.2
Fixed a bug where the debug version of the dependencies for LibRawWrapper.dll were being copied into the exe bundle, causing the driver to fail every time. If you get an object reference error in NINA on image download, this is what's still causing it, but I think it's solved.
v1.0.1
Fixed some bugs with the exe installer. Some necessary files were found to not be transferring over properly, they should now.
v1.0 Initial Release
This is the initial release for the Fujifilm ASCOM driver. It is still very much in testing, but I feel it's stable enough to release a v1. Simply install the ASCOM platform and run the installer below and you should be good to go.
If you do get errors or even just experience some quirks, do let me know I can generally have things patched up quickly.
