WashMax Category

Contents of WashMax
1. Carwash Interfaces (How to interface with various car wash makes...)
2. Teller Interfaces (How to interface with various teller models)

WashMax

Articles about the various WashMax and iConnect Online products and services.

About Cold Card Activation

Cold Card Activation allows you to have WashMax Market cards that are assigned to a marketing program, but not yet functioning. This allows you to have the cards sitting on a display where customers can grab them, but stolen cards will not work. A store clerk must activate the card upon purchase.

Cold Card Activation is driven by a program on the Site Server called Cold Card Activator (CCA). It sits in the tray (a blue card with ice and a check mark) until a card is swiped. The application comes pre-installed on recent Site Server images, and may be added to an existing device. A mag-card reader for the Site Server must be purchased along with a license for the application.

When a card is swiped the input display pops up over the normal Code-a-Wash or EPG display:

The clerk enters information via the touch-screen.

Each of these three input fields may be configured as not shown, shown but not required, or shown and required. They can all be turned off, allowing swiped cards to be activated without any input at all. Here's the settings screen:

If a card is swiped but the back-end WashMax Onsite service, which handles the actual processing, is not connected it shows:

Other failures also show with this red screen. Any error screen can be closed or will go away on its own after several seconds.

Cards are active and available for immediate use on the first bay of the site where activated. Other sites/bays will take a few minutes.

Two WashMax Flex Program Reports are available for card activation. (Sample screen below.) Also, the Key details screen shows when the card was activated, and any other available detail (clerk ID, initial value, initial usage count).

By requiring the clerk to enter their ID at activation, and using the WashMax reports, clerks can be rewarded for signing up customers.

Any number of different marketing programs can be activated. You create the programs on WashMax and pre-assign groups of cards to each program. When the card is swiped for activation, it already "knows" which program it belongs to. Different card art-work or packaging can be used to distinguish the cards on display.

Adam Fanello

About Site Controllers

The Activa Site Controller and WashMax Site Controller is the general name for a device at a car wash location that hosts Intelio (and sometimes Ryko) provided software, other than the Activa itself. It is frequently called an "edge" or a "caw", although these designations no longer fits very well.

These platforms have been replaced by the Site Server for new and replacement installations.

A bit of history...

NEMA/6102

The first Site Controller utilized a Nagasaki 6102 motherboard and was enclosed in a large NEMA rated box. The model is commonly called a NEMA or a 6102. The early versions ran Red Hat Linux 9 (RH9), but replacement hard drives switched to running Fedora Core 5 (FC5). On the SOC, you will thus see the platform for edges running on this model labeled as 6102 RH9 and 6102 FC5.

Minibox

The second generation/model of edge was run an an iTuner MiniBox. It also ran Fedora Core 5 (FC5) as the operating system. These are listed on the SOC as a Minibox FC5 platform.

Here's where things start getting complex...

Sys1 / Sys2 CAW

The third generate of edge does not, in fact, have a hardware platform. This is where the Site Controller name began. Ryko provided a hardware box, produced by Sys Technologies, that was designated a CAW-iC. The CAW-iC runs Windows XP Embedded with Cygwin as the operating system, and Ryko's Code-a-Wash, EPI Server, and other applications. It also runs VMware's VM Player, which can run two virtual machine (VM) edges. This became Intelio's Site Controller platform. Even when the Ryko applications aren't needed, this platform may be used simply to run the edge VMs. This hardware platform may also be called Sys1 and uses the CAW1 flash imager. (The CAW2 flash imager is known to work on the Sys1 most of the time.) The motherboard is model GA-945GCMX-S2.

Around the beginning of 2009, Ryko began shipping a new revision of the CAW-iC which looked the same as the old one but had a new motherboard model GA-G31M-S2L. This is designated the Sys2 and requires the CAW2 flash imager. (Later CAW flash imagers also work, up to CAW5.)

Sys3 CAW

This model never shipped.

Sys4

