SBAM1991 DV5950 LINUX M24 V4.2.0and4.2.0.p3
SBAM1991 DV5950 LINUX M24 V4.2.0and4.2.0.p3
2022-02-23
Important:
When doing the procedures in this document, you must use safe work practices and wear the correct
personal protective equipment (for example, safety eyewear) according to your company's standard
operating procedures.
All procedures in this bulletin should be followed exactly as stated. FAILURE TO FOLLOW THE PROCEDURES
MAY CAUSE THE MACHINE NOT TO WORK AND RE-IMAGING TO A PREVIOUS SOFTWARE VERSION IS NOT
POSSIBLE.
Announcement:
This bulletin announces the availability of M24 - Linux Software Version 4.2.0 and 4.2.0.p3 patch for
the DRYVIEW 5950 Laser Imager and TRIMAX TX55 Laser Imager. 4.2.0 is a new/full release that is
based on Ubuntu 20.04. Further info about patch p3 below.
Note:
The software is for systems with LINUX compatible DREs only. Refer to document SBAG2912 –
Announcing 5950 Imager on LINUX Operating System, available on the Service Portal for more
information.
Note:
Please refer to DryView 5950 Adjustments and Replacements Publication No. AA2206_en about how to
remove the Top Cover / Right Cover to have access to the MCS in order to identify which chip is installed.
Prerequisites:
Ensure that any pending print cycles have completed.
Power Off the imager, and then disconnect the power cord.
How to identify the new FPGA Chip on the MCS P/N AG0510 Rev. F and above
In order to determine if on the MCS you received from stock is installed the new FPGA chip , compare the
pictures below with the chip S/N :
• NEW FPGA, CYCLONE IV, has S/N EP4CE6E22C8N
• OLD FPGA chip has S/N EP4CE6E22C7N
Important:
If you upgrade the microcontrollers’s firmware BEFORE installing software v4.2.0.p3 , the MCS board will
likely be unusable and no longer upgradeable . In general, the new MCS boards should NOT be downgraded
to fit current software (rather, software should be updated to resolve a 20156 instead ).
Furthermore, all new MCS boards with Cyclone IV new package layout will be shipped from the factory with
the 1.5.0 MCS firmware pre-programmed.
Important:
DV5950 v4.2.0 production software must be already installed on the target imager BEFORE installing
patch p3. If not, then first upgrade your printer to v4.2.0 using the version release and instructions below.
DV5950 software patch 4.2.0.p3 must be installed to support new FPGA Chip AL8839 present on the MCS P/N
AG0510 Rev. F and above.
Software version 4.2.0 is installed on production units effective with these serial numbers:
Note:
V4.2.0.P3 Linux OS released on DV5950 production from Feb. 26th, 2022
• FAILED VERIF - one open association was not dropped during performance load printing test
• DICOM Siemens OEM test issue - Tux returns an Abort when sent unsupported SOP Class.
Windows returned Rejected.
• Enhancement - New DCF support needed for V5 film (DVE, DVB+, DVM+).
• Service Tool Language Not Always English
• EC919 from QA test of 4.1.3 release (intermittent, single occurrence - problem acquiring the
shared image buffer)
• Enhancement - Display installed OS security patch info on VersionInfo page of Web Portal /
Service Tool
• Remove Ignored file from 5950 baseOS - "Ignored" File in View Logs by File "Ignored" File in View
Logs by File
• Escalation - Argentina TT site EC935 - This failure was due to an MCS threading, locking, timing
and clean up issue of an internal Timer. The handling was not correct and the Timer was
attempted to delete more than once – causing a crash. The threading/lock usage has been
corrected.
• 5950 K2 Kiosk intermittent DICOM failure. GuangMing - Risk 2 - possible DICOM issue. Modality
console showed imager not available.)
• When DICOM SCU sends illegal ConfigInfo value - Tux does not handle it gracefully (Canon CT, GE
OPTIMA XR240 DR)
• Enhancement - Suggest to reenable rollback check and fully home - even if no film cartridge in the
tray
• Enhancement - Provide ability to enable/disable packet capture (tcpdump .cap file creation) and
download the resulting file using ST (L4/L5)
• Linux5950 - 2 issues: 1) printing out blank film, 2) after reboot always prompt EC935
• 8x10 Throughput Does Not Meet Requirement (114FPH instead of >120FPH)
• Enhancement - Improve patch handling to eliminate the issue where patch could be inadvertently
installed on system that is not the correct base release
• Enhancement - Train patches to properly update individual component version items, not the
complete Var_VersionInfo.xml file
• Brazil dealer - SecureLink connect fails - specific K-number, Serial-number configuration
• Ability to do OSIF.deb upgrade and auto-restart via ST application update mechanism (patch
release)
• Enhancement - SmartLink generic agent 1.5.2 (20.04 compatible build). Current Smartlink agent
releases do not integrate and work properly with 20.04. Also will include updates from 1.5.1.
• Enhancement - MAC address display in WP/ST for each network adaptor.
• Enhancement - Bring PageBuilder enhancements from 6950 that improve rendering (reduce
rendering load/times) into 5950
• DV5950 enhancement - Service requests to display empty cartridge instead of EC116 for planned
liner change
• Calibration can fail with crash due to very intermittent timing issue
• 5950TUX-PHILIPS DSA&Philips post-processing workstation can't send the print job to imager
(MaxPDUSize=0)
• Enhancement - From Field Issue - Allow ST to change default IP for Service0 LAN adaptor
Note:
This release also includes the fixes for the defects that were already in 4.1.3.p1, .p2, and .p5 items.
5950TUX- WDM DR (it used PZ medical ‘s DFP and system) can send print job to imager,but 5950 can't print
(Cambridge toolkit)
5950TUX-PERLOVE digital gastrointestinal diagnosis machine can't send the print job to imager (Cambridge
toolkit)
IRay modality fails to print. DICOM decode error. Resolved in field by IRay replacing a DLL and configuring as
Agfa5302 imager. (Cambridge toolkit)
Task99227 - 5950 Placeholder task to include fix for PZ Medical modalities (Cambridge DICOM toolkit). This
issue is already represented for 5950 in defects: 791, 792, 827
Also includes the following that were released in previous .p2 patch:
RabbitMQ crashed during startup after hard power off of 5950 during self-test.
Enhancement 5950 - Add a Scheduled Restart feature - optionally enabled via the Service Tool
5950 MFG - 1-time failure - H/W failure of RFTag block data reads causes MCS failure EC935 on startup.
Requires power-cycle.
5950 generating intermittent EC544 during extended throughput test. Configuration requires: new MCS
board/firmware, alternating 14x17 tray feed sequence.
5950 - Monitor service attempting to start DICOM.service when it should not - increasing auth.log size
And also includes the following that were released in previous .p1 patch:
20.04 issue - MCS Image memory buffer diagnostic intermittently indicates failure.
Enhancement - 5950 - FPGA firmware support for new Cyclone IV chip.
5950 MCT print can generate a film with a garbled or mixed-print image under certain conditions.
5950 Backup/Restore does not properly handle the FlipView parameter to/from the ReverseView setting.
Note:
Prior to v4.2.0.p1 the Reverse View (FlipView) parameter was not properly included in the backup file. So
if Reverse View is enabled on a prior version, install 4.2.0.p3 and then create a new backup file to use for
future restores. Further info about the “Reverse View” feature at the end of this document.
Important:
All procedures in this bulletin should be followed exactly as stated. FAILURE TO FOLLOW THE
PROCEDURES MAY CAUSE THE MACHINE NOT TO WORK AND RE-IMAGING TO A PREVIOUS SOFTWARE
VERSION MAY NOT BE POSSIBLE.
Note:
The estimated time to image the solid state drive with the software release, perform the installation
using the USB security key (KEYLOK), and restoring configuration parameters (e.g. network settings) for
the imager is approximately 30 minutes, including imager restart time.
Remember the following steps when you perform the software upgrade:
• Reinstalling the DRE software with the bootable USB drive
• Automatic configuration from the KEYLOK (VARInstaller)
• Microcontroller upgrade
• Restoring the configuration parameters from the backup file
• Enabling Remote Management Systems (RMS) if applicable
Note:
There are no KEYLOK changes for use of Software Version 4.2.0 As always, if the KEYLOK is being changed
to a different format, both the KEYLOK and software must be loaded at the same time.
Note:
MoBoMatch9088_Tux is included in the LINUX Bootable USB .zip package. After the bootable drive is
created, copy MoBoMatch9088_Tux to the drive.
1. Create a folder on your laptop and copy both the v4.2.0 (AJ9791_T) and v4.2.0.p3 (AM45
26_A) software files from the Service Portal to your laptop.
Note:
The MD5 file is a checksum file used to verify the data within the zip files were not corrupted during
download from the Service Portal. The MD5 code within the file is used in conjunction with a Viewer to
perform the software integrity check. Viewers such as WinMD5 can be downloaded for free from the
Internet.
2. Navigate to the folder created in step 1 and extract the contents of AJ9791_T_Linux_5950.7z ( 7
Zip>extract here ) . The folder below will be created :
5. Eject the newly created bootable USB drive from the service laptop.
6. Power cycle the DRYVIEW 5950. If the printer is already off, switch it on for a few minutes and
then power down.
Note:
Power-cycling the machine allows the current Managed Print Solutions (MPS) files to transfer to the RMS
Server. (This action is mandatory for MPS printers. If you have a non-MPS printer, you can skip this step –
power cycling is not required.)
7. Connect your service laptop to the printer via SecureLink and Service Tool (Web Link). Always use the
latest Secure Link Client and Web Link software versions on your laptop.
Note:
During software installation, the DRE will emit a beep every few seconds. When the procedure has
completed successfully, the beeps change to continuous medium-pitched beeps.
15. Power off the machine and remove the bootable USB drive.
16. Power on the imager and wait for the configuration process to complete. This could take up to 10
minutes.
17. When the Amber Power indicator is flashing. , automatic configuration from the KEYLOK
(VARInstaller) has started. You should hear periodic medium pitch beeps while the process
completes.
Note:
Code 935 will display after power-on and during VARInstaller operation. This is normal.
18. Once the the VARInstaller has completed, the imager will emit 3 high-frequency beeps, the 935
will disappear, and the imager will automatically restart.
Note:
If the 935 is still on the display after 15 minutes, wait 5 more minutes, and then power-cycle the machine
manually using the main switch. After the manual reboot, if 935 still appears on the display, something
failed in the VARInstaller installation. In that case, power off the machine and restart the software
installation procedure from step 11.
19. After a successful VARInstaller process, code 156 may display on Local Panel, indicating that the
ARM microcontroller firmware must be updated. If the release does not require an update of
ARM microcontroller firmware, skip to step 20
If in your MCS is installed the FORMER / OLD FPGA chip S/N EP4CE6E22C7N , proceed to next step i.e.
microcontroller firmware upgrade ( step 20 below ).
In the case of new NEW FPGA Chip AL8839 , CYCLONE IV, S/N EP4CE6E22C8N install the patch p3 , see
below “Patch Update” ( DO NOT UPGRADE the Micro’s firmware before installing the patch p3.)
Note:
Before moving on, check the file integrity, using md5 checksum number . Viewers such as WinMD5 can be
downloaded for free from the Internet to do it.
Installation sequence:
1. Ensure that the imager is already installed with 4.2.0 full release or prior .p1 or .p2 patch.
2. Connect to imager with SecureLink and ServiceTool.
3. Install the .7z update file via the Service Tool: Upgrade –> Application -> Manual tab
• Select the file (“AM4526_A_TuxMonoInstaller_4.2.0.p3_2022-01-26_1003.7z”) from your
location on client PC ( below as an example ).
• Upload the file and install it.
4. Imager automatically restarts after application upgrade completes. Wait for imager to come back up.
5. If the imager will have an EC156 error. (Both the FPGA and ARM micro have changed for the 4.2.0.p1
patch) see below “Microcontroller Firmware Upgrade” , otherwise skip steps 6 .
6. Connect with Service Tool and upgrade the micros ( see Microcontroller firmware upgrade below)
To upgrade the firmware for the microcontrollers, with your service laptop connected via Secure Link and
using the Service Tool (WebLink):
When micro update is complete, the system will automatically restart (code 705 shows on Local Panel).
c. Verify the Software v4.2.0.p3 Microcontroller versions. Click Menu > System
Identification > Version Information.
7. Confirm 4.2.0.p3 was successful going to System Information too > Version Information ( below as an
example ).
• OS:
• Xubuntu 20.04
• Base OS Image 43
• OSIF 2_29_210913
Note:
Before the restore process:
20. Restore the imager’s system configuration (Menu > Utilities > Backup / Restore), click the
Restore tab, then click the Restore button.
Note:
If the restore operation fails, click the Upload Configuration File checkbox, click the Select button,
navigate to the location where you saved the backup file uding the Download Backup option in Step 8,
click Open to select the backup file, then click the Restore button.
21. After the restore is complete, verify that the Network, System Identication, Clock, and DICOM SCP
settings are correct.
Important:
Only set the system clock to the actual date and time. Changing the date and time too far ahead or back in
will cause permanent adverse affects to the system.
If the customer will be using DVE film for the first time, change the configuration for the customer, or
ensure that they understand that it must be changed:
• Select Menu > Configuration > DICOM SCP > Film and Image Options tab and change the ‘Film Base’ to
BLUE FILM for any modality using DVE film.
• If the modality was using DVC (CLEAR FILM), this film will need to be printed before changing the Menu
> Configuration > DICOM SCP > Film and Image Options tab to BLUE FILM, otherwise it will no longer
print.
Note:
For LINUX operating systems, RMS is enabled using an application named Smart Link Deployment Utility. You
must install this application on your laptop using SmartLinkDeploymentUtility-setup.exe.
22. Download SmartLinkDeploymentUtility from the Service Portal.
23. Install SmartLinkDeploymentUtility-setup.exe on your laptop.
24. Double-click SmartLinkDeploymentUtility.exe located in the directory shown below:
26. Verify that Country Code and DeviceKNumber are correct and the SmartLinkServer is set to
Production.
Note:
If Country Code or DeviceKNumber are incorrect, update the System Information > Identification screen in
WebLink.
Note:
You can click the to verify the GAS Server connections are active to allow remote connectivity.
28. Restart the imager by selecting Menu > Utilities > Session > Restart.
29. To complete the RMS verification, confirm the remote connection of the printer on the RMS SmartLink
Portal (https://cs-rmsportal.carestreamhealth.com/Monitor/Monitor.aspx).
Note:
You must have an account to log in to the RMS / Smart Link Portal. If you do not have an account, call the IMT
Help Desk or COE to check if the imager has been correctly registered on the RMS Portal and that the
connection is established.
• Check that the drum temperature is correct and adjust / calibrate if necessary. Refer to the Service
Manual (9G3889) for detailed instructions.
• Print a test film to verify that the system performance and image quality are acceptable.
• Provide a quick training session to the customer on the new look of the Web Portal (enter the IP
address of the laser imager on the customer’s computer in a web browser such as INTERNET
EXPLORER, CHROME, FIREFOX, or EDGE.
A copy of the customer Web Portal Procedures guide can be downloaded from Menu >
Documentation.
Steps needed in the Service Tool to modify the MaxPDUSize value from the default to the value needed for
use by the modalities that utilize the Cambridge DICOM Toolkit:
a. Choose “Menu->Configuration->DICOM SCP->Communications”
d. Click “Save”
e. Restart the imager.
Note:
Do NOT use the range X.Y.Z.10 – X.Y.Z.30 as that range is reserved for the imager DHCP server
to hand out addresses to client that connects.
b. The new Service Port IP address will take effect almost immediately once you save it. If you
are connected via the Service Port you will be dropped and will need to acquire a new DHCP
address again on the client laptop.
c. Verify the new Service Port IP address and DHCP server: connect to the Service Port with
DHCP client laptop to verify that the new IP entered above is now the default and that the
DHCP address handed to the client should be in the range from X.Y.Z.10 – X.Y.Z.30.
Capture DICOM packets within WebLink ( in case of Dicom comm issue with SCU )
2. Steps needed to capture DICOM packets (eliminating the need to use Wireshark) within WebLink.
The DICOM Packet Capture feature is located in MenuUtilitiesDICOM Packet Capture
and the instructions for running the “Packet Capture” and downloading the datafile are
included on both tabs.
• Click “Save”
• The imager is now enabled to restart at the time and interval configured. A restart is not
required.
4. Network configuration snapshots ( for example how to read printer’s MAC Address , how to block
a modality IP address ( DICOM SCU )
Note:
“Reverse View” , specifies if the Film needs to be viewed with the Glossy (Emulsion) side facing Up.
Default is > No . Basically it re-orients the image when printed on the film so that the user can view it with
the emulsion out on a light box. This parameter will be recordered in the back up too now.
1. Use the Service Tool to record M24 in the Service History Log.
2. If this is the first installation of 4.2.0.p3 software, clear the call as M24.
3. Record the appropriate feedback:
Customer K-number SID Service Code Serial Activity Code Installation Part No.
Name Number Time
Bulletin History
Made in USA.