MIURA M020-2 Multi Dock Charging Cradle User Guide

: June 16, 2024
: MIURA

Table of Contents

MIURA M020-2 Multi Dock Charging Cradle
Product Information
Product Usage Instructions
Software Update
System Menu
Revive
Functional Test
End-user Troubleshooting
Filtering Process
Example Diagnostic Files
Regulatory Information
FCC STATEMENT
Precautions for use
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

MIURA M020-2 Multi Dock Charging Cradle

Product Information

Specifications

Automatic full security check every 24 hrs
Bluetooth turned off during the security test
Files that fail security check will be removed
ReviveTM feature with pin-hole reset switch

Product Usage Instructions

Software Update
To perform a software update, follow these steps:

Access the application menu.
Select the “Software Update” option.
Follow the on-screen instructions to complete the update process.

Restart or Shutdown
To restart or shutdown the terminal, follow these steps:

Press the “OK” button to continue or “BACK (X)” to cancel.
If restarting, the terminal will reboot.
If shutting down, the terminal will completely shut down.

System Tampered
If the terminal detects tampering, follow these steps:

The terminal will close the Payment application and abort any transaction in progress.
The tamper state will be indicated on the display.
Return the tampered terminal for investigation.

Ready To Install
If the terminal is in the Ready To Install state, follow these steps:

No application is installed or has been deleted.
Return the terminal for investigation.

ReviveTM Feature
To use the ReviveTM feature, follow these steps:

Locate the pin-hole reset switch next to the power button.
Press the reset switch to activate the ReviveTM feature.
If external power is applied, disconnect it when prompted by the terminal.
The terminal will display the Revive Menu.

Reboot Terminal
To reboot the terminal, follow these steps:

Select the “Reboot Terminal” option in the Revive Menu.
The terminal will perform a complete hardware and software reset.

System Restore
If the terminal becomes unresponsive or is not running as expected, follow these steps:

In the Revive Menu, select the “System Restore” option.
The terminal will attempt to restore the system.
If the restore process fails, acknowledge the failure by pressing the “ENTER( )” key.

Factory Reset
To perform a factory reset, follow these steps:

Select the “Factory Reset” option in the Revive Menu.
The terminal will reset all software and configuration to the factory state.
If the factory reset process fails, acknowledge the failure by pressing the “ENTER( )” key.

Built-in Functional Test
To perform a built-in functional test, follow these steps:

Obtain the required test cards (swipe and smartcard) from Miura.
Alternatively, use a modified terminal provided by Miura.
Follow the on-screen instructions to perform the hardware tests.

FAQ

Q: What should I do if the terminal detects tampering?
A: If the terminal identifies tampering, immediately return it for investigation.
Q: What does the Ready To Install state mean?
A: The terminal is in a Ready To Install state when no application is installed or has been deleted. Return the terminal for investigation.

The terminal automatically performs a full security check every 24 hours. The terminal can be configured by the application to trigger this security test when the terminal is idle. During this time the Bluetooth will be switched off. The files that failed the security check will be removed from the terminal.

Software Update

The software on the terminal can be updated by the application on the smart device. The software update will be transferred to the terminal over Bluetooth or WiFi, once this is complete the software update will start. The terminal will indicate if a software update is in progress and will report success/failure. If the software update fails, the operator has to acknowledge the failure by pressing ENTER( ) to proceed further. In the unlikely event that a software update fails, a Factory Reset (see ReviveTM section) may be required to make the terminal operational. A software update is in progress. The terminal will display the success or failure message accordingly.

System Info
By selecting option (1) in the System Menu the user will be shown the terminal information. This would consist of current software installed on the terminal. This area will also display any injected keys for secure payments, along with the battery percentage of the terminal, the serial number of the terminal, and the hardware version installed. Here you can select BACK ( ) to return to the previous menu as above or OK ( ) to continue to return to the idle screen of MPI.