Beginning in June 2009, Intelio began working directly with Sys Technologies and has produced the Sys4 box with the latest GA-G31M-ES2L rev 1.x motherboard. It has a different front panel than the older models, no CD-RW drive, and replaces the modem card with two additional Ethernet ports. For the first time, this hardware is a dual-purpose device. It can be imaged with the CAW4 or CAW5 flash imager and operate as such a CAW-iC, with the Ryko applications and edge VMs. Alternatively, it may be imaged with the ehost1 flash imager, whereby it operates as an edge host device.

It is important to understand that the Sys4 box is just a piece of hardware. Intelio has leveraged this same piece of hardware to serve two different functions. The ehost and caw devices run entirely different operating systems, serve different (but overlapping) purposes, and are managed in different ways. (The ehost platform has been discontinued.)

Back of a Sys4 box

Sys5

In late September 2009, Sys Technologies began delivering a box with GA-G31M-ES2L rev 2.0 motherboard. The main difference is that the on-board Ethernet chip changed from Realtec to Attansic (owned by Atheros). The outside looks identical to a Sys4, but requires the CAW5 flash imager.

In Q2 2010, Ryko began shipping a Sys5 CAW iC, but with a different case. In spite of the case difference, this is still a Sys5.

CAW model Site Controller

The "caw" model Site Controller is also called the Merchandise Site Controller, because it is the only model that can interface with a store Point of Sale (POS) system to issue wash codes. Because it runs the EPI Server, it is also required if the site has a Ryko coinbox (AMTT, AMTT-CS, or Enteract) or multiple Intelio Activa tellers.

Ethernet Adapters

Every caw has a primary Ethernet port around the middle of the back panel, among the USB ports. This is the network uplink port and is shipped set to automatically obtain a dynamic IP address. It may be reconfigured from within Windows XP.

On the Sys4 and Sys5 boxes, there are two additional Ethernet adapters:

Auxiliary Connection 1 is located nearest the primary port and is preconfigured to IP 192.168.111.20.
Auxiliary Connection 2 is located nearest the outer edge of the box and is preconfigured to IP 192.168.112.20.

These adapters can used to connect other equipment, such as Moxa nPort serial device servers for carwash communication. By convention, a Moxa for bay 1 should have a last octet of .21, bay 2 should have .22, etc. A network switch may be added to support more than one device. The edge(s) must be configured with the address you choose for the Moxas. You may also just place Moxas on the site's network, along with the caw via the primary port, and not use these auxiliary connections.

Ehost model Site Controller

This platform has been discontinued, but there are still a few in service.

The ehost (AKA: ehostess) is a device running the CentOS 5.3 Linux operating system that has been modified by the OpenVZ virtualization system. Unlike the virtual machines (VMs) of WMware on the caw, the ehost runs a single kernel that has been split into multiple operating system instances (all CentOS). Just to confuse matters, an instance is synonymously called a Virtual Private Server (VPS), Virtual Environment (VE), or container. In any case, each VPS runs an Intelio edge. This approach is very light weight, allowing for many edges to run on a singe ehost. (The maximum number of edges is untested, but may be as high as eight.)

The ehost does not run any Windows or Ryko applications. It is simply a hardware host for WashMax edges.

Ethernet Adapters and Moxas

The Sys4 box has three Ethernet ports.

ID	Location	IP Address	Netmask	Suggested Use
eth0	Center of back panel among USB ports	dynamic	dynamic	uplink
eth1	Card slot nearest eth0	192.168.111.20	255.255.255.0	teller Moxa
eth2	Card slot nearest outer edge of box	192.168.112.20	255.255.255.0	car wash Moxa

When an edge is running in a VPS, it will default to find a Wash Select II at 192.168.111.21 and an AUTEC, Belanger, or Istobal at 192.168.112.21. This of course only works for a single bay site. The network can be setup in whatever makes sense for the site, including plugging everything into the site network and not using eth1 and eth2, or plugging a network switches into these ports to accommodate multiple devices.

Configure the Ethernet adapters by logging into the ehost as root and using the command:
nw config [ifc] [static|dhcp] [ipaddr] [netmask] [gateway] [default] [dns]
The parameters in brackets may be left off, in which case the script will prompt for details.

Configure a Moxa nPort by logging into the ehost as root and using the moxaconfig command:
Usage: moxaconfig <eth-adapter>
Where: <eth-adapter> is eth0 eth1 or eth2

