ScanVue Price Verifier Web Browser Client User Guide

®
ScanVue Web Browser Client
ScanVue® Price Verifier
Web Browser Client User Guide
IEE Inc.
7723 Kester Ave
Van Nuys, CA 91409
38599-01 RevE
1
3/11/2014
®
ScanVue Web Browser Client
TABLE OF CONTENTS
Introduction ................................................................................................................... 3
Description ............................................................................................................................................................... 3
Usage .........................................................................................................................................................................3
ScanVue® Documentation Access Instructions .......................................................................................................4
Technical Assistance .................................................................................................... 4
ScanVue® Web Browser Specifications .................................................................................................................5
Display ......................................................................................................................................................................5
Power Options: ........................................................................................................................................................5
Communication Options: ........................................................................................................................................5
Additional Communication Options: .....................................................................................................................5
Operating Modes ........................................................................................................... 6
Configuration Mode ................................................................................................................................................6
Kiosk Mode ..............................................................................................................................................................6
Demo Mode ..............................................................................................................................................................7
Configuring the Web Client .......................................................................................... 8
Wireless Network Security......................................................................................................................................8
Connecting to a Network Host ................................................................................................................................ 8
Connecting to a Local Host .....................................................................................................................................9
Network Configuration by Barcode .......................................................................................................................9
Network Configuration using Ethernet .................................................................................................................9
Network Configuration using UnitConfig ........................................................................................................... 10
Configuring the Browser Interface ...................................................................................................................... 10
Specifying the Input Device URL ......................................................................................................................... 10
PushButton, MSR and Touchscreen URL’s ....................................................................................................... 12
Touchscreen ........................................................................................................................................................... 12
Pushbuttons ............................................................................................................................................................ 12
Magnetic Stripe Reader ........................................................................................................................................ 12
Running the Browser Client (Kiosk Mode) ................................................................ 13
Slideshow ................................................................................................................................................................ 13
Using the PV ........................................................................................................................................................... 14
Review of Rules for Implementing a Web Server Application .......................................................................... 14
Page Load Response Time .................................................................................................................................... 15
Page Load Errors................................................................................................................................................... 15
Appendix A .................................................................................................................. 16
Demo Barcodes ...................................................................................................................................................... 16
38599-01 RevE
2
3/11/2014
®
ScanVue Web Browser Client
Introduction
The ScanVue Price Verifier Web Browser Client Users Guide is intended to be used
along with the ScanVue Price Verifier User Manual (the primary User Guide). Network
setup for V7. 4X software is identical to Scanvue; thus details may not be repeated
unless germane to the context. Specific web browser setup modes and operations are
fully described in this document.
Description
The ScanVue Price Verifier Web Browser Client is an embedded version of Mozilla’s
Firefox running under kernel V2.6X of the Linux operating system. The ScanVue Web
Browser software presents the server side application program developer with a
standard HTML web browser interface to the Price Verifier (PV).
The V7.4X client application is stored as a compressed binary image on an internal
CompactFlash™ card, along with necessary operating system files and utilities. At boot
time, compressed files are expanded into RAM memory where the client application will
execute.
Usage
V7.4X runs on the Geode LX800 based AMLCD model PV with 2GB CompactFlash™
and 512MB SDRAM memory.
38599-01 RevE
3
3/11/2014
®
ScanVue Web Browser Client
ScanVue® Documentation Access Instructions
Following are the directions on how to access ScanVue® Price Verifier support documentation
and Software Developers Kit (SDK) from IEE web site (www.ieeinc.com).
Please follow link for available ScanVue® Price Verifier documentation off the website.
http://www.ieeinc.com/html/scanvue_price_x_verifier_support_documentation.html
1) Under ‘Documentation Folder Contents‘,look for the following:
ScanVue® Price Verifier User Manual.PDF
ScanVue Price Verifier Web Browser Client Users Guide.PDF
Metrologic QuantumTM Configuration Guide.PDF
2) Download the latest configuration program UnitConfig 3.4.zip and modeset utility from
the website located under ‘Sample Utilities Folder Contents’.
Note: The latest files (UnitConfig.exe version 3.4 and ProductInfo.dll) will need to be
placed in the same folder of your choice.
Technical Assistance
If you require technical assistance in bringing up your ScanVue® Price Verifier, please call (818)
787–0311 and ask for Technical Support. Please be prepared to discuss your configuration and
setup parameters.
38599-01 RevE
4
3/11/2014
®
ScanVue Web Browser Client
ScanVue® Web Browser Specifications
Display
¼ VGA (320x240 pixel) color graphics 5.7” Diagonal LCD display
Network Server Computer Requirements:
MS Windows, Unix, Linux, VAX or any other platform that runs a TCP/IP network
Supported Operating Systems:
Windows 98, ME, 2000, NT, XP, 7, Unix, Linux and Open VMS
Power Options:
Wi-Fi and Ethernet Models: 11-29 VDC, 10 W typ. (24 VDC Nominal)
PoE Hardwired Models: 48 VDC, 10 W typ. (IEEE 802.3af compliant)
Communication Options:
11Mbps (IEEE 802.11b) Wi-Fi *
TCP/IP peer-to-peer Ethernet 10/100 BaseT
Power-over-Ethernet (PoE)
Additional Communication Options:
2 USB ports (For internal use only at his time to support optional Touchscreen, MSR and
Wi-Fi Dongle) – For any desired future use, please contact Sales
Barcode Scanner:
Omni-directional, 1,650 Scan Lines per Second, 5 Fields of 4 Lines
Auto discriminates all 1-D bar codes including RSS-14, RSS Limited and RSS Expanded
Interactive Device Options:
4 front panel push button switches
16 x 12 digital touch screen
Magnetic Stripe Reader
Browser Software:
Operating System:
Internal Web Server:
Image Formats:
Input Data Steering:
API:
Embedded Linux
Embedded Apache Server
GIF, Animated GIF, JPEG, PNG
Configurable URL for each device type
Standard HTML 4.0, Javascript, PHP
Configuration Setup:
On-line: UnitConfig, Off-line: Barcode
Security:*
WEP
WPA - WPA-PSK, TKIP
WPA2 - WPA-PSK, CCMP
®
*NOTE: WEP (Wireless Equivalent Privacy) encryption continues to be supported by ScanVue , however, the
recommended solution to WEP security problems is to switch to WPA2 (Wi-Fi Protected Access).
38599-01 RevE
5
3/11/2014
®
ScanVue Web Browser Client
Operating Modes
Version 7.4X browser client software, although fully integrated, may be considered to
have three primary modes of operation: Kiosk Mode (the normal run-time operating
mode), Configuration Mode (the mode used when setting up the PV) and Demo Mode
(the default mode as shipped). Kiosk and Configuration modes require a network
connection to a host computer (although the unit may be minimally configured with
barcodes). Demo mode runs directly on the PV without connection to a host and is
useful for salespeople and others interested in easily demonstrating the PV’s
capabilities. Demo mode is a fully functional implementation of a simple host (internal)
serving the PV using PHP and html scripts.
Configuration Mode
Configuration Mode is used to initially configure the unit to its specific network and
operational settings and subsequently for general maintenance, changing unit modes
and network settings.
Configuration is done using the external UnitConfig program. If you have wireless units
and are using WPA, your IT policy may not allow turning the security off even
temporarily for new installs. In this case you may have to use a combination of methods.
Not all configuration options may be entered using barcodes, so the barcode approach is
only recommended for initial network configuration.
Once properly set up and connected to your host, changes to the PV’s configuration can
be made via the external UnitConfig program without ever having to disconnect any PV,
even if the changes are made from a remote corporate location across a WAN.
Kiosk Mode
Kiosk Mode is the run-time browser mode for the product. It is the interface between the
user (customer) and the PV. A retail store unit, for example, running a product item
price verifier, loyalty program, gift registry and other retail applications will be operating
in Kiosk mode.
Although the V7.4X Browser client is a separate software package than the V6.x
ProductInfo client, there is a common base of code extracted from the V6.x client that is
used in the underlying structure of the V7.4X client. This code supports the input device
drivers—barcode scanner, digital touchscreen and pushbuttons, informational
messages, the configuration mode control routines and many other tasks. In many ways
the two client versions are very similar underneath the top layer, which is why the same
utilities work with both versions of software. The application interface layer is, however,
completely different with the V7.4X browser supporting a standard HTML interface as
compared with a V6.X unit, which uses altogether different methods to communicate
with the host and users.
38599-01 RevE
6
3/11/2014
®
ScanVue Web Browser Client
Demo Mode
Demo mode provides a way to showcase the PV’s abilities without requiring a physical
connection to a host computer. An internal web server with a price-lookup database
application loaded with several items is embedded in all V7.4X ScanVue models.
To enter demo mode, HomeURL mode must be set to the factory default URL
http://localhost/index.html. HomeURL2 mode must be set to the factory default URL
http://localhost/index2.html. When booted up in this mode, the PV will default to its
internal servers’ home pages. The PV will accept barcodes from the scanner device,
card swipe data from the MSR and button presses while 2 home pages are cycled
between 2 graphic images. If unsuccessful, a graphic appears informing the user that
the data was not understood. The optional touchscreen and printer can be active to
demonstrate functionality.
New PV’s shipped from the factory will already be in the default configuration and will
boot to the internal home page ready to accept the demo barcode scans. For units that
have been re-configured, scan the Return to Factory Defaults barcode tag then the Save
and Reboot tag, which will return the PV to its factory default (Demo Mode) condition.
Demo barcode tags are provided at the back of this manual. They are for Contadina
Sauce, Seeds, Stain, T-Shirts and one for a Ferrari animation. When each barcode is
scanned, the internal web server application will lookup the price and description for that
item (and/or graphic content) and display the data retrieved from the lookup tables. The
data for each item is composed of multilevel graphic images and demonstrates what
might be done on an in-store networked system.
To exit demo mode, reconfigure the PV to run on your network (see next section on
Configuring the PV) and change the HomeURL and HomeURL2 to your network home
pages.
38599-01 RevE
7
3/11/2014
®
ScanVue Web Browser Client
Configuring the Web Client
ScanVue units are shipped from the factory with default settings to allow easy
connection to a host—either your network server or a local desktop or laptop where you
can configure the unit for your network. When the PV boots, status information screens
1-3 are displayed on a blue background if configured for hardwired Ethernet. When
configured for Wireless operation, info screens are displayed on a green background.
Alternately, the CD-ROM provided with the PV contains a program SetupServer that will
install a shared folder (\POS) and frequently used utility programs onto your Windows
based host. UnitConfig is an easy to use graphics program, designed to re-configure
the PV’s internal modes and network settings when on-line and connected to a host.
This program will be the most useful and frequently used utility.
Wireless Network Security
Initially, security settings are disabled. WPA mode must be enabled in the unit to use
the security feature. The PV will run in WPA or WPA2 (Wireless Protected Access).
UnitConfig allows the user to setup the mode parameters. The supported ScanVue
settings are shown in the table below. For additional security requirements contact IEE
Sales.
SCANVUE
WPA
WPA-2
USEWPA
TRUE
WPDSCANSSID
TRUE
WPAKEYMGMNT WPA-PSK
WPAPAIRWISE
TKIP
WPAGROUP
TKIP
USEWPA
TRUE
WPDSCANSSID
TRUE
WPAKEYMGMNT WPA-PSK
WPAPAIRWISE
CCMP
WPAGROUP
CCMP
Connecting to a Network Host
The PV’s IP Address is obtained via DHCP and the Mask is 255.255.0.0. If a DHCP
server is running on your network it should find the PV’s MAC address and assign it an
IP Address when you plug it in to the network (provided that any gateway in the network
required to access the DHCP server is also configured).
As shipped, a hardwired unit will initially attempt to make a DHCP connection to a host
over its Ethernet port. If it fails to receive a DHCP address, the unit will default to IP
address 192.168.1.100. For wireless units, the default behavior is identical to hardwired
units unless the PV fails to make a connection with its designated wireless router or
access point. In that event, the unit reverts to hardwired, allowing the user to connect to
the unit from another computer. If the unit’s address is not compatible with the target
network, a crossover cable (also not provided) between the PV and a PC may be
needed to make a direct network connection to the PC.
38599-01 RevE
8
3/11/2014
®
ScanVue Web Browser Client
After the PV has been powered up or reset and the boot cycle is completed, normal
browser operation is to load the web page specified in the parameter HomeURL and
HomeURL2. Note: If these URL’s cannot be found, the browser will enter a cyclical state
where it alternately displays the logo and a message warning the page cannot be
displayed. Ensure the HomeURL or HomeURL2 value is correctly entered and its server
is on-line and accepting connections.
At this point you should be able to ping the PV from your host computer to validate the
connection. Use UnitConfig to change the HomeURL parameter to the page you want
loaded when the PV boots up. The default IP address can also be changed at this time
if a DHCP address was not assigned. A detailed explanation of how to use UnitConfig
is available in the ScanVue Price Verifier User Manual.
Connecting to a Local Host
Using UnitConfig to configure the PV is only possible if the unit has a valid network
connection to a host PC running Windows with the UnitConfig software installed. Refer
to the ScanVue® Price Verifier User Manual for more details on connecting the unit to
a PC. A synopsis is contained in the section “Network Configuration Using Ethernet,”
below.
Once connected, changes can be made quickly and easily with the UnitConfig program.
Network Configuration by Barcode
An alternative way to configure a PV off-line is with barcodes. The PV can be
completely setup for your network using the barcodes described in Appendix B of the
ScanVue® LCD Price Verifier User Manual and checked using status screen 1 and 2
barcodes which will enable you to verify the settings. You will need to have a barcode
generator program and printer available if you are going to configure using barcodes.
Network Configuration using Ethernet
A few rules and network parameters are worth repeating here to assist in getting quickly
connected to the host. This process is described in greater detail in the Quickstart
Guides and primary User Guides.
1. Connect the RJ45 network port on the PV directly to your local computer network
port via a cross over CAT5 cable. If you are connecting through a hub or switch, use
a straight through CAT5 cable. The PV uses a rate sensing 10/100 Mb/s device,
which should automatically detect and implement the appropriate speed for your
network.
2. The PV’s default IPAddress is 192.168.1.100 (if it doesn’t get a DHCP address) and
Mask is 255.255.0.0. The IP Address of the server installed using ScanVue® Price
Verifier User Manual is 10.0.10.13. If you are using UnitConfig to do the setups
you will have to temporarily change the Windows network settings to accommodate
this.
3. Start the PV by plugging in its DIN power connector. The PV will begin its boot cycle
and after booting will display a logo followed by 3 sequential status screens showing
the unit’s current configuration, and finally on to the home page (displaying the
default demo as shipped).
38599-01 RevE
9
3/11/2014
®
ScanVue Web Browser Client
Network Configuration using UnitConfig
1. Start the UnitConfig program on the host correctly networked to the PV. Enter the
PV’s IP Address in the “Unit IP Address:” box.
2. UnitConfig will interrogate the PV at the IPAddress entered and read back and
display all the current mode settings, filling in the boxes in the table. Make any
changes necessary then save and reboot the unit into its new configuration.
A detailed explanation of UnitConfig is contained in ScanVue® Price Verifier User
Manual.
Configuring the Browser Interface
Three optional input devices are available (Digital touchscreen, 4 front panel mounted
pushbuttons and magnetic stripe reader). Each input device (except touchscreen) has
a unique URL prefix and suffix that can be set using UnitConfig and provides the
steering to get that device data to a specific web domain where the server application
originates.
Specifying the Input Device URL
Input device URLs are built from an optional base prefix, a URL prefix, the ASCII data
read from the input device and an optional URL suffix in the general form:
{[BasePrefix]URLprefix}{Data}[URLSuffix]
Where:
BasePrefix refers to a prefix to be applied before all URLs
URLPrefix refers to a prefix applied after the BasePrefix for 1 URL
Data refers to the input data
URLSuffix refers to a suffix applied after the Data for 1 URL
For example, if BasePrefix is http://mysite.com/, URLPrefix is barcode.php>val= and
URLSuffix is not used, a barcode scan of 1234567B would yield the following:
Barcode scan
http://mysite.com/barcode.php?val=1234567B
where 1234567B is the SKU or UPC number
Let’s look at another example using all elements. If BasePrefix is http://mysite.com/,
URLPrefix is catalog/ and URLSuffix is .html, a barcode scan of 1234567B would yield
the following:
Barcode scan
http://mysite.com/catalog/1234567B.html
where 1234567B is the SKU or UPC number
The first example demonstrates a price lookup application where the concatenated URL
will route the ASCII data read from the scanner to the php script “barcode.php,” which
expects input to be assigned to the “val” variable. That php script would then generate a
page to be displayed on the PV representing the item scanned. The second example
demonstrates a price lookup using an html script residing in the “catalog” directory on
the “mysite.com” domain. Again, the script generates a page to be displayed on the PV
representing the item scanned. In either case, the script can use the scanned barcode‘s
ASCII value to retrieve price, description, a product graphic, and even instructions for
product usage from whatever source the programmer chooses. The possibilities are
limited only by the ingenuity of the application programmer.
38599-01 RevE
10
3/11/2014
®
ScanVue Web Browser Client
The table below shows the specific modes for the browser client. If any input device is
not present, its mode does not have to be set.
Configuration
Mode
HomeURL
HomeURL2
URLPrefix
Description
Default
Complete URL defining the primary home or start page. Must be a valid web
page. Typically, this page might load an animated GIF “slideshow”. With
default HomeURL, the browser cycles between HomeURL and HomeURL2.
Be sure to include the port number if other than port 80 (or 443 for https://
lookups), as in http://mysite.com:83/.
http://localhost/in
dex.html
Example: http://mysite.com/index.html
Complete URL defining the secondary home or start page. Must be a valid
web page. Typically, this page might load an animated GIF “slideshow”.
With default HomeURL, the browser cycles between HomeURL and
HomeURL2. Be sure to include the port number if other than port 80 (or 443
for https:// lookups), as in http://mysite.com:83/.
Example: http://mysite.com/index2.html
Prefix for the barcode scanner. Any legal full or partial URL is acceptable.
http://localhost/in
dex2.html
http://localhost/b
arcode.php?val=
URLSuffix
Example: http://mysite.com/barcode.php?val=
Suffix for barcode scanner. Any legal URL suffix will suffice. May be left
blank.
btPrefix
Prefix for 4 pushbuttons. Any legal full or partial URL is acceptable.
btSuffix
Example: http://mysite.com/buttons.php?val=
Suffix for 4 pushbuttons. Any legal URL suffix will suffice. May be left
blank.
(Not Set)
Prefix for Magnetic Stripe Reader (MSR). Any legal full or partial URL is
acceptable.
http://localhost/m
sr.php?val=
Example: http://mysite.com/msr.php?val=
Suffix for MSR. Any legal suffix will suffice. May be left blank.
(Not Set)
msrPrefix
msrSuffix
(Not Set)
http://localhost/b
uttons.php?val=
ScreenBlank
Timeout in seconds before screen blanks. 0 is no blanking. This value must
be left at 0 or set greater than the POS timeout (otherwise scan results may
be prematurely blanked).
0
BDelay
User settable delay between barcode scans to prevent very rapid
multiple scans from overloading the embedded browser. (secs)
0
38599-01 RevE
11
3/11/2014
®
ScanVue Web Browser Client
PushButton, MSR and Touchscreen URL’s
Touchscreen
The touchscreen emulates a mouse and does not have URL prefix and suffix entries.
When the touchscreen is pressed, the browser internally reads the co-ordinates output
by the touchscreen controller and positions the cursor at those coordinates. It then
generates a “button down/button up” event pair. If the cursor is positioned over a
hyperlink on the page it is displaying, the browser will attempt to follow that link. The
touchscreen driver is throttled to disallow drag-and-drop events, ensuring users cannot
drag the displayed window out of the PV’s display region.
The maximum resolution of the touchscreen is 31 horizontal cells and 23 vertical cells.
This corresponds to a physical size of 0.15” x 0.15” (3.7mm x 3.7mm) on a 5.7” screen.
A graphic button this size is far smaller than a finger can press and at this resolution at
least 4 cells x 4 cells should be used for a graphic button. The smallest practical button
size for finger operation is 0.6” x 0.6” (15mm x 15mm). These are not hard rules, only
guidelines.
Pushbuttons
The four pushbuttons are treated as four separate input devices. When a pushbutton is
pressed, a URL is generated with the btPrefix and btSuffix specified and the pushbutton
position number merged.
PushButton
Pushbutton 1 (leftmost)
Pushbutton 2 (2nd from left)
Pushbutton 3 (3rd from left)
Pushbutton 4 (rightmost)
Pushbutton release
Value
fffffff1h
fffffff2h
fffffff4h
fffffff8h
fffffff0h
Pushbutton Table
For example:
Pressing pushbutton 2 could generate the following URL (depending on settings).
Press pushbutton 2
http://mysite.com/buttons.php?val=fffffff2
Releasing pushbutton 2 could generate the following URL (depending on settings).
Press pushbutton 2
http://mysite.com/buttons.php?val=fffffff0
Magnetic Stripe Reader
HTML cannot handle many of the special characters that are commonly used in magnetic stripe
encoding. MSR data sent to an HTML application via the browser has been encoded to pass the
elements as needed by HTML conventions. For example, ‘&’ is replaced by ‘&’ in the
passed data. Additionally, it is recommended PV programmers use active scripts (ASP, PHP,
etc.) to parse the data sent by the MSR, as MSR data is commonly dynamic and unique to the
card being swiped.
38599-01 RevE
12
3/11/2014
®
ScanVue Web Browser Client
Running the Browser Client (Kiosk Mode)
The browser will default to the HomeURL specified and expects to find a web page at
that location on the web server to load as the default web page.
Slideshow
When the PV is not actively being used by a store customer, a ‘slideshow’ should be
displayed to prevent static image burn-in on the LCD screen and attract customers to the
unit. A ‘slideshow’ (which is a changing sequence of images) can be tailored to
advertise sales or specials, display co-op advertising, show store information or simply
give instruction on using the PV to the customer. This slideshow also serves to attract a
customer to the display.
At a minimum we recommend an alternating 2 image graphic sequence that can be as
simple as the image below shown twice, sequentially, in complementary colors. The two
images should be alternated every 5 seconds or so.
JOES HARDWARE
JOES HARDWARE
SCAN HERE
SCAN HERE
One way to implement a slideshow is to create an animated GIF on the home page that
the browser window can load and display. The animated GIF should not exceed 1Mbyte
in size—depending on the complexity of each image in the animated GIF, this could be
up to 20 individual images.
If a more complex slideshow is desired, a simple web-server driven sequence of images
can be implemented on the home page. For example, the home page contains a pointer
to a GIF or JPEG image with a meta-tag in the header specifying how long to display the
page and which page to go to next. An almost infinitely long chain of images or a loop
could be created.
38599-01 RevE
13
3/11/2014
®
ScanVue Web Browser Client
Using the PV
When one of the input devices is activated, an internal device driver converts the ASCII
data read from the input device into a URL for the PV to send to the web server.
Each input device generates a unique URL as described previously. That URL is
opened by the PV’s embedded browser and displayed for the POSTimeout value. The
HomeURL page is the exception – it has no timeout assigned to it. Additional pages
may be linked to, creating an infinitely long chain of potential responses to inputs (up to
the length of the POSTimeout). Once POSTimeout has been reached, the unit
generates a call to the HomeURL again, and the process repeats itself.
Implementation note: To bypass the POSTimeout, set its value to 0. This implies all
‘final’ pages in any sequence of pages resulting from an input must specify a return to
HomeURL explicitly in their meta tags. Given the obvious potential for error, for rapid
deployment, this is discouraged.
Review of Rules for Implementing a Web Server Application

Once the home page loads, control resides primarily with the web server application.
The PV’s page display will persist until the either web server directs it to another
page, a new URL is generated by scanning a barcode, pressing a pushbutton or the
POStimeout value is exceeded in which case it will return to the homepage.

If the optional Screenblank timeout is used, it should be set to some time longer than
you expect to be viewing a single page (longer than POStimeout) to prevent getting
stuck on a page and burning the screen. This function is analogous to setting the
screen-saver timeout on your desktop computer. It causes the display to blank,
which defeats the customer attraction of a slideshow. Note: The LCD display is not
warranted against burn-in by the LCD manufacturer or IEE.

Fastest response time for loading HTML pages will be seen when the pages are
converted to 320x240 pixels (¼ VGA) before presentation to the browser window.
Full VGA (640x480 pixel) pages will load but only the top left quadrant of the page
will be displayed and the page may load slower due to any added graphics
processing required.

Scanning a barcoded item generates a URL with the SKU or UPC# merged with the
scanner prefix and suffix specified. This unique URL can be used to lookup and
retrieve the specific items properties from a table.
For example; the URL http://mysite/pricelookup/123456B.html will be directed to the
mysite domain, pricelookup directory. The application will retrieve the price and
description data for item 123456B, format it and display its contents in the browser
window. In this example URLprefix = /mysite/pricelookup; URLsuffix =.html and the
item SKU or UPC barcode = 123456B.

Pushing one of the 4 pushbuttons generates a URL with the pushbutton number
merged with the btPrefix and btSuffix specified. The pushbuttons are numbered 1 to
4 from left to right when viewing the unit upright from the front.
38599-01 RevE
14
3/11/2014
®
ScanVue Web Browser Client

Always run a slideshow during the PV’s idle time. An animated GIF may be the
easiest way to implement a slideshow. Many large animated GIFs may not be
desired as they do consume system memory and require space and CPU time for
decompression. As always with web-based software, test and evaluate the results
for practicality in your environment.

If both Event Start and Event End modes contain 0000000F (this is a bitmap
indicating all 4 buttons are activated), a start event will be generated when a button
is pressed and an end event generated when the button is released. The time
interval between a press and a release can be measured. If only a single event is
required when a button is pressed, set Event End to 00000000.
Page Load Response Time
The speed at which new pages load is mostly a function of your network. The browser is
defaulted to a 1/2 second delay (mode bdelay=0 set in UnitConfig) between barcode
scans to prevent multiple fast scans hanging the PV. We recommend testing and
changing this number to between 0 and 5 (additional seconds) to obtain the best
response. In any case, a page will not load in under ½ second from the time any input
completes. MSR devices may not begin outputting data until they complete their
internal data conversion of all tracks scanned on the swiped card. This may add 1 or 2
seconds to the response time.
Page Load Errors
If a page load fault is detected on the HomeURL page, the screen will cycle between an
error page and the logo continuously until it can successfully retrieve the HomeURL
page.
All other pages will generate an internal browser error page. Although IEE has modified
these pages, they are no replacement for a good active script and a graphic. We
recommend using an active scripting language to handle all pages, providing a
programmatic solution for page lookup errors. An example of this is contained in the
php scripts shipped with the unit (found in /var/www/iee). Of course, embedding the
initial pages in the PV at that directory eliminates part of the problem by ensuring those
pages will serve even if the network is temporarily down.
38599-01 RevE
15
3/11/2014
®
ScanVue Web Browser Client
Appendix A
Demo Barcodes
SAVE CONFIGURATION
RETURN TO FACTORY DEFAULTS
DEMO IMAGES
38599-01 RevE
16
3/11/2014
®
ScanVue Web Browser Client
MORE DEMO IMAGES
Ferrari Animation
38599-01 RevE
17
3/11/2014