Restart MPI
If the installed MPI needs to be restarted for any reason, the user of the System Menu would press option (2). Options here are BACK ( ) to cancel or OK ( ) to continue to restart MPI.

Reboot
To reboot the terminal the user would select option (3) from the System Menu. Once pressed you will be prompted “System Reboot Are you sure?” Here you may choose BACK ( ) to cancel the reboot or OK ( ) to reboot the terminal.

Shutdown
Option (4) in the System Menu will prompt the user to “System Shutdown Are you sure?”. Here can also select BACK ( ) to cancel the shutdown of the terminal or select OK ( ) to completely shut down the terminal.

Error states

System Tampered
If the terminal identifies a tamper, the terminal will immediately close the Payment application aborting any transaction in progress. The tamper state is indicated on the display. A Tampered terminal should be returned for investigation.

Ready To Install
The terminal will be in a Ready To Install state if no application has been installed or has been deleted. A terminal in the Ready to Install state should be returned for investigation.

Revive

Miura products include a Revive feature which is activated using a pin-hole reset switch, which is situated next to the power button.

Pressing the Revive™ button will trigger a hardware reset, and the terminal will display the Revive Menu. This is best done when there is no external power applied, if external power has been applied the terminal will request to disconnect the external power. The end-user should use this feature if the terminal is running but is “locked up” and not responding to the power button.

The Revive™ Menu has three options, namely:

Power up as Normal
System Restore
Total Factory Reset

Power up as Normal
Selecting this option will reboot the terminal resulting in a complete hardware and software reset.

System Restore
The “System Restore” option will restore the terminal to an earlier point in time. If the terminal be- comes unresponsive to the power button or is not running as expected and option 1 in the revive menu is unsuccessful in recovering the terminal, the “System Restore” option can be used. The terminal requires the operator to confirm the “System Restore” selection in order to avoid unintentional system restoration.

Confirmation of the “System Restore” action is “System Restore” in progress. The terminal will display the success or failure message for the System Restore. If the system Restore process fails, the operator has to acknowledge the failure by pressing the ENTER ( ) key. In the unlikely event that a system restore fails, the terminal may be in an unusable state. The operator should then try “Total Factory Reset to recover the terminal.

Total Factory reset
The “Total Factory Reset” option allows the end-user to reset all software and configuration back to the state it was in when the terminal left the factory. This feature should be used if there are any issues with the terminal operation that cannot be solved by a Reboot or “System Restore”. Following a successful “Total Factory Reset”, the user will need to repeat the pairing process, and the controlling application on the smart device will need to perform any software configuration and key injection required. The terminal requires the operator to confirm the “Total Factory Reset” selection in order to avoid unintentional factory reset operation. Confirmation of the “Total Factory reset” action; Factory Reset in progress.

The terminal will accordingly display the success or failure message for the Total Factory Reset. If the Total factory reset process fails, the operator has to acknowledge the failure by pressing the ENTER ( ) key. If the factory reset fails the terminal has to be returned for further investigation.

Terminal Diagnostics
The Revive™ button can also be used to activate the terminal’s diagnostics facilities. This involves ex-porting operating system log files and running a built-in hardware functional test. It is not envisaged that this will be done by an end-user.

The diagnostics state is entered by activating the Revive™ button whilst holding the ‘O’ key. Once the terminal has booted, it will export XXX-XXXXXX- Conf.txt, XXX-XXXXXX-Info.txt, and XXX- XXXXXXEvents.txt diagnostic files in the USB Mass Storage Device, where XXX-XXXXXX is the serial number of the terminal. Example contents and format of these files are described in Appendix A: Example diagnostics Files. When returning a terminal under RMA, these files should be returned as well.

Once these files have been retrieved the USB cable can be removed and the terminal automatically starts the functional test, see the Functional Test section.

Creating Terminal Diagnostic Data: This state is notified when the diagnostics state is entered by activating the pin-hole switch.
Terminal diagnostics data exported in USB Mass Storage Device: Once the diagnostics log files have been created, the files will be exported to the Mass storage device. The files can be retrieved by connecting the USB lead to a computer. Unplugging the USB lead after this will start functional tests.
Failed to export Terminal diagnostics data in Mass storage device: If the terminal fails to export the diagnostics log files in Mass storage device, the terminal will display a failure message. The terminal should be identified as a return under warranty and all details of the terminal, and the fault recorded.

Functional Test

The Miura Operating System contains a built-in functional test that fully tests the hardware.

In order to perform the tests the following are required (and can be obtained from Miura):

A Miura test card with Mag-swipe and smartcard.
A Miura’s Raspberry Pi BT/WiFi responder. Or alternatively, a modified terminal provided by Miura running specific software with a pre-set Bluetooth address and a configured WiFi router/access point.
A 5 Volt power supply, capable of supplying at least 1 Amp.
An M020 fast-charging cradle
A small paper clip (not a sharp object) to activate the pin-hole reset switch.

The functional tests are activated when the USB lead is unplugged after the retrieval of the diagnostics files from the USB Mass Storage Device (MSD).

The following are general points for functional tests:

For each test, the instructions will be shown using the display.
For a pass, the next test will be loaded
For a fail, the operator has to acknowledge the failure by pressing ENTER ( ) to continue to the next test. Pressing CANCEL( ) when a Test has failed will abort the functional test.
Some tests can be aborted by pressing CANCEL( )
If any tests fail or are aborted, the final result will be a fail
If a test was aborted or performed incorrectly all tests must be repeated
If all tests pass the final result will be passed.
Either way, a results text file of the form XXX-XXXXXX_Results. txt will be exported in the MSD.

Where XXX-XXXXXX is the serial number of the terminal.

NOTE:
If tests are skipped or performed incorrectly (e.g. if a card was swiped badly or the Bluetooth responder was not switched on), the terminal will appear to have failed when it is not faulty. It is therefore important to make sure all tests are performed correctly. The sections below describe the procedure for functional tests.

Beeper Test
The beeper will sound for 2 seconds at the start of the factory test. After hearing the beeper a confirmation screen to which the operator has to press ENTER( ) if the beeper is working correctly or CANCEL( ) otherwise.

LCD display Test
Five color test screens will be displayed, each for 2 seconds. These are red, green, blue, white and lastly black. The operator has to look for a color problem, stuck pixels, or any abnormalities in the display. The black screen is a confirmation screen to which the operator has to press ENTER ( ) if the display is working correctly or CANCEL( ) otherwise.

Touchscreen (TS) test (M021 only)
The operator will be asked to touch a crosshair shown on the screen to perform a test of the touchscreen. After each touch, the crosshair will move to a different location to test different areas on the screen. After tapping or touching all the required positions, the test will automatically indicate whether it has passed or failed.

LED test (green LED)
The green LED at the top right corner of the terminal will blink, to which the operator has to press ENTER( ) if the LED is working correctly or CANCEL( ) otherwise.

Keypad backlight test (M021 only)
The keypad backlight will blink, to which the operator has to press ENTER ( ) if it is working correctly or CANCEL( ) otherwise.

Keypad Test
The terminal requires the operator to press each of the keys on the Keypad. The terminal will indicate which key should be pressed and then move to the next key if the press was successfully registered until all keys have been tested.

Magnetic Stripe Reader Test (Mag swipe)
The operator should swipe the test card provided. The terminal, on reading the swipe card, will record the success or failure. The operator is allowed a second try if the first swipe is not done properly. If it is not possible to run this test, it can be skipped by pressing the CANCEL( ) key.

Chip card Test
The terminal will request the operator to insert the test card provided into the chip card slot. The terminal will read the card and record the result. The terminal will then request the operator to remove the card to proceed to the next test. If it is not possible to run this test, it can be skipped by pressing the CANCEL( ) key.

Contactless card Test
The operator has to bring a contactless card near the contactless logo when prompted. The terminal will read the card and record the success or failure accordingly.

