j4210u-app

J4210U Hardware Demo Application

Supported Hardware

1. J4210U USB UHF RFID Desktop Short Range Reader. [https://www.amazon.com/dp/B09LD5L45F]
   
2. J4211UH USB Plain & Simple UHF RFID Desktop Handheld Reader. [https://www.amazon.com/dp/B0C7M5T21F]
   
3. J4420UX USB UHF RFID Long Range Reader with I/O. [https://www.amazon.com/dp/B0CGZJSXS6]
   
4. J4212U Short Range UHF RFID Desktop Reader with USB, GPIO and UART. [https://www.amazon.com/dp/B0CGYXD76V]

BUILD

The demo application is built using Eclipse with SWT toolkit. To successfully compile this application under other Java IDE and with your own code, do as follows:

1. Select the platform. Go to each platform and open the project file for that platform.
2. But when coding in Java, all code reside in a platform shared /src folder.
3. The binary class files reside in the platform's /bin folder.

FRAMEWORK

You can modify this application and create your own application. Your application then automatically run on all supported platform if you do as follows:

1. Each platform has j4210u.xml. Run this Ant script independently for each platform to build the single executable j4210u.jar. NOTE: This jar is platform dependent.

Windows 64 bit

Install Launch4j, a free Java executable from jar to create your Windows executable. Make sure that the following files are in the same directory as the executable: j4210u.dll, libgcc_s_seh-1.dll, libstdc++-6.dll, libwinpthread-1.dll and any other files that you load in the application.

MAC OS X

There is a Mac OS X application named UhfApp.app. You can directly run this application. To create your own application, make sure that simply run the Ant script j4210u.xml, the script will modify an application name UhfApp.app. You can change the name and the application icon by editing Info.plist inside UhfApp.app directory.

There are two Mac OS X distributions: The Intel Mac where an Intel base processor is used and the M1 Mac where Apple's M1 chip is used. Choose the appropriate distribution to run. One distribution will not run on the other Mac hardware. The are totally different hardware.

Linux 64 bit

In Linux, you simply run j4210u.sh script. To make this file executable, run the command:
chmod 755 j4210u.sh
Make sure libj4210u.so is in the same directory as the jar file.

Python

The python3 code is compiled with version 3.7. Most likely, it will also work with other version 3. See the README.TXT file in the python3 directory for specific instructions.

ECLIPSE PROJECT

Choose the product. Open the project for appropriate platform under the directory /platform.

Windows 64 -> /platform/win64
Mac OSX (Apple Silicon, M1 or higher) -> /platform/macosx (Do not use in Intel based Mac)
Mac OSX (Intel Processor) -> /platform/macosx[intel] (Do not use in Apple Silicon)
Linux 64 -> /platform/linux64
Python 3 -> /platform/python3
Other Platforms -> /platform/, where is one of the following: bananapi, beaglebone, beaglebone-ai64, orangepi, pocketbeagle, raspberrypi64.

NOTE: You may get error after loading the product because the /src folder will not in the same directory where we developed. Simply point to the correct directory in your development environment.

Videos

Short Youtube videos are prepared to learn how to operate this device.

1. Jence UHF App J4210U- https://youtu.be/JgcDBT68OjM
   
2. J4210U With RaspberryPi- https://youtu.be/B4wUL2kJwo0
   
3. J4210U With Python- https://youtu.be/jBNB8a8g6Hk
   
4. J4210U App New Features- https://youtu.be/jBNB8a8g6Hk
   
5. J4210U Messaging Feature - https://youtu.be/UJeyh9SEx2o?si=OaB1BONRjRyPppfk
   

NOTE

The hardware driver for j4210u is compiled to run only in 64 bit platform.

Arduino and Energia Support

The following models are compatible with Arduino and Energia:

1. J4212U
2. J4220UX These devices have GPIO and UART output in addition to USB allowing them to be operated by UART connection. The device is powered through the external ports and it is not necessary to connect with USB.

Drivers

Windows already come with a default USB Serial driver. Connect the device and check if there is any new COM port attached to the device. If not, then install the 64-bit driver from the driver directory. For Linux and Mac OSX, the driver attachement is automatic. However, in some Linux cdc_acm have to be executed if a driver is not attached.