Known Issue with readying Sopix sensors simultaneously on multiple PCs (XrayVision 4/Server based DCV only)

When a sensor is ready on one PC and you ready a different Sopix sensor on a second PC, the first sensor capture shuts down. This is because there is one INI file that all the sensors access in the network share of the software. When a sensor readied, it holds an exclusive lock on that file.

As of 1/11/17, we are still waiting on a potential fix from Acteon. The only way to work around this currently is to put local installations of Apteryx on the capture workstations. (You might try setting up multiple "Acteon" folders within the shared install folder, and pointing each workstation's SED options path to a different folder. To my knowledge this has not been tried yet. Refer to Feature 3324 for more info)

As of 4/6/17, updating SED to version 10.0 Build 1 (from our website) and updating Sopix2 drivers to current versions should fix this issue.

Using Original SopixII Direct Extension with newer (2nd generation) Sopix2 sensors

Acteon has released a new TWAIN driver called “Acteon Universal TWAIN,” which our direct extension for XVCapture is able to call. This means if installed, utilizing CCB TWAIN or TWAIN only can be avoided completely, as it allows us to use our existing direct extension. This provides much more consistent image capture results when compared to CCB TWAIN.

Integration steps:

“Acteon Universal TWAIN” is installed - can confirm it is installed by checking TWAIN sources through i-view/twacker_32 for “Acteon Universal TWAIN,” or by navigating to C:\Windows\twain_32 and checking if a folder called Acteon Universal TWAIN exists. If it is not installed, direct client to reach out to Acteon to get this installed.
Once confirmed to be installed, install SopixII direct extension as usual
When readying the sensor, the following interface should appear. Image capture will function in the same way old sensors and drivers did.

Incorrect image orientation (old drivers/interface, 1st gen Sopix2 sensors only)

The orientation of images taken with a Sopix sensor is controlled by the Sopix driver interface itself, rather than our post-capture filters. By default, the sensor position is set to up, as seen in the below screenshot. If all images are coming out upside-down in XVCapture, change this sensor position to down (you can click on the position inside of the driver interface), and leave it at that position regardless of which side of the mouth images are being captured on. In most cases, setting it to “Down” and leaving it on that setting will resolve orientation issues.

Incorrect image orientation (new drivers/interface, 2nd gen Sopix2 sensors only

While the newer interface has a sensor position GUI as well, and changing the sensor to “down” resolves the issue per-image, it no longer remembers this setting which causes the user to have to set the sensor to “down” manually per image.

To resolve:

Leave sensor position in the interface on “Up”
Integrate the sensor using the SopixII Direct Extension instead of CCB TWAIN (see https://planetdds.atlassian.net/wiki/spaces/DIKB/pages/3441295380/Sopix+2+Sensor#Using-Original-SopixII-Direct-Extension-with-newer-(2nd-generation)-Sopix2-sensors )
Apply a “Rotate 180 Degrees” filter to the SopixII extension’s PCFs

NOTE: If an office uses both gen 1 and gen 2 Sopix2 sensors, plug in a gen 1 sensor and ensure the sensor position is also set to “Up.” If set to “Down,” images taken with the older sensors will begin returning rotated 180 degrees.

Sopix Sensor Active image area (can be used for calibrations)

Header Size is incorrect

Navigate to the MAS2W driver installation folder

%programdata%\Apteryx\Sopix

Cut all files with "LAST" in name to a created folder (I used \backups)

NK: You may also need to cut the files out from C:\Users\Public\Documents\MAS2W, As this is the default path MAS2W writes images to. This was the resolution for ticket #48194.

FFC Header File - different image size

This error stems from the Acteon drivers, not our software. Acteon will need to resolve.

Unable to write in the data storage folder

Permissions issue - set permissions on C:\ProgramData\Apteryx to Everyone > Full control.

Image Quality

Sopix 2 MAS2W driver filters

Click the gear and set the filter to X2. This is like the Schick Filter or the Gendex Optimizer.

Sopix2 Sensor "Secret Menu" in MAS2W.exe

There is a hidden menu in the MAS2W.exe interface when configuring. If you Hold CTRL+Shift and hit OK in the options, it will display a hidden window allowing you to set additional options including darkening/brightening of images.

New Sopix2 Auto-firing

If images that were previously taken are randomly populating during subsequent image captures, this may be caused by permissions on the Acteon folder located in XVCapture’s root directory. Giving everyone full control of that folder should resolve the issue.

New Sopix2 sensors not working/not consistent within CCB TWAIN extension

NOTE: Solution appears to be hit or miss, possibly not working with the newest version of their drivers but this has yet to be fully determined. Steps can still be attempted as they may work, but is not guaranteed.

Download the AXAM folder from the Apteryx CX - Customer Support Files page in Teams
Copy the AXAM folder to C:\Windows\Twain_32 on the client’s workstation
Navigate to C:\Windows\Twain_32\AXAM and run Drivers SOPIX-SOPIX2 Series.exe
Install CCB TWAIN as normal, point filepath in CCB TWAIN’s extension settings to C:\Apteryx\XVCapture\Apteryx.plugins.bridge
Run a test capture sequence
- if images auto-populate, launch the same TWAIN via Twacker or other TWAIN test tool and allow all “queued” images to auto-populate to clear the folder they’re coming from
If successful, repeat above steps on any workstations needed

Newer Driver UI: