On Windows 11 computers, the TSL RFID Reader does not appear in the list of pairable Bluetooth Devices.

Overview

Bluetooth classic is disabled by default on Windows 11 machines. If you use TSL 11xx or 21xx readers (or 31xx readers in Bluetooth classic mode) and these do not appear in the list of discoverable devices you may need to set ‘Bluetooth devices discovery’ to ‘Advanced’ within Windows 11’s Bluetooth settings.

This applies to the following TSL Bluetooth RFID readers:

• 1128
• 1153
• 1166
• 2128
• 2173
• 2128L
• 2128P
• 3166

Method:

1. Right-click on the Windows 11 logo in the taskbar & choose ‘Settings’
2. Click on ‘Bluetooth & devices’
3. Click on ‘View more devices’
4. Scroll down to the ‘Device settings’ area
5. Use the drop-down list to change ‘Bluetooth devices discovery’ from ‘Default’ to ‘Advanced’

Further Information

More in-depth instructions can be found here:

Enable or Disable Advanced Bluetooth Devices Discovery in Windows 11 Tutorial | Windows 11 Forum

The post TSL Reader Not Visible in Windows 11 Bluetooth® Devices Discovery List appeared first on Technology Solutions (UK) Ltd.

You will need to be using the TSL ASCII 2 Software Development Kit – for Android™ v2.5.0 or greater to add support for Android 12 (or greater) devices.

To support the (API31+) requirement of User permission checks, your app will need to issue a request for Bluetooth® permissions where appropriate. If this is not done, then Bluetooth® readers will NOT BE AVAILABLE – e.g. calls to ReaderManager.sharedInstance().updateList() will return an empty list.

The Android developer guide to requesting permissions is available here: 
https://developer.android.com/guide/topics/permissions/overview 

Run-Time Permissions Required

The new permissions to be requested are: 
Manifest.permission.BLUETOOTH_CONNECT
Manifest.permission.BLUETOOTH_SCAN
 
Note: Manifest declarations are still also required. The Rfid.AsciiProtocol-Library contains its own android_manifest.xml that will be merged with your project’s android_manifest.xml when your project is built. The library provides both the original Bluetooth® permissions for older devices along with the newer permissions shown above.

At an appropriate point in your application, ask the user for the above permissions. The permissions dialog will be provided by the OS and often refers to “nearby devices” rather than mentioning Bluetooth® specifically. You may want to warn your users that allowing this permission is required to connect to TSL® Readers via Bluetooth®.

When permissions have been granted, call ReaderManager.sharedInstance().updateList() to ensure the reader list is up to date. The Android SDK’s sample projects have all been updated with examples of how this can be done – there are slight differences in implementation details due to the differing UIs, but the code is mostly identical.

The Sample code implementation asks for permission in the onStart() lifecycle method of the apps Activity, but you may find a better place in your own apps if use of the TSL Reader is not . 
 

 
The implementation of the checkForBluetoothPermission() method can be found at the end of the sample project’s Activity source file.

By following the above advice, owners of the latest Android devices can continue to enjoy using your RFID App with their TSL® RFID Reader. 

The post TSL ASCII 2 SDK for Android™ – Supporting Devices Running Android 12 or Greater appeared first on Technology Solutions (UK) Ltd.

If you wish to publish an App to the iTunes App Store (or the B2B store) that supports a TSL iOS-Compatible device then Technology Solutions (UK) Ltd will need to obtain approval for your app against the appropriate hardware in the MFi program.

If you fail to complete this step:

If you have missed the statements within our SDKs (and on ASCIIProtocol.com) and do not send us the information listed below, then you will likely receive an App store rejection email from Apple similar to below:

“We are unable to post your app to the App Store at this time because your app has not been authorized by the accessory manufacturer to work with the MFi accessory:

com.uk.tsl.rfid

To resolve this issue, please contact the accessory manufacturer to request your app be added to the MFi Product Plan form.”

We require the following information:

1. The TSL devices your App will support
2. The name of the App as it will appear in the App Store – ensure that hyphenation, white space and spelling match the store name exactly
3. The App version number
4. Indicate if this is an update to an existing App or a new App
5. Indicate whether the App can be used independently of the TSL Device(s)
6. The App bundle Id
7. All External Accessory Protocols your App supports (ensure ‘com.uk.tsl.rfid’ is included)
8. A functional description of your application
9. The App Category
10. The name of the developer that will submit the app to the App Store