Charger Test
The terminal will request the operator to insert the USB cable connected to the PC or USB wall adapter and check for a Red charging LED next to the USB connector, if ON press ENTER( ) otherwise CANCEL( ). The terminal will then request the operator to remove the USB and check if the Red LED is off, if OFF press ENTER ( ).

Flashing red LED (regular on/off about twice a second)
- Remove power for 1 hour and ensure the terminal is in a room temperature environment (18-25C). Re-power with a known good cable and power supply (5V 1A). If the error re-occurs or persists, return the unit for repair
Flickering red LED (irregular or on with short off periods)
- Remove power and check with a known good cable and power supply (5V 1A).
- If the error re-occurs or persists, return the unit for repair
Red LED does not light even when correctly plugged into a power supply
- Remove power and check with a known good cable and power supply (5V 1A)
- If the red LED still does not light, there is a fault – disconnect the USB power & return the unit for repair

Charging Cradle Test

This will test that the charging contacts for use with a Fast Charge Cradle are working correctly. This test can be skipped if a Fast Charge Cradle is not available.
The contacts to be tested are 5V fast charge and GND, as shown in item 2 in the M020 Features section. The terminal will request the operator to place the terminal in the Fast Charge Cradle.
After a short period, the terminal will then request the operator to remove it from the charging cradle, which removes power from the charging contacts. The operator will be notified if the test fails.
Note: on certain OS versions a Smartcard charging test will follow this test. In that case, please repeat the procedure indicated for the Charging Cradle Test or skip if a Fast Charge Cradle is not available.

Bluetooth Test
For this test, the operator should have one of the following:

Miura’s Raspberry Pi BT/WiFi responder or
Dedicated Miura terminal configured as a BT responder

The operator should have the provided Bluetooth responder powered on and in Bluetooth range for this test. This test is automated and does not require any other input from the operator. The result will be recorded accordingly by the terminal and the operator will be notified if the test fails.

WiFi Test
For this test, the operator should have one of the following:

Miura’s Raspberry Pi BT/WiFi responder or
WiFi router or Access point configured with the following details:
- Router or access point type: standard 2.4 GHz, 802.11n or newer
- network name (SSID): miura-wrt-belk
- network security type: WPA2-AES
- network security key: WIF Imlur@

Either has to be powered on and in range. This test is automated and does not require any other in- put from the operator. The result will be recorded accordingly by the terminal and the operator will be notified if the test fails. If it is not possible to run this test, it can be skipped by pressing the CAN- CEL( ) key.

MFi Test
This is an automated test of the Apple Co-processor. The operator will be notified if the test fails.

Hardware Functionality Test Completion
Once all the tests have been executed, the test results will be exported in the MSD. The terminal will indicate on the display that the results have been exported in MSD. The results can be retrieved and attached to any reports as needed. The terminal can then be powered off.

End-user Troubleshooting

It is not possible for Miura to define end-user troubleshooting, as there are many components in the end-user experience that are not defined or controlled by Miura. It is envisaged that the partner will define the troubleshooting process, in part using information from this document.

This section gives some suggestions about what should be included as part of this process. Note that problems reported as the terminal not responding may in fact be caused by an issue with the smart device or the application running on it.

Does the device power on?

If the terminal does not power on, it should be charged for at least 3 hours (refer to Charging the battery). The red charging LED can be used as an indication that the terminal is charging correctly.
If the terminal still will not power on, the power source and USB cable being used should be verified.

Does the terminal perform as expected?

If the terminal displays System Tampered it should be returned for investigation
If the terminal does not perform as expected, and the issue is believed to be with the terminal as opposed to the smart device, then the user should Reboot the terminal using the Revive™ feature.
If the terminal is still not functioning as expected, and everything possible has been done to rule out the smart device and application, a System Restore should be performed.
If the terminal is still not functioning as expected, a Total Factory Reset should be performed.

Filtering Process

This section is aimed at determining if a given terminal is functioning correctly and is acceptable for use in the field. It is not envisaged that this process will be carried out by the end-user, but will form the basis of testing performed by Miura and the partner at various stages in the terminal’s life cycle including Miura OBA (Out of Box Audit), Partner QA Testing, Partner returns filtering and Miura returns filtering. Each of these stages will no doubt include other additional tests and processes as defined by the organization performing the stage (and documented separately) but the filtering process defined in this section should be common to all.

The equipment required is as detailed in the Functional Test plus the following:

Adequate light source
Magnifying glass
Inspection gloves (to avoid leaving fingerprints on new units)
1A USB mains adaptor and USB cable (enough to charge all units before filtering)

Step1: Perform a visual inspection on the terminal (to check for imperfections, damage, rattles, etc)

If this passes go to step 2.
If this fails the damage should be photographed and recorded.

Step 2: Charge the terminal and Power it on.

Charge each terminal for at least 1 hour using a 1A USB mains adaptor and USB cable.
Take the terminal off charge and switch it on (if it is not on already)
If the terminal powers on, go to step 3.
If the terminal will not power on, it is faulty.

Step 3: Check the terminal starts up.

If the terminal starts up normally (see Operating the M020 Payment Terminal), go to step 4.
If the terminal displays system tampered, the terminal is faulty.
If the terminal is in any other state, record the error state, obtain and store the terminal diagnostics files, and attempt to recover the terminal by performing a factory reset.
If the terminal now starts normally, go to step 4.
If not, the terminal is faulty.

Step 4: Run the Terminal Diagnostics and Functional Test.

Run the terminal diagnostics and functional test.
Retain all the log files created during these processes
If the terminal passes all functional tests, the terminal is deemed no fault found.
If the terminal fails any of the tests, it is faulty. All retrieved diagnostic files should be retained as they will be needed in any diagnostics that may be carried out.

NOTE:
The terminal will also report a failure after a Factory Test if the tests are carried out incorrectly, or if any test is skipped, in which case the test needs to be repeated in full. If a particular test fails, the operator can choose to continue with the remaining tests.

Example Diagnostic Files

020-000110-Conf.txt
This file identifies the hardware and software configuration of the Terminal.

Customer=Generic
Sound=N/A
GSM=N/A
Charge_cradle=5V
Smartcard=TDA8029HN
Flash=NAND 2kblocks64pages2112bytes*8b
USB_WiFi=N/A
RAM=LPDDR 4Banks8Mwords16b
Contactless=M020-EMVPCDHW-V1
Hardware=M020-TEST01-V2-0
Series=M020
USB_Bluetooth=6223E-UUD
Backlight=N/A
Serial=020-000050
Power=LP3910
OS=M000-DEVOS-V7-2
Ethernet=N/A
Printer=N/A
Light_sense=N/A
Battery_Low=N/A
Mag_sense=N/A
Battery_Stats=N/A
USB_OTG=500mA
Display=Mono 128*64 SSD1309
Processor=MCIMX258CJM4A
Keyboard=3×5(NA,M020,CLR,1,2,3,4,5,6,7,8,9,CNL,0,ENT)+Pwr+Revive
KB_backlight=N/A
MFi=MFI337S3959
LEDs=M020
PCBA=M020-PCBA01A-V1-5
Mag=3-Track MRD532

020-000110-Info.txt
This file provides information about the Terminal, including the hardware part number, current OS part number, Serial Number, current application part number, and fingerprint of the Remote Key Injection CA certificate loaded in manufacture.

Hardware: M020-PROD01-V2-0
Software: M000-OS-V7-4
Serial: 020-000050
App-version : M000-MPI-V1-28-CONF15-V1
CA-fingerprint: 93:DD:63:E0:19:50:FE:15:FF:57:F7:59:C7:34:65:5A:0E:75:4C:F8

020-000110-Events.txt