Bootstrapping

As with all Intelio devices, you configure it by logging in as root and running ./bootstrap.sh. The script will prompt you for an edge number to add to the host. Enter it, and the scripts will create the new VPS and automatically run its bootstrap. When complete, allow it to reboot as normal; it will return you to the ehost where another edge can be added.

If an edge needs to be added after the initial bootstrap is completed, login to the ehost as root and run
/home/intelio/script/install/createEdge.sh <edge#>
Replacing <edge#> with the edge number to add.

Adam Fanello

About Site Servers

Activa Site Server and WashMax Site Server are two names for a device at a car wash location that hosts Intelio (and sometimes Ryko) provided software, other than the Activa itself. It's name is sometimes shortened to sserv. The Ryko iServer and Sheetz Car Wash Server (cws) are variants.

A bit of history...

The Site Server is a direct descendant of the older Site Controller line, and picks up its numbering scheme where the Site Controller left off (at five).

Models

Hardware	BIOS Settings	Network Locations
Sys1 (same case as Sys2) Gigabyte GA-945GCMX-S2 motherboard Intel Celeron CPU @ 2.8 GHz (Benchmark 334) 1 GB RAM 3.5" 80 GB HDD Dial-up modem	Press DEL at bootup to enter CMOS setup Power Management Setup -> AC Back Function = Full-On. Press F12 at bootup for boot menu. Select Hard Drives and then USB-HDD0 to boot flash imager.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: N/A Auxiliary Connection #2: N/A Modem: In expansion card slot. Not used.
Sys2 (same case as Sys1) Gigabyte GA-G31M-S2L motherboard Intel Celeron 430 CPU @ 1.8 GHz (Benchmark 529) 1 GB RAM 3.5" 80 GB HDD Dial-up modem	Press DEL at bootup to enter CMOS setup Power Management Setup -> AC Back Function = Full-On. Press F12 at bootup for boot menu. Select Hard Drives and then USB-HDD0 to boot flash imager.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: N/A Auxiliary Connection #2: N/A Modem: In expansion card slot. Not used.
Sys3 (Ryko only) Biostar G31-M7 TE motherboard Intel Celeron E3300 @ 2.5 GHz (Benchmark 1676) 1 GB RAM	Press DEL at bootup to enter CMOS setup Advanced -> SuperIO Configuration -> Restore on AC Power Loss = Power On Boot -> Hard Disk Drives -> Press '-' to move USB device to the top Press F10 and Enter to Save & Exit.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: N/A Auxiliary Connection #2: N/A Modem: In expansion card slot. Not used.
Sys4 (same case as Sys5) Gigabyte GA-G31M-ES2L rev 1.x motherboard Intel Celeron 430 CPU @ 1.8 GHz (Benchmark 529) 1 GB RAM 3.5" 80 GB HDD Two PCI Network Interface Cards	Press DEL at bootup to enter CMOS setup Power Management Setup -> AC Back Function = Full-On. Press F12 at bootup for boot menu. Select Hard Drives and then USB-HDD0 to boot flash imager.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Add-on card nearest motherboard. (Center of three NICs.) Auxiliary Connection #2: Add-on card nearest outer edge of case.
Sys5 (same case as Sys4) Gigabyte GA-G31M-ES2L rev 2.0 motherboard Intel Celeron 430 CPU @ 1.8 GHz (Benchmark 529) 1 GB RAM 3.5" 80 GB HDD Two PCI Network Interface Cards	Press DEL at bootup to enter CMOS setup Power Management Setup -> AC Back Function = Full-On. Press F12 at bootup for boot menu. Select Hard Drives and then USB-HDD0 to boot flash imager.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Add-on card nearest motherboard. (Center of three NICs.) Auxiliary Connection #2: Add-on card nearest outer edge of case.
Sys6 Intel D945GCLF2D motherboard Intel Atom 330 CPU dual-core @ 1.60 GHz (Benchmark 635) 1 GB RAM 3.5" 80 GB Western Digital HDD PCI Network Interface Card Optional external USB Ethernet interface	Press DEL at bootup to enter CMOS setup Advanced / Peripheral Configuration: -> Serial Port = Enable -> Parallel Port Port = Disable -> Audio = Enable -> On-board LAN = Enable Advanced / Drive Configuration: -> ATA/IDE Mode = Native -> S.M.A.R.T. = Enable Power: -> After Power Failure = Power on -> Wake on LAN = Power on Boot -> Boot to Removable Devices = Enable -> Boot to Network = Disabled -> USB Boot = Enable -> Boot USB Devices First = Enable Automatically boots a flash imager when inserted.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Sole add-on card. Auxiliary Connection #2: Blue TrendNet USB device (optional)
Sys7 Jetway NC94-510-LF motherboard Intel Atom D510 CPU dual-core @ 1.66 GHz (Benchmark 661) 1 GB RAM 3.5" 80 GB Western Digital HDD Realtec Dual NIC PCIe Network Interface Card	Insert flash drive in USB port. Press DEL at bootup to enter CMOS setup. Advanced BIOS Features - Hard Disk Drives - - Page Down to put SATA:WDC below USB FLASH Integrated Peripherals - Onboard SATA Function - - SATA Run Mode Configuration = Compatible - Onboard Super IO Function - - Onboard Floppy Controller = Disabled - PWR Status After PWR Failure = Always On	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Port labeled CH1 on add-on card. Auxiliary Connection #2: Port labeled CH2 on add-on card.
Sys8 Intel D525MW motherboard Intel Atom D525 CPU dual-core @ 1.80 GHz (Benchmark 717) 1 GB RAM 3.5" 160 GB Western Digital HDD PCI Network Interface Card See Fix Site Server Sys8 Serial Port.	Press F2 at bootup to enter CMOS setup Advanced / Peripheral Configuration: -> Serial Port = Enable -> Parallel Port Port = Disable -> Audio = Enable -> On-board LAN = Enable Advanced / Internal Chipset Drive Configuration: -> Configure SATA as = IDE -> S.M.A.R.T. = Enable Power: -> After Power Failure = Power on -> Wake on LAN from S5 = Power on Boot -> Boot to Removable Devices = Enable -> Boot to Network = Disabled -> USB Boot = Enable -> Boot USB Devices First = Enable Automatically boots a flash imager when inserted.	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Sole add-on card. Auxiliary Connection #2: N/A
Sys9 Jetway NC94-525-LF motherboard Intel Atom D525 CPU dual-core @ 1.80 GHz (Benchmark 717) 2 GB RAM 3.5" 160 GB Western Digital HDD Intel Gigabit Dual NIC PCIe Network Interface Card	Insert flash drive in USB port. Press DEL at bootup to enter CMOS setup. Advanced BIOS Features - Hard Disk Drives - - Page Down to put SATA:WDC below USB FLASH Integrated Peripherals - Onboard SATA Function - - SATA Run Mode Configuration = Compatible - Onboard Super IO Function - - Onboard Floppy Controller = Disabled - PWR Status After PWR Failure = Always On	Local Area Connection: Center of back panel among USB ports. Auxiliary Connection #1: Port labeled CH1 on add-on card. Auxiliary Connection #2: Port labeled CH2 on add-on card.