Please send all of the above information to support@tsl.com. We will submit the above details exactly as provided. Be aware that your App will be rejected by the App Store review process if the App details that you provide to us are incorrect.

Further information

• If you have separate Apps for iPhone and iPad then please submit a separate set of details for each App.
• When the App has received MFi approval we will supply you with the appropriate Product Plan ID (PPID) numbers to include in your App Store submission.
• When submitting your App to the App Store it is essential that you include the PPID numbers in the Review Notes section of your submission.
• If you need any further information contact support@tsl.com.

We can’t wait to see your great Apps!

The Developer Support Team

The post How to Submit an App Supporting TSL iOS Compatible Devices to the App Store appeared first on Technology Solutions (UK) Ltd.

Command Breakdown:

Basic operation is available to all the TSL Apps without configuration however, if modified scanner settings are required, follow the steps below to create a custom profile for the App.

Note: the Apps are not affected by changes to the “Default” profile.

Creating a Custom Profile

Using custom profiles allows each App to be configured independently. The steps below show how to create a custom Barcode Scanner profile for use with a TSL App:

1. Open the Settings App (usually a green icon with a white gear/cog)

2. Tap the Honeywell Settings row, typically, this is towards the bottom of the list.

3. Tap on the Scanning settings row

4. Tap on the Internal Scanner row this reveals the profile list.

5. Tap the (+) to create a new profile

6. In the Add Profile dialog, choose the Select an Application option

7. In the list that appears, select the TSL application you are using in this example we configure TSL Tag Finder, this will create a new profile.

8. Tap on the newly created profile to edit it and modify its configuration in this example, we will modify the Check Digit option of the UPC-A symbology

9. Tap the Symbology Settings row

10. Tap the UPC-A row

11. Ensure the Send Check Digit option is enabled

12. Use the terminal’s Return button to go back – make any additional changes required.

13. The terminal is now ready for use with TSL Apps!

Note: RFID Scan Scan Write and RFID Tag Finder require that scanned barcodes include the Check digits – this may require modifying several symbology settings e.g. UPC-A, EAN-13, etc…

The post Configuring the Barcode Scanners on Honeywell Terminals To Work With TSL® Mobile Apps appeared first on Technology Solutions (UK) Ltd.

Enabling the Intent Wedge

The terminal’s barcode scanner needs to be configured to issue an Android Intent message for each scanned barcode. The instructions below show how to enable this feature.

1. Open the Settings App (usually a green icon with a white gear/cog).

2. Tap the System row, typically, this is towards the bottom of the list.

3. Tap on the Scanner settings row

4. Tap on the Wedge row – this reveals all the Wedge options.

5. Find the section marked Intent Wedge.

6. Ensure that the Enable intent wedge checkbox is ticked/on.

7. All other values are used at their default setting so no further action should be necessary, however, to confirm this, verify that the other settings are as shown below:

8. The terminal is now ready for use with TSL Apps!

Additional Configuration for RFID Scan Scan Write and RFID Tag Finder

By default, Datalogic terminals will append a linefeed character to all scanned barcodes and many symbologies are not configured to send a checksum digit – these may cause problems for RFID Scan Scan Write/RFID Tag Finder  and the remedies are described below.

Removing the Unwanted Linefeed Character

This option is controlled in the Scanner Settings Formatting section:

1. Navigate to Scanner Settings as described above, steps 1 – 3

2. Tap the Formatting row

3. Change the Label suffix option to None by deleting the default [LF] characters.

This change will ensure that the Hex encoding option within TSL® RFID Apps will work correctly.

The ASCII encoding option will quite happily encode the default linefeed into the EPC so its removal is a matter of choice.

If you are encoding tags using any of the GS1 Tag Data Standard encodings then you will also need to ensure that the Datalogic barcode scanner sends the checksum digit with the barcode.

Enabling the Checksum Digit

This option is controlled in the Scanner Settings -> Symbology settings section and needs to be changed for each symbology in use:

1. Navigate to Scanner Settings as described above, steps 1 -3

2. Tap the Symbology settings row

3. Select the symbology in use e.g. UPCA

4. Ensure that the Send checksum option is enabled

With the linefeed suffix removed and checksum digits enabled, TSL® RFID Apps can now write GS1 tag encodings.