The File records the system events that happened from the manufacture of the Terminal.
Jun 18 11:32:41 miura miura-monitor: Couldn’t access shutdown time data
Jun 18 11:32:41 miura miura-monitor: Startup time – Wed Jun 12 11:32:08 2013
Jun 18 11:32:42 miura miura-monitor: Start-Up event – Wipe (4)
Jun 18 11:32:44 miura factory-test: Starting terminal key verification
Jun 18 11:32:44 miura factory-test: Terminal key verification success
Jun 18 11:32:46 miura factory-test: Ready to install Application
Jun 18 11:34:33 miura factory-test: Application installation starting
Jun 18 11:34:56 miura miura-auth: Request for make_factory
Jun 18 11:34:57 miura miura-auth: Request for make_restore
Jun 18 11:34:57 miura factory-test: Application installation successful
Jun 18 11:36:23 miura miura-monitor: Shutdown time – Wed Jun 12 11:35:01 2013
Jun 18 11:36:23 miura miura-monitor: Startup time – Wed Jun 12 11:35:57 2013
Jun 18 11:41:26 miura miura-monitor: Shutdown time – Wed Jun 12 11:35:01 2013
Jun 18 11:41:26 miura miura-monitor: Startup time – Wed Jun 12 11:41:00 2013
Jun 18 11:41:26 miura miura-monitor: Start-Up event – Start Terminal Diagnostics (7)

020-000110-Results.txt
Summary of the functional tests.

LCD Test

LCD Test: SUCCESS

LED Test

Pinpad LED Test: SUCCESS

Keypad Test

Keypad Test: SUCCESS

Mag-Swipe Test

Mag-swipe-test: TRK1 – PASS
Mag-swipe-test: TRK2 – PASS
Mag-swipe-test: TRK3 – PASS
Mag Swipe Test: SUCCESS

Smart-Card Test

Smart card Test: ATR Received: Size = 19.
Smart card Test: ATR: 3b5f9500807300010059434c5a1b0011409000
Smart card Test: SUCCESS

Contactless Card Test

Contactless: Card Detected!!!
Card in field
Contactless card Test: SUCCESS

Charger Test

Charger Test: SUCCESS

Cradle Test

Cradle Test: SUCCESS

Bluetooth Test

Manufacturer: Fn Link
Firmware tbd
HCI version: 4.0, LMP version: 4.0
Waiting for connection… accepted connection from 20:12:11:15:16:5D received [hello!]
Bluetooth Test: SUCCESS

Apple co-processor test

Apple co-processor test co-processor info:
Device version 5
Firmware Version 1
Protocol Major version 2
Protocol minor version 0
Device ID 0x00000200
Apple Co-Pro Test: SUCCESS
Factory Test: Functionality tests completed.

Regulatory Information

Battery:
This product uses a Lithium-Poly battery.

Do not use it in a humid, wet, and/or corrosive environment. Do not put, store, or leave your product in or near a heat source, in a high-temperature location, in strong direct sunlight, in a microwave oven or in a pressurized container, do not subject to extremely low air pressure and do not expose it to temperatures over 60°C (140°F). Failure to follow these guidelines may cause the battery to leak, become hot, explode, or ignite, and cause injury and/or damage.

Do not pierce, crush, cut, open, or disassemble the battery. If the battery leaks and you come into contact with the leaked fluids, rinse thoroughly with water and seek medical attention immediately. For safety reasons, and to prolong the lifetime of the battery, when not in use store your product in a cool, dry place. Charging will not occur at low (below 0°C/32°F) or high (over 45°C/113°F) temperatures.

CAUTION:

Do not remove or attempt to remove the non-user-replaceable battery.
Risk of explosion if the battery is replaced with an incorrect type.

THE BATTERY CONTAINED IN THE PRODUCT MUST BE RECYCLED OR DISPOSED OF PROPERLY ACCORDING TO THE LOCAL LAWS AND REGULATIONS AND ALWAYS KEPT SEPARATE FROM HOUSEHOLD WASTE. BY DOING THIS YOU WILL HELP CONSERVE THE ENVIRONMENT.

