Content Regulatory Regions ......................7 1.1. FCC Statement and IC Statement ......................7 1.2. European CE ............................8 Introduction ........................9 2.1. SOLARIA Intelligent Integrated Reader with 1 External Port ..............9 2.2. Software development kits ........................9 Reader Basics ........................10 3.1.
Page 4
5.4.2. The Capture Point Name can be modified in this page ................38 5.4.3. Access Mode ............................39 5.4.3.1. Set Access Mode..........................40 5.4.3.2. Custom Embedded RFID application....................40 5.4.4. Frequency Configuration ........................41 Set Regulatory Region ........................41 5.4.4.1. Operation Profile ..........................42 5.4.5. 5.4.6. Memory Information ........................44 5.4.7.
Page 5
5.8.1. Tag Group .............................55 5.8.2. Tag Database ............................59 5.8.3. Tag Filter ...............................66 5.9. I/O Management ..........................69 5.9.1. I/O Port Testing ............................69 5.10. Event Management ..........................70 5.10.1. Event Management ..........................71 5.10.1.1. Add Event ............................71 5.10.1.2. Modify Event ............................73 5.10.1.3. Enable/Disable Event ........................74 5.10.1.4.
Page 6
5.12.2. Upgrading JNI Library..........................92 5.12.3. Upgrading SSI API library ........................93 Read Tag using Web Interface and Event Engine ..............95 6.1. Read Tag using Default Profile and Default Event .................95 6.2. Example 1: Read Tag using Custom Profile and Custom Event ..............97 6.3.
Regulatory Regions 1.1. FCC Statement and IC Statement FCC STATEMENT 1. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference. (2) This device must accept any interference received, including interference that may cause undesired operation.
IC STATEMENT This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation of the device.
Figure 1. The SOLARIA reader has the following connectivity: Ethernet; GPIO; N-Type Antenna Port. 2.2. Software development kits Software development kits are available in SSI website: 1) .NET API (HTTP) 2) .JAVA API 3) Custom Embedded RFID: sample codes in /opt...
Reader Basics 3.1. Basic Hardware The SOLARIA is an Integrated RFID reader. Below is a side view of the SOLARIA Integrated Reader. The LED indicators show the operating status of the reader. Figure 2. SOLARIA connectors and LED indicators Operational description Power GREEN indicates power is applied to the reader [PWR]...
Page 11
Figure 3. SOLARIA connection diagram Interface Description PoE+ (IEEE 802.3at Compliant (Type 2); Ethernet interface: IEEE 802.3 10BASE-T/100BASE-TX IEEE 802.3 compliant Ethernet transceiver through an RJ-45 connector that has PoE+ magnetics. Power DC power supply - 12V, 5A (60 Watts) Or PoE+ (IEEE 802.3at Compliant, 30W) GPIO 4 pairs Opto-isolated inputs and outputs Antenna Port...
3.2. Connectors pin out details. The following diagram provides specific details regarding each connector type: Figure 4. Different types of M12 connectors Ethernet - LAN(PoE+): Mode A Mode B Description Rx+, DC+ LAN Rx+, DC+ for Mode A PoE Spec Rx-, DC+ LAN Rx-, DC+ for Mode A PoE Spec Tx+, DC-...
Page 13
Power - DC: Signal Description Color Voltage (12-57v) Brown Ground White GPIO Signal Description Color GPO3 Open Collector General Purpose Output #3 Brown GPI1_3_Return Optically isolated Input #1 and #3 common return Blue GPI2 Optically isolated input #2 White GPI3 Optically isolated input#3 Green Open Collector General purpose output #2 and #3...
3.3. Hardware set up a) DC Power The Solaria reader can be powered up by (1) AC/DC power or (2) PoE+ (802.3at PSE,30W) injector 1) Option 1: By AC Adaptor Unit [Optional Accessory] SOLARIA connect the AC adapter via the M12 Power cable and DC converter (optional). Please screw tight the lock on the M12 connector to ensure reliable power connection.
3.4. Mounting of the SOLARIA Reader Installation method on metal poles: Using the mounting bracket provided, the reader can be mounted onto a pole with a diameter of 40-60 1. Put on the mounting bracket in the orientation needed and put on the bolts. Tighten the bolts using a wrench.
3.5. How to Connect to and Configure SOLARIA User can connect to SOLARIA reader via Ethernet in the following ways: 1) Use the browser interface and the built-in event engine to configure the reader to run automatically based on certain logic sequence. 2) Write embedded program in the Linux OS inside directly to configure and control the reader.
3.6. Connecting to the SOLARIA reader using Browser SOLARA Reader is set to connect to Ethernet in DHCP mode. Connect Ethernet cable from your PC to the reader directly, or via an Ethernet switch while the reader is powered by DC adapter. Make sure the host is configured to work as a DHCP server. If the reader is powered up by PoE+ Switch or PoE+ injector, make sure the host is set in the same subnet and there should be a DHCP server in the subnet.
Page 18
A User Login page will be shown in User Name: stars, Password: systems then click Login The Status page is showed up after login. Default Access Mode should be HTTP/XML. Change the Access Mode if reader is not in HTTP/XML mode •...
3.7. Connecting to the SOLARIA reader via SSH Another popular way to connect to a Linux device is via SSH. Choose SSH on the front page if using the application PuTTY or other SSH terminal program: Start Putty, select SSH on Connection Type and type in IP address of SOLARIA, then click Open...
Page 20
Next, you should type in Login name : root Password : hRd29sLr23...
3.8. Embedded Linux Applications Development By using SSH of SOLARIA reader, you can develop embedded Linux codes in the usual Linux development manner. The SOLARIA Reader is using Yocto Linux. For popular open source software, you can use the command “dnf” to download popular precompiled binaries (dnf is similar to apt-get) by the following steps below:...
3.9. GPIO Port and Accessories for Connection SOLARIA has 4 General Purpose Inputs and 4 General Purpose Outputs, all of them are optically isolated, and also an isolated 12 Volt DC output power supply with a rating of 2 Watt.
GPIO Ports Connection Guide SOLARIA GPIO ports are optically isolated switches only. There are various ways one can connect them up for common peripheral control. The following sub-chapters describe typical ways to connect up for General Purpose Input (GPI) and General-Purpose Output (GPO) operations. The GPIO ports are optically isolated.
Page 24
Example 1: (GPI with +5V External Power Supply) Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of 1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also present for protection.
Page 25
Example 2: (GPI with +5V External Power Supply) Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of 1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also present for protection.
Page 26
Example 3: (GPI using the External +12V, 2 Watt Power Supply) Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of 1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also present for protection. GPI_1 Logic becomes Low when the sensor or Push button switch is turned on...
Page 27
Example 4: (GPI using the External+12V, 2 Watt Power Supply) Each GPI pin pair “looks” into an optical isolator with an operational forward voltage of 1.2 Volt, maximum 50 mA current. An internal series 1K Ohm 1.5 Watt resistor is also present for protection.
4.2. General Purpose Output (GPO) The maximum current that can pass through the GPO optically isolated switches of the SOLARIA reader is 2 Ampere. Therefore, a protection resistor with very high-power rating must be added in series to the external circuit to limit the current to 2 Ampere.
Page 29
Remark: The maximum current flowing through GPO pin pair is 2A...
Page 30
Example 2: GPO using relay for full isolation and high coil current (with External Power Supply) Remark: The maximum current flowing through GPO pin pair is 2A...
Web Browser Interface Details This chapter describes in detail the web browser interface. With SOLARIA, this web browser enables full control of the reader, including the event engine. 5.1. Home Page The home page of the web-based administration interface can be entered by typing the IP address of the reader (default IP address is printed on the label) on the web browser.
5.2. Status The “Status” page gives a quick overview of the status of the reader. The reader basic information such as serial number and access mode can be found on the first page of status page If any event was enabled and reading tag, the basic RFID related parameters will show on status page such as transmitting power, profile and session as below:...
Page 33
All firmware versions are shown on status page.
Network information can be found on status page such as IP and Mac address 5.3. Users Management The “Users Management” page contains sub-menu for adding, deleting and modifying password, set auto- logout time and login/logout.
Page 35
5.3.1. Modify Password To modify password, input the current password, new password and retype new password. Then click “Modify”.
Page 36
5.3.2. List Users The “List Users” page lists all the users and his/her authority. 5.3.3. Set Auto Logout Time The “Set Auto Logout Time” page allows ones to set the time for automatic logout if the user is idle.
5.3.4. Login/Logout The “Login/Logout” page is for users to login or logout the web browser interface. 5.4. System The “System” page contains many sub-menus to configure the reader for operation. Users are recommended to access these pages to determine the required settings before any operation.
5.4.1. Reader ID Here is the “Reader ID” submenu: 5.4.2. The Capture Point Name can be modified in this page The name of each antenna port refers to the Capture Point Name (Some may refer to read point name). This name can be configured. In other words, each antenna port (or capture point, or read point) can be uniquely identified and accessed or referred to.
5.4.3.1. Set Access Mode If you configure the reader on the web interface (e.g. Network setting, Time settings, Event Engine, etc.), you must set the Access Mode to “HTTP/XML”. If you configure the reader using your own embedded control system, please set the Access Mode to “Custom Embedded RFID HTTP”...
5.4.4. Frequency Configuration The “Frequency Configuration” page allows user to configure the frequency to be used by the reader. Please refer to the regulatory law of your region for the allowed frequency to be used. Here is the “Frequency Configuration” submenu:...
5.4.5. Operation Profile The “Operation Profile” page is extremely important as it sets the basic RFID parameters of the reader. Parameter Description Profile ID Each profile can be saved and recall for use in Event Engine, or be uploaded and redeployed to other SOLARIA reader in the field.
Page 43
Reader Mode/Link Profile There are different Reader Modes: 0 – Best Multipath Fading Resistance 1 – Longest Read Range, Dense Reader Mode 2 – Read Range and Throughput, Dense Reader Mode 3 – Maximum Throughput Please see Appendix B for more details Session # Session # S0, S1, S2, and S3, as defined by EPC Target...
5.4.6. Memory Information The “Memory Information” page shows the RAM and Flash memory used and free (available for use). It also displays the Clear Cache cycle time. This is the periodic time when the Linux OS cache is cleared. 5.4.7. Configuration Backup/Restore The “Configuration Backup/Restore”...
5.4.8. Power Up Notification System can send power up notification to server with a particular format if it is enabled 5.4.8.1. Add Power Up Notification 5.4.9. Heartbeat Heartbeat is used to monitor the system if it is running 5.4.9.1. Add Heat Beat The Heartbeat sending interval, type and address sending should be set on Add Heart Beat as below.
If the HTTP Post type server is selected, corresponding Server and Data Format should be selected as below. Server and Data Format was defined in Cloud Server page. 5.4.10. Log File Configuration There are different types of log files which can be enabled as shown below.
5.4.11. Download Log file All Log files can be download on this page, select Log files type going to download then click Download to start download. 5.4.12. Company Label Company label can be shown on web page and was defined on this page...
5.4.13. Advanced Settings The reader sensitivity can be set on this page by changing the parameters below. 5.4.14. Scheduled Restart System Restart can be scheduled on this page...
5.6. Network Management “Network Management” page allows the user to set the network parameters. Here is the network management sub-menu: The connection can be static IP or DHCP Connection Type can be set to static IP as below Connection Type can be set to DHCP as below.
5.6.1. Ethernet Configuration In “Network Configuration” page, one can configure the network parameters such as the reader IP address, Subnet mask, Gateway and DNS server.
5.7. Time and Timer Setting Here is the “Time and Timer Setting” submenu: 5.7.1. Date/Time The “Date/Time” page allows the user to set the real time clock inside the reader. Please configure the UTC (GMT) time on the reader. The local time will then be calculated based on the time zone that is being set.
5.7.2. Time Zone The time zone can be set on this page 5.7.3. NTP Setup This page allows one to setup the NTP server. The SOLARIA reader will update its time by connecting to the NTP server at a preset time and preset mode. Be sure to enter the gateway and DNS server in the network configuration page in order for the NTP server be reachable by the reader.
5.8. Tag & Tag Filter The “Tag & Tag Filter” page allows you to create the Tag group or Tag database which will be used in Trigger page and define filter to be enabled on operation profile. In actual deployment, RFID reader is used to do security screening of incoming or outgoing objects.
Page 56
Click Add to confirm the new group Add Tag ID to the group Click Add to add new tags to the group and below menu will pop up Click confirm the to confirm the addition of new tag to the tag group...
Page 57
Click Save to save the new tag group Import New tag ID Click Import then select the tags record file...
Page 58
New Tag ID was added to the window Click Save to save new record to the tag group Click Save & Download All record in the tag group was saved to file as below...
5.8.2. Tag Database Database can be created in reader for user to link tag with database record include basic information such as Vehicle name, plate number and corresponding photo, then show the record on web page after proper event defined. The defined database can be shown on page List Database The location of Database in reader can be set on Database Configuration submenu.
Page 60
Database can be added on Add Database submenu as below...
Page 61
Particular Database can be deleted on Delete Database All defined database can be shown on List Database Submenu as below...
Page 62
Tag Record in a particular database can be added after choosing right database The Tag Record content can be added to database on this page...
Page 63
Tag Record in a particular database can be deleted after choosing right database Click Delete to delete a particular record on selected Database as shown on below...
Page 64
Tag Record in a particular database can be modified on List Tag Record submenu after choosing right database as below Click here to start the modification...
Page 65
The content of database on particular record can be modified on this page as below Then click Modify to confirm the modification Each Database can be backup on Database Backup/Restore submenu as below after choosing target database Click Backup to start the backup...
Databases can be restored to system from pervious backup file as below 5.8.3. Tag Filter The tag filter was used to identify particular tags from a large population. There are two types of filter can be used including pre filter and post filter. If the pre filter is used, tags not matching filter will not respond while post filter, the reader will filter out all non matching tags after received all tags response.
Page 67
Filters can be added in Add Filter as shown below Only tag with same character on memory bank beginning with will apply the action Once filters are defined, they can be enabled in operation profile then take effect as shown below Choose the filter to apply from here...
Page 68
Any filters can be deleted from this page...
5.9. I/O Management The “I/O Port Testing” page allows users to test functionality of I/O port 5.9.1. I/O Port Testing Below is the “I/O Port Testing” page, it allows one to look at sensor input (you MUST press the “Refresh” button to update the input state), and control the outputs for system testing.
5.10. Event Management Event management is the most important part of the reader configuration. By setting it properly, you can handle business applications more efficient and autonomous. To create and enable an event, one needs to set up triggers, resultant actions, and then use that to assemble events. Once an event is created, the reader would run it accordingly.
5.10.1. Event Management Here is the “Event management” submenu: Note that there is ex-factory a “Default Event” running the “Default Profile”. It comes disabled (in the Enable column, it is False). Once you enable it, it will start reading RFID tags from Port 1 (assuming an antenna is connected to Port 1 for model SOLARIA and there are RFID tags in front of the antenna) 5.10.1.1.
Page 72
One should select the operation profile for the event. This operation profile is defined in the “System” page “Operation Profile” submenu. The Inventory Enabling Trigger is the initial trigger that turns on the RF power of the reader to start doing inventory.
5.10.2. Trigger A trigger is a stimulus that causes the reader to recognize it and do something about it. The trigger is used in Inventory Enabling, Inventory Disabling, and of course inside the actual Event Triggering Logic section. Below is the “Trigger” submenu: 5.10.2.1.
Page 77
“Read Any Tags (any ID, 1 trigger per tag)” would look at tags coming into the antenna ports (or capture points), the ones being ticked here would be selected, and will generate 1 trigger per tag (different ID) notification. By selecting which antenna port one can then select tags read by specific antennas to trigger an event.
Page 78
For “read any tags” trigger, the user also has to specify which antenna port or capture point it is collecting the tags from. To choose it, just tick the box on the left of each entry. For “Input Sensor State” trigger, the Port Number 1 shown on below, is mapped to physical GPI1 port which using pin 2 /pin12 of GPI1 terminal (GPI1 ports details see section 5.8).
5.10.2.4. List Trigger Below is the “List Trigger” page. 5.10.3. Resultant Action The “Resultant Action” pages define the resultant action that will be enforced when an event logic is established. Below is the “Resultant Action” submenu:...
5.10.3.1. Add Resultant Action There are 8 types of action: 1. Do Nothing (Only Show on Screen) – Nothing is affected, except the tags collected can be shown on browser screen. Note that there are APIs that can collect the tag IDs or information on demand from the remote server.
Page 83
Data Format ID is defined in Cloud Server page...
Page 84
Different field can be added to reporting format as below If one selects “Output Port” then one has to input few more fields. The user has to select the Port Number, 1 to 4. The Output Logic has to be selected, which can be either Open, Close or Pulse.
For Pulse, there are more parameters to be configured. The Pulse Logic, which can Open-Close-Open, or Close-Open-Close, and Pulse Mode, which can be One Shot Pulse or Pulse Train, the Pulse Width in msec., and for Pulse Train, the duty cycle and Pulse Duration. These are all self-explanatory. 5.10.3.2.
5.10.3.4. List Resultant Action Below is the “List Resultant Action” action page. 5.10.4. Tag Inventory Capture Tags Raw If there is any Event was enabled to read tags, all raw tags data can be found on this page...
5.10.4.1. Display Tag Group/Database Record When tag record within particular database was read by reader, the database content can be shown on this page as below Below is the Event called “Example Tag Database Display”, once the Event was enabled and right tag was detected, the database content will be shown as previous diagram...
5.11. Version Management The “Version Management” page allows you to review the version upgrade history (in the Version Control Submenu), and to do firmware upgrade (in the Firmware Upgrade Submenu). 5.11.1. Version Control In the “Version Control” sub-menu page, one can see the version number of the software. This is an important page to check if the versions are correct, especially after a firmware upgrade.
WebApplication to automatically restart to the login page. Firmware upgrades include the following 5 items: 1. Web Application Upgrade 2. JNI Library Upgrade 3. SSI API Library Upgrade 4. Apply Patch 5. RFID Firmware Upgrade 5.12.1. Upgrading Web Application Below is the page to upgrade Web application.
Page 91
the upgrading can be done directly using the zipped file...
Then click Upload after choosing the Web application file and upgrading will start 5.12.2. Upgrading JNI Library Choose the JNI Library zipped file (no need to unzip) Then click Upload...
Upgrading Unified API library Choose the zipped Daemon file. Then click upload. Applying Patch to System If there is any patch for system, it can be done on this page. Linux OS versions: 3.0.35 or 4.x.x can use same Patch file...
Page 94
Choose the zipped patch file then click upload...
Read Tag using Web Interface and Event Engine One can use a browser to quickly configure the SOLARIA reader to autonomously read tags based on certain logic sequence defined in the event engine and operation profile. 6.1. Read Tag using Default Profile and Default Event The SOLARIA reader comes with a Default Profile and a Default Event.
Page 96
Go to the List Event of Event Management in Event page and click List Event to show the Default Event Click “Default Event” to continue Click “List Event” to show default Event In Default Event, the reading tag from antenna port 4 can be started after the default event was enable and click Modify to confirm the change...
Click “Enable Event” to enable the tag reading Click “Modify” to confirm the changing Reading tag from antenna port 1 can be stopped once the default event was disable by unchecking Enable Event and click Modify to confirm the change 6.2.
Page 98
Click ports connected with antenna. 1 port have been activated with maximum output power equal to 30dBm and other 3 ports are not activated. Change the session, Target, Algorithm and Tag population to optimize reader performance.
Page 99
Please click “Add” to confirm the change. Add Event and change to use Demo1 which created before Click Add to create new event. Start inventory reading using Event Demo: Go to List Event in Event Management and click “Event Demo” to modify the Event. Click “Event Demo”...
Page 100
Select Always On Click Enable Event to enable it Click “Modify” to apply the change Please click “Modify” to confirm the change and inventory will start. Go to Tag inventory to check inventory result. Click “Tag Inventory” to check Inventory result...
Page 101
The Inventory can be stopped by disabling the Event 1 on Event Management as below Unchecked Enable Event to disable it Click “Modify” to apply the change Below procedure to enable particular group of tag to be detected and used this group as trigger Add tag group: Go to Tag group in Tag &...
Page 102
Click confirm to confirm the addition of new tag to the tag group Click Save to save the new tag group...
Page 103
Import New tags: Prepare tag record file, below is the example file and view by notepad Click Import then select the tags record file...
Page 104
New Tags was added to the window Click Save to save new record to the tag group In the Add trigger of Event menu, new tag group (TagGroup 3) is available as shown below Go to Event management, Group Trigger can be used in Trigger Logic on Event Demo...
6.3. Example 2: Example Event using Database Tag Group and Database Display The event Example Tag Database Display can display content of database located in reader if tag within database tag group was detected from antenna port 1 on SOLARIA or antenna port 4 on SOLARIA. This database record can contain Picture/Photo and text such as equipment photo, staff photo and corresponding text After corresponding even was enabled, database content will be shown on below page if the tag in...
Page 107
Below show the database event details. The database is going to use in this event, was choose in Trigger page as shown below The way showing database content was defined in Display Format, so, you need choose right display format in Resultant Action page as shown below on Display Tag Database Record Action Mode...
Page 108
Display Format can be modified/added in Display format page as shown below...
Page 109
Type of record on database can be listed in List Database as shown below.
Page 110
The content of each record on each database can be changed from List Tag Record as shown below click here to continue click here to choose which record to be modified...
Page 111
The content of record can be modified on this page The new record can be added to particular database in Add Record as shown below click here to continue...
Page 112
The content of each record on particular database can be added on this page as shown below...
Page 113
After all necessary modification was done, the event can be run again by clicking Even Enabled as shown below You should see the event status changed to Enabled...
Page 114
If you go to Display Tag Group/Database Record, you can see the database record content linking to the detected tag (The tag with EPC 123456789012345678901234 was used in this event Example Tag Database Display shipped with reader).
6.4. Read Tag using Custom Embedded RFID Change the access mode to Custom Embedded RFID Click Set to confirm the change Input the Embedded RFID application path and its command on this page as shown below, the application will run once the access mode changed to “Custom Embedded RFID” Select this page to input command path and it command...
Demo Source Codes for Download The source codes are available on request. The support page could be found in the below link https://star-int.net/support/...
Page 117
Historical Firmware Versions The following are lists of historical firmware versions of each firmware: Web Application: Version Number Date Description JNI Library: Version Number Date Description Patch: Version Number Date Description Unified API Library (Daemon): Version Number Date Description...
Page 118
About Us Founded in 2013, STAR Systems International (SSI) is a world leader in Automatic Vehicle Identification Technologies. SSI focuses on providing best-in-class transponders, readers and professional consulting services for Smart City Initiatives, including Electronic Tolling (ETC), Electronic Vehicle Registration (EVR), Fleet Management, Parking and Secure Access Control applications.
Page 119
INDUSTEY CANADA STATEMENT(French): Cet appareil est conforme aux normes RSS exemptes de licence d'Industrie Canada. Son fonctionnement est soumis aux deux conditions suivantes : (1) Cet appareil ne doit pas causer d'interférences nuisibles et (2) cet appareil doit accepter toute interférence reçue, y compris les interférences susceptibles de provoquer un fonctionnement indésirable de l' appareil.
Need help?
Do you have a question about the Smart Cities Solaria and is the answer not in the manual?
Questions and answers