The post Configuring the Barcode Scanners on Datalogic Terminals To Work With TSL® Mobile Apps appeared first on Technology Solutions (UK) Ltd.

TSL^® have added support to RFID Explorer, RFID Scan Scan Write and RFID Tag Finder for the built-in barcode scanners on Zebra handheld terminals. This support uses the Android Intent system and some configuration of the terminal is required.
The TSL^® Apps make use of the built-in DataWedge App to provide barcode scanner input. This App has a long history and the instructions below refer specifically to DataWedge Version 6.4 and are based on the online guides that Zebra provide. Refer to the online guide for your particular version of DataWedge for any differences to the
steps outlined below. The full v6.4 setup guide is available here:

http://techdocs.zebra.com/datawedge/6-4/guide/setup/

Import DataWedge Profiles

If you have v6.4 then the supplied profiles for RFID Explorer, RFID Scan Scan Write and RFID Tag Finder can be imported as described here:
http://techdocs.zebra.com/datawedge/6-4/guide/settings/#importaprofile
If you are unable to import the profiles then follow the procedure below

Create a DataWedge Profile For The App

We recommend that a custom profile is created for each App which will allow for independent customisation of the Barcode settings such as enabling/disabling supported symbologies.

1. 1. Install the app (e.g. RFID Explorer) that will use DataWedge for scanning.
   2. Start DataWedge app and navigate to the Profiles list (if not shown by default).
   3. Tap on the Profiles screen’s “hamburger” menu and select -> New profile.
   4. Enter a name for the Profile (see table below) and tap OK. The new Profile appears in the Profiles list.

1. 5. Tap on the new profile.
   6. Select Associated Apps from the Applications section.
   7. In the Hamburger menu, select -> New app/activity. A list of installed apps appears.
   8. Select your app’s package name (scrolling down, if necessary) e.g. com.uk.tsl.rfidexplorer2.
   9. Tap the asterisk (*) to associate all of your app’s activities with DataWedge.
   10. Tap the device’s Back button until the new Profile’s Settings screen appears.
   11. Confirm that the “Profile enabled” checkbox is checked.
   12. In the Barcode Input section ensure that the “Enabled” checkbox is checked
   13. In the Intent Output section ensure that the “Enabled” checkbox is checked
       1. 1. Tap the “Intent action” option and enter: com.tsl.action.BARCODE_DATA
          2. Ensure that the “Intent delivery” option is set to: Broadcast Intent

1. 14. Disable all other Plug-ins such as Keystroke output or IP output etc…
   15. The TSL® app will now be able to use the terminal’s barcode scanner when required.

The post Configuring the Barcode Scanners on Zebra Terminals To Work With TSL® Mobile Apps appeared first on Technology Solutions (UK) Ltd.

Bluetooth® connections to TSL^® UHF RFID Readers operate in either SPP mode, where the reader is controlled by a custom-written application or in HID mode, where the reader behaves like a Bluetooth® keyboard.

Original Behaviour

In SPP mode, the Bluetooth® connection is always controlled by the host application. When powered-on, the reader will wait for a connection and power-down after (default) 60s if no connection is made. Once a connection is made, then the reader will stay awake and connected indefinitely.

In HID mode, once the reader is paired to a host, it will at power-up, automatically attempt to connect to the host.

New Behaviour

A firmware change now allows for a reader, in SPP mode, to reverse the master/slave role, remember the last connection and attempt to reconnect automatically when it is powered-on. This behaviour is off by default and is currently only applicable to iOS devices.

This greatly simplifies the use of the readers as, after they have been paired and connected to an application once, all that needs to be done is to power them on and use them.

Enabling

Additions have been made to the ASCII2 protocol sleep command (.sl) to allow control of this behaviour, with the following new parameters:

Just issuing the command .sl -ar on will be enough to make the reader remember the next iOS device that it is connected to. This may be achieved through the use of ASCII 2 Protocol Explorer for Windows Desktop or more simply, by using the ‘TSL Reader Configuration‘ app available from the App Store.

An application may choose to issue a .sl -cm off command to make the reader sleep and forget a connection, but still be prepared to remember the next device or a .sl -ar off command to sleep and stop the behaviour completely.

Firmware Versions

The new behaviour was introduced with the following versions of firmware.

The firmware in existing readers may be updated as described in the Application Note Downloading Firmware.

The post Bluetooth® Auto-Reconnect Mode appeared first on Technology Solutions (UK) Ltd.