Images

Images are snapshots of a hard drive content that is cloned onto each hardware device to act as the starting point. The images have names of the format <image-class><highest model supported><variant><revision> <company> <date>. For example, "sserv7Rh Ryko 2010-08-05". The fields are:

<image-class> is usually sserv for a Site Server, although Sheetz's is cws, which stands for Car Wash Server.
<highest model support> the highest hardware model number that the image works on. Images are usually backwards compatible.
<variant> is optional. If none is given, then the image is Intelio's baseline. "R" is used for Ryko Code-a-Wash, "S" is Ryko iServer.
<revision> each time the image is updated, the image letter is increased.
<company> is the company that produces the image.
<date> is the date that this revision was released.

The master list of all Site Server images is on the SiteServer page of Intelio's internal wiki.

sserv3 image for Sys3

The Sys3 box is the currently shipping hardware from Ryko. It was forked from Intelio's sserv7h image and is PCI compliant.
Note: The iVisor application's reporting service requires login name "reporting" with password "reporting".

sserv6 image for Sys6

The sserv6 image is obsolete because it is not PCI compliant. Only use sserv7.

The sserv6 image was built for the Sys6 hardware platform. It runs Windows XP Professional, VMware Server (replacing VMplayer on caw images) supporting up to three edge virtual machines. It is otherwise equivalent to the CAW images.

sserv7 image for all models

With sserv7, the image has built rebuilt from the ground up to be PCI compliant. It is backwards compatible to the Sys1 hardware platform, runs Windows Embedded for POS 2009, VMware Server, EPG, ClamWin anti-virus, and auto-logins as a non-administrative user. It may also run all of the normal Ryko Code-a-Wash applications. Radiant Epsilon may be installed on it.

sserv8 image for all models

The sserv8 image has updated drivers to work with the Sys8 platform. It is backwards compatible to the Sys1.

Ethernet Adapters

Every Site Server has a primary Ethernet port around the middle of the back panel, among the USB ports. This is the network uplink port and is shipped set to automatically obtain a dynamic IP address. It may be reconfigured from within Windows, where it is labeled Local Area Connection. There are one or two additional Ethernet adapters, depending on configuration. The following table describes all of the network connections that you will find in Control Panel / Network Connections on a freshly imaged sserv:

Name in Windows	IP Address	Netmask	Recommended Use
Local Area Connection	dynamic	dynamic	uplink
Auxiliary Connection #1	192.168.111.20	255.255.255.0	teller Moxa @ 192.168.111.21
Auxiliary Connection #2	192.168.112.20	255.255.255.0	car wash Moxa @ 192.168.112.21
Intelio VPN	dynamic	dynamic	do not alter
VMware vmnet1	192.168.110.1	255.255.255.0	do not alter
VMware vmnet8	192.168.109.1	255.255.255.0	do not alter

The Auxiliary Connections on the add-on cards and/or USB adapter can used to connect other equipment, such as Moxa nPort serial device servers for carwash communication. By convention, a Moxa for bay 1 should have a last octet of .21, bay 2 should have .22, etc. A network switch may be added to support more than one device. The edge(s) must be configured with the address you choose for the Moxas. You may also just place Moxas on the site's network, along with the Site Server via the primary port, and not use these auxiliary connections.

Carwash Interfaces

How to interface with various car wash makes and models

AUTEC interface with WashMax

The WashMax site controller connects with an AUTEC car wash PLC via an adapter called a PPI MultiMaster. This adapter converts the RS-485 signals used by the car wash's PLCs to RS-232. The RS-232 end may be connected directly to an Intelio Site Server, directly to the serial port or via a Serial Device Server (ex: Moxa nPort 5110).

PPI MultiMaster Switch Settings:

The PPI MultiMaster has eight dip switches on the side. Hold the device so that you can read the labels on the LED. To the left of the dip switches, on the case, it is labelled 1 on top and 0 below.
Set switch #5 up, in the direction of the 1 label on the case. Set all other switches down, in the direction of the 0 label on the case.

Configuration with a Moxa:

For a Moxa nPort 5110, use a null-modem adapter.

Moxa settings:

TCP Server Mode
Serial port settings:

Baud: 19200 baud
Parity: None
Data Bit: 8
Stop Bit: 1
Flow Control: None
UART FIFO: Enabled

Set the IP address to something that works on the network. If connected into the Site Server's Auxiliary Connection #2, the car wash's IP is typically 192.168.112.21. Set this same IP in WashMax Onsite.

Configuration via COM1 Serial Port

See How to communicate to car wash through COM1 serial port.

Adam Fanello

Belanger interface with WashMax

Overview

The Belanger Vector and FreeStyler car wash models offer limited capability to report faults to WashMax.
Older WashMax site controller models may connect directly to a Belanger controller via an RS-232 cable. This is out of favor due to limitations however. The favored hardware configuration involves connecting a serial device server, such as a Moxa nPort, to the Belanger controller and to the site's Ethernet network or a Site Server's Auxiliary Connection #2.

Hardware connections