CE marking
This equipment complies with the requirements for CE marking when used in a residential, commercial, or light industrial environment, achieving all the appropriate provisions of the relevant legislation in the EU.

RED directive
Hereby, Miura Systems Ltd declares that Miura Systems Ltd products and accessories are in compliance with the essential requirements and other relevant provisions of the EU Directive 2014/53/EU. The declaration of conformity can be found here: www.miurasystems.com/certifications

WEEE directive
The wheelie bin symbol on the product or its packaging indicates that this product shall not be treated as household waste. In line with EU Directive 2002/96/EC for waste electrical and electronic equipment (WEEE), this electrical product must not be disposed of as unsorted municipal waste. Please dispose of this product by returning it to the point of sale or to your local municipal collection point for recycling. By doing this you will help conserve the environment.

Pacemakers
Pacemaker manufacturers recommend that a minimum of 15cm (6 inches) be maintained between a handheld wireless device and a pacemaker to avoid potential interference with the pacemaker. These recommendations are consistent with independent research and recommendations by Wireless Technology Research.

Guidelines for people with pacemakers

You should ALWAYS keep the device more than 15cm (6 inches) from your pacemaker.
You should not carry the device in a breast pocket.

Other medical devices
Please consult your physician or the manufacturer of the medical device, to determine if the operation of your wireless product may interfere with the medical device.

FCC STATEMENT

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, and (2) this device must accept any interference received, including interference that may cause undesired operation.

FCC Caution:

Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment.
This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

Reorient or relocate the receiving antenna.
Increase the separation between the equipment and the receiver.
Connect the equipment to an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.

Radiation Exposure Statement
The product complies with the FCC portable, RF exposure limits set forth for an uncontrolled environment under FCC rule part §2.1093 and KDB 447498 D01.

The exposure standard for wireless devices employs a unit of measurement known as the Specific Absorption Rate or SAR. The SAR limit set by the FCC is 1.6W/kg. For body-worn operation, this Mobile Point of Sales terminal has been tested and meets FCC RF exposure guidelines when used with an accessory that contains no metal and that positions the product a minimum of 0 mm from the body. Use of other accessories may not ensure compliance with FCC RF exposure guidelines

Canada IC
This device contains license-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canada’s license-exempt RSS(s). Operation is subject to the following two conditions:

This device may not cause harmful interference.
This device must accept any interference received, including interference that may cause undesired operation.

Radiation Exposure Statement
The product complies with the safety requirements for RF exposure in accordance with RSS-102, issue 5 for portable use conditions.

The exposure standard for wireless devices employs a unit of measurement known as the Specific Absorption Rate or SAR. The SAR limit set by the RSS is 1.6W/kg. For body-worn operation, this Mobile Point of Sales terminal has been tested and meets RSS RF exposure guidelines when used with an accessory that contains no metal and that positions the product a minimum of 0 mm from the body. Use of other accessories may not ensure compliance with RSS RF exposure guidelines.

Precautions for use

Do not use in areas of strong electromagnetic interference such as near:

Microwave ovens;
Magnets;
Shoplifting prevention devices;
High-voltage lines;
Automatic doors;
Communication antennas etc.

Do not install:

Where wide variations of temperature and/or humidity can occur or near fires, heat equipment, air conditioners, places where condensation may occur, etc.;
In areas exposed to strong direct sunlight;
In areas with high concentrations of dust or other fine particles;
In locations where the terminal may be accidentally dropped or damaged by falling objects;
Where the USB plug cannot be easily removed if an abnormality occurs;
In locations where high levels of static electricity are likely to occur;
Where water or other liquids may be spilled onto or into the terminal.

Registered office:
Miura Systems Ltd, Unit 3, Cliveden Office Village, Lancaster Road, Cressex Industrial Estate, High Wycombe, UK HP12 3YZ