Setting a CK65 back to factory default

Here’s the procedure to set a CK65 back to the initial shipping from factory state.

Restart the CK65 by holding down the power button and selecting Restart from the pop up menu.

When the Honeywell splash screen appears, press and hold the green button and hold down the power button. Release these keys when the Restart Boot Loader screen appears.

Press the green button until the Full Factory Reset screen appears, then press the power button.

The CK65 will erase all data and do a Factory Reset.

Honeywell CK65 RF settings

Any RF settings other than the typical set up of SSID and security are not so easy to find on the CK65. Here are two configuration locations for Android 10:

Go to Settings, Network & Internet, and tap on the SSID you are currently using. A sprocket icon will appear to the right of your network name, tap on it. Now tap on the pencil icon at the top of the screen. You’ll be prompted to enter the password and the SIP keyboard will pop up. Minimize the SIP keyboard and you’ll be able to scroll down and change from DHCP to a static IP number.  If these are not visible, tap on Advanced Options. Restart the CK65 after you’ve switched from DHCP to Static, or vice versa.

To get to the Honeywell Proprietary RF settings go to Settings, Location, Wi-Fi and Bluetooth scanning, and turn W-Fi scanning off. Next, go to Settings, Network & Internet, and toggle off  the Wi-Fi switch to the right of your SSID name. Tap on Wi-Fi (which should now be off) then Wi-Fi preferences, Advanced, scroll down and tap on Honeywell Proprietary Settings. You can now modify these settings as needed.

CK65 Enter Key does not work in Honeywell Launcher

When you start Honeywell’s Launcher application it automatically changes the pop up keyboard type (SIP) to the Honeywell Enhanced keyboard and it disables all other keyboard choices.

If you start Chrome within Launcher you’ll notice that the Enter key on the CK65’s physical keyboard doesn’t work. You can enable Gboard when you’re in Chrome which fixes the issue but it will occur again when the CK65 reboots or Launcher is restarted.

To get around this you have to modify the Launcher XML configuration file. To do this, click on the three vertical dots on the top right corner of Launcher and select Export Configuration.

Exit Launcher and turn on Provisioning Mode within Honeywell settings then put the CK65 in a dock connected to a PC with a USB cable. Enable File Transfer by swiping down from the top of the screen.  Scroll down the notification list and  tap on the last item on the list to enable File Transfer. On your PC you should see a file named Honeywell Launcher.xml in the Honeywell folder on the CK65.

Copy this file to your desktop and use Notepad to edit this entry:

<Key name=”key_gboard_mode” desc=”Keep Gboard option in Soft keyboard” flags=”16″>false</Key>

Change the value from “false” to “true” then copy the XML file back to the CK65’s folder \honeywell\persist.

Reboot the CK65 and start Launcher. You will now see Gboard as an available SIP choice. Enable it the enter key will begin working. Android will remember your keyboard choice so this change will persist through reboots.

Configuring a Honeywell Xenon Scanner to be GS1 compliant

If the following data is encoded in a 128 symbol

{Start C}{Function 1} ]1710091510123456789012{Function 1}2002

where the first Function 1 after the Start C symbol indicates it’s a GS1 bar code and the second Function 1 is a delimeter after a variable length field. When a scanner reads this symbol it should output:

]C11710091510123456789012<GS>2002

Note the output starts with a [C1 indicating a Code 128 GS1 symbol and the second Function 1 code gets translated to an ASCII Group Separator character <GS>, or Hex 1D

The Xenon does not do this by default, but if you scan these two configuration labels, it will behave per the GS1 spec:

 

 

FTP difference between older PX4 and new PX4ie

Older PX 4 printers allowed an FTP connection as an unknown user with no password. You could then copy files to the printer’s c: drive. You can’t do this with the PX4ie. To demonstrate this I started a command prompt from Windows and connected to an older PX4:

C:\Users\Sybil\Desktop>ftp 192.168.0.28
Connected to 192.168.0.28.
220 EasyCoder FTP Server v.1970 ready.
500 Sorry, no such command.
User (192.168.0.28:(none)): INTERMEC
230 User logged in (no password).
ftp> put lbl.txt MYLABEL.TXT
200 PORT command OK.
150 Opening ASCII mode data connection for ‘MYLABEL.TXT’
226 Transfer complete.
ftp: 34 bytes sent in 0.20Seconds 0.17Kbytes/sec.
ftp>

Note that the printer let us sign in as the user INTERMEC with no password. The put command copied lbl.txt to the printer’s c:  drive as MYLABEL.TXT.

You can’t do this with the PX4ie. The security has been changed to prevent unknown users from connecting via FTP to the printer. The file structure has changed in the new printer;  the c: drive has been mapped to /home/user on the PX4ie.

To accomplish the same task with the new printer you’ll need to provide a user name and password and specify the destination folder. So now this FTP command sequence becomes:

C:\Users\Sybil\Desktop>ftp 192.168.0.77
Connected to 192.168.0.77.
220 Welcome to Honeywell Printer PX4ie  14321961033
200 Always in UTF8 mode.
User (192.168.0.77:(none)): admin
331 Please specify the password.
Password: pass (hidden)
230 Login successful.
ftp> put lbl.txt /c/MYLABEL.TXT
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 Transfer complete.
ftp: 34 bytes sent in 0.00Seconds 17.00Kbytes/sec.
ftp>

These new commands are compatible with the older PX4 printers, so with this small change to your FTP commands will work with both printers.

Note: If you omit the /c/ folder destination in the put command, the file MYLABEL.TXT will be copied to  the /home/user/admin folder.

Update

I discovered that you can log into the PX4ie as “user” (lower case) without a password and the printer will allow you access to the /home/user (i.e. c: drive) folder.  So, in the first example above, substitute “user” for “INTERMEC” and the new PX4ie behaves the same as the older printers.

PX940V Can’t calibrate verifier

If you cannot calibrate the PX940V’s verifier, try this.

Most times this failure is due to dirt on the glass over the verifier,  often not visible. To confirm this is the issue, print a test label and connect to the printer’s web page and look at the verifier’s image under Verification, Verifier Image. You’ll probably see something like this:

The vertical black lines aren’t on the label, it’s dirt on the verifier glass.

Open the front verifer arm.

Clean the glass with isopropyl alcohol and Q-Tips, or an alcohol wipe. Repeat until there are no lines on the verifier image, then try to calibrate the verifier again.

Note the row of label sensors next to the verifier.

Installing a PC4ie dual serial board

There is a new dual serial I/O board for the updated Honeywell PX4 industrial printer, the PX4ie. The part number is 50147018-001 and it is currently shipping. Unlike the old board, which was dual RS232 out of the box, you need to install two jumpers and two IC (integrated circuit) chips into the board.

You are working with static sensitive devices here, so make sure you ground yourself before touching the board or ICs.

For UART A the jumper connects the two pins on the right of P4 and the IC gets installed in the socket pictured here. Notice the semi circle on the bottom of the chip (it’s clearer on the next picture), it lines up with the semi circle on the board:

UART B installs the same way:

Again, note the semi circle cut out at the bottom of the IC. This time the jumper is installed at P8. Make sure that you don’t bend any of the pins on the IC when you  insert it into the socket.

The rest of the installation is described in the Honeywell installation manual. Click on the documents tab to get this manual.

 

Honeywell PX4ie, IPL, and Loftware

IPL in the PX4ie printer is now a Fingerprint program, that is, it receives an IPL data stream and converts it to Direct Protocol before printing a label. Some of the older IPL configuration commands are not supported. Loftware is famous for sending down a lots of these commands with their label data and some of these can cause problems with the PX4ie.

The way to get around this is to turn on the ignore commands feature in the printer.

Browse to the printer’s IP address and click on Configure on the left side of the screen.

Next, click on Languages and enter “itadmin” and “pass” for the user name and password and press the login button.  Click on Languages again, then IPL.

The second to last selection from the bottom is the Commands Ignore. Enable this, save it, reboot the printer and try your Loftware label again, it should now print.

 

Symbology identifiers

You can enable symbology identifiers in most scanners. For example, if you enable the GS1 Code 128 identifier and scan a Code 128 symbol that encodes F1 0123456, where F1 is a 128 function 1 code, the scanner will output “]C10123456”. The left square bracket precedes the symbology type, the letter indicates the symbology, and the number after the letter is the specific parameter for that code.

These identifiers are used by programs to ensure that he correct symbology and type is being used. A quick listing of the important codes and modifiers:

A     Code 39

0 = No check digit
1 = Check digit, transmitted
3 = Check digit, not transmitted
4 = Full ASCII, no check digit
5 = Full ASCII, check digit transmitted
7 = Full ASCII, check digit not transmitted

C     Code 128

0 = Standard Code 128
1 = GS1 Code, Function 1 in the first position
2 = Function 1 in second position
4 = Concatenated according to ISBT rules

d     Datamatrix

0 = ECC 0 – 140
2 = ECC 200, Function 1 in position 1 or 5
3 = ECC 200, Function 1 is position 2 or 6
4 = ECC 200, Extended Channel Interpretations implemented
5 = ECC 200, Function 1 in position 1 or 5, ECI implemented
6 = ECC 200, Function 1 in position 2 or 6, ECI implemented

E UPC

0 = Standard code, except for EAN-8
1 = Two digit supplemental code
2 = Five digit supplemental code
3 = Combined UPC and supplemental code
4 = EAN-8

 

Upgrading a Honeywell CK75 Android version

First, download the operating system files, either GMS (Google Mobile Services) or Non-GMS from Honeywell’s FTP site. You’ll need to sign up for an account if you are not registered.

Navigate to Software, Computer Devices, Handheld, CK75 CN75 CN75e, Android 6, Current, Device Image, GMS (or Non-GMS). Download the file that has an “sd” in the  file name. You’ll need Honeywell’s Download Manager; there’s a link to it on the FTP page.

Unzip the files into a temporary folder. Insert a micro SD card into your PC and format it as FAT32. Copy the entire contents of the unzipped folder onto the root of the SD card. Power down the CK75 and open the back cover above he battery, there are three screws holding it down. Insert the micro SD card into the slot; refer to the manual if you need help with this.

Replace the cover, turn on the CK75 and place it into a powered dock. The files on the SD card will be detected on boot up, a Honeywell logo will display,  and after 8 minutes or so an animation appears on screen:

In another 4 minutes the CK75 will reboot to a Honeywell screen. In another 3 to 4 minutes the Android Welcome screen will appear and walk you through the initial set up. When this is done, power off the CK75 and remove the SD card.

Next, navigate to the same folder on Honeywell’s FTP server, but instead of GMS or Non-GMS select the CommonES folder and download the .zip file. This file contains updates to the Honeywell programs on the CK75. Connect the CK75 to your PC (refer to the manual if you don’t know how to do this) and copy the downloaded .zip file (don’t expand it) to IPSM\honeywell\autoinstall folder. You may have to create this last folder yourself.

Go to the main apps page on the CK75 and select AutoInstall. Make sure that AutoInstall is enabled, then click on “Packages upgrade”. You’ll see the various programs being updated. When complete, delete the .zip file from the \IPSM\honeywell\autoinstall folder. The package updater does not clean this up automatically and the upgrade will install on each boot unless you manually delete this file.