Mount the Moxa nPort near the Belanger controller and connect it to the site's Ethernet network. Use a standard serial cable to connect to Moxa to port ??? on the Belanger controller. Depending on the Belanger controller model, a null-modem adapter may be needed:

Model	Null-Modem Adapter with nPort DE-311	Null-Modem Adapter with nPort 5110
E-300	yes	no
E-410	yes	no
E-1063	no	yes

Serial Device Server configuration

When using a device server, it must be configured as:

Old scheme: 192.168.1.54 (Use 192.168.1.64 for a second bay.)
sserv Auxiliary Connection #2: 192.168.112.21
If this IP does not work for the site's network, any other address may be used but Intelio site controller must be configured with the alternative address.

Run as a TCP Server listening on port 4001
The inactivity timeout must be disabled .
Serial side set to 9600 baud, 8 bit data, 1 stop bit, no parity, and no flow control.

Edge Settings

The edge should find the Moxa if it's at one of the normal IP addresses for a Belanger Moxa. (As specified above.) If something else is used, you must edit /home/intelio/conf/site.properties and set belanger.ip.host to the IP address. The edge app must be restarted for it to take effect.

Adam Fanello

Istobal interface with WashMax

Overview

The Istobal M series car wash models offer the capability to report faults to WashMax.

Hardware connections

Mount a serial device server, such as the Moxa nPort, inside the Istobal controller. Connect it to the site's Ethernet network and to via serial cable to Istobal board A9 connector X9. Depending on the device server used, a null-modem adapter may be needed. (The Moxa nPort DE-311 requires it, the nPort 5110 does not.)

Detailed instructions are in attached at the end of this article.

Serial Device Server configuration

When using a device server, it must be configured as:

Old scheme: 192.168.1.54 (Use 192.168.1.64 for a second bay.)


        sserv Auxiliary Connection #2:  192.168.112.21
        If this IP does not work for the site's network, any other address may be used but Intelio site controller must be configured with the alternative address.


     Run as a TCP Server listening on port 4001 and set Force transmit to 75 ms.

     The inactivity timeout must be disabled . 
     Serial side set to 2400 baud, 8 bit data, 1 stop bit, no parity, and no flow control.


Edge Settings
The edge should find the Moxa if it's at one of the normal IP addresses  for an Istobal Moxa. (As specified above.) If something else is used,  you must edit /home/intelio/conf/site.properties  and set istobal.ip.host to the IP address.  The edge app must be restarted for it to take effect.
Configure the Istobal Controller

     Turn power on to A9 (controller board)
    Wait for it to boot up.
    Press the 0 button twice.
    On the "Enter access code" screen shown, enter 2003.
    On the Main menu screen:
    
        Scroll down by pressing 0. You will see a second screen with 7 - communications.
    
    Press 7.
    The next screen shows: 1 - local connexion, 2 - remote connexion, etc
    Press 1.
    The next screen shows: 1.1 serie connexion // NOT installed
    Press E. The next screen shows 1- printer, 2 - computer, 3 - not installed 

    Press 2.
    To return, press C repeatedly to back up to the top screen. 


Adam Fanello
Nu-Star interface with WashMax
Overview
The Nu-Star Comet II model can report a few faults to WashMax via simple relays.


Hardware
The hardware needed is a  Kit 108 I/O Relay Board connected to a Serial Device Server such as the Moxa NPort. These can be mounted in an Activa base along with a network switch.  A diagram at the end of this article shows how to wire the I/O relay board to the Nu-Star PLC.

Serial Device Server configuration
When using a device server (ex: Moxa nPort), it must be configured as:

     Run as a TCP Server listening on port 4001.
     Serial side set to 9600 baud, 8 bit data, 1 stop bit, no parity, and no flow control. 

Adam Fanello
PDQ car wash interface with WashMax
Overview
The PDQ LaserWash, G5, M5, and Tantem car wash models have an optional  PC for the PDQ Site Management System. This can send status to Intelio's  edge. 


Hardware Connections
The PDQ SMS computer must be connected to the same LAN as the Intelio  Site Server. It aught to have a static IP address so that it can be  found and configure, but this does not appear to be required.


WashMax Server Configuration
Intelio support personnel only: Login to the customer account at www.washmax.com, click on Management, and Edit the site. Set the correct car wash make and model and Save.

Edge (v4) Configuration
Configure the edge eth1 network to a static IP address. (Login as root, and run the command: nw config eth1 

Select the correct configuration profile. If you need to reselect, login as intelio and run script/install/select_profile.sh 
The  correct car wash model must be selected, otherwise the wrong alerts  will be generated.


WashMax Onsite (v5) Configuration
Open the web UI, click Configure, and select correct PDQ car wash model for the appropriate bay(s). Then Restart the service.

PDQ SMS Configuration

    From the Site Server, open Internet Explorer and enter the IP address of the PDQ server.
    Login. owner - 12345, or PDQ Eng - 83340. 

    Enter the Site Management System setup page. (Click Setup ->SMS links.)

    
        Set the Pulse Time to 10 minutes.
        Set the URL to the static IP address for the edge VM (if using one, v4) or the site server (v5).
        Set the port to 8790.
        Click the Test SMS Server button. You should see a message received in the edge's log.
        Upon success:
        
            Check the Enable Site Management System checkbox.
            Click the Submit button.
        
    

Adam Fanello


Teller Interfaces

How to interface with various teller models
Activa interface and configuration
The Intelio Activa Virtual Attendant has a dedicated section in this knowledge base. Please read the Activa category for information.

Adam Fanello
Enteract interface and configuration
The Ryko Enteract Virtual Attendant is nearly identical to the Intelio Activa. Most of the information in the Activa category of this knowledge base applies to the Enteract as well. Please reference the Activa category for information about the Enteract.

Adam Fanello
Wash Select II interface and configuration
WashMax can work with the Unitec Wash Select II teller.
The Wash Select II and POS 4000 manuals are attached to the end of this article.

Hardware Interface
Configuration a Moxa:
For a Moxa nPort 5110, use a null-modem adapter.

Moxa settings:


    TCP Server Mode
    Serial port settings:
    
        Baud: 9600 baud
        Parity: None
        Data Bit: 8
        Stop Bit: 1
        Flow Control: None
        UART FIFO: Enabled
    

Set the IP address to something that works on the network. If connected into the Site Server's Auxiliary Connection #1, the teller's IP is typically 192.168.111.21. Set this same IP in EPG on the setting's Unitec tab.

Teller Configuration
Setup Generic Terminal Mode with extensions enabled.
Enable "Accept Proprietary".

Works best when washes are defined with the lowest end wash as wash type 1, with prices increasing with higher wash types.
Adam Fanello




Powered by KnowledgeBuilder

WashMax Category

Table of Contents

WashMax

About Cold Card Activation

About Site Controllers

A bit of history...

NEMA/6102

Minibox

Sys1 / Sys2 CAW

Sys3 CAW

Sys4

Sys5

CAW model Site Controller

Ethernet Adapters

Ehost model Site Controller

Ethernet Adapters and Moxas

Bootstrapping

About Site Servers

A bit of history...

Models

Images

sserv3 image for Sys3

sserv6 image for Sys6

sserv7 image for all models

sserv8 image for all models

Ethernet Adapters

See Also

Alerts (Comprehensive list)

Production of Intelio Marketing Cards

Carwash Interfaces

AUTEC interface with WashMax

PPI MultiMaster Switch Settings:

Configuration with a Moxa:

Configuration via COM1 Serial Port

Belanger interface with WashMax

Overview

Hardware connections

Serial Device Server configuration

Edge Settings

Istobal interface with WashMax

Overview

Hardware connections

Serial Device Server configuration

Edge Settings

Configure the Istobal Controller

Nu-Star interface with WashMax

Overview

Hardware

Serial Device Server configuration

PDQ car wash interface with WashMax

Overview

Hardware Connections

WashMax Server Configuration

Edge (v4) Configuration

WashMax Onsite (v5) Configuration

PDQ SMS Configuration

Teller Interfaces

Activa interface and configuration

Enteract interface and configuration

Wash Select II interface and configuration

Hardware Interface

Configuration a Moxa:

Teller Configuration