ISD Software Release tes EPS Ruby/Sapphire/Topaz Suite Version EPSPAK 2.04.06 Release Level HPV-20 (Dell) Version HPV-20 (Dell Rev. 4) Version HPV-20 (V950) Versions Production 4.03.03 or higher 4.03.03 Rev. 4 or higher 5.01.04, 5.05.00 or greater SMS Version 1.09.13 iorder Kiosk Version 1.01.03 GSD Version 2.1 Loyalty Version 5.0 V900/V920 VIPER Version 4.02 or 4.03 GemPro CPU Configuration CPU-6 Base Change Version 164 Shift Configuration Ruby-Only 3-Shift Ruby/Sapphire, Sapphire/Topaz 3-Shift/12-Shift Previous Production Version 2.04.05 Reference Set EPS Reference Set: Version 2.04 Release Date August 28, 2014 Publication Date February 24, 2015
Contents Attention ----------------------------------------------------- 3 New In This Release: 2.04.06------------------------------ 4 Resolutions ----------------------------------------------- 4 New In Previous Release: 2.04.05 ------------------------ 4 New In Previous Release: 2.04.04 ------------------------ 5 New In Previous Release: 2.04.03 ------------------------ 8 New in Previous Release: 2.04.02 ----------------------- 11 Installation Options ---------------------------------------- 19 Upgrade Summary ------------------------------------------ 20 Minimum Requirements ----------------------------------- 33 Fuel Hardware Peripherals Supported ------------------ 35 Ruby/Sapphire Options Supported----------------------- 51 Important Information------------------------------------- 58 2
Attention SMS Report Configuration The SMS Import > Report Configuration and SMS import > Grouplist is NOT supported in EPSPAK 2.04.03. If the TOOLS > Import Configuration Data function is used to import the Report Configuration or Grouplist, this result in a failure to print several reports as part of the Topaz Day Close. All reports printed on the Topaz Close Day MUST be configured via Sapphire Configuration Manager > Report Manager > Report Configuration. Configuration Change The 12-Shift report install option has been removed from Ruby-Only installations. The 12-Shift report option is only available for Ruby/Sapphire sites. te about the Software If the current HPV-20 image does not meet the required versions listed in these release notes, then this version requires re-imaging of the HPV-20. If proceeded without re-imaging HPV-20, the installation may have unpredictable results. The required versions can be found on the front page of these release notes. Topaz Installation For installing the Topaz, you must see the following: Upgrade Summary section in these Release tes. VASC Bulletins 0210_004 and 0210_003 available on the VeriFone Premier Web Portal in the EPSPAK Sapphire and Topaz areas. Topaz Hardware and Software Installation Guides are available on the VeriFone Premier Web Portal at Petro Downloads > Topaz > Topaz: Other Documentation. Topaz Configuration See the Installing Topaz section of these release notes for additional configuration steps required for the Topaz to communicate with the EPS. 3
New In This Release: 2.04.06 RESOLUTIONS Dispenser Card Readers Ruby/Sapphire/Topaz Occasionally, when a customer pressed the payment key together with receipt prompting before fueling at the DCR and "Receipt Prompt before sale" was set to "Y", no fuel was dispensed and a receipt printed with customer information. This was corrected. New In Previous Release: 2.04.05 RESOLUTIONS Dispenser Card Readers Network Ruby/Sapphire/Topaz 1. Previously, the volume preset was not working on Dresser Wayne dispensers due to loyalty being used as a qualifier for the Fast Credit transaction. This was corrected. 2. Previously, the Wayne DCR keypad was not accepting the number of digits. This was corrected. Previously, there were problems with updating the card table when the new card table had different number of entries than the old table. This was corrected. 4
Sapphire Sapphire Management Suite (SMS) Previously, the POP by Card Type credit card names were not being abbreviated in SMS. This was corrected. New In Previous Release: 2.04.04 ENHANCEMENTS Network Ruby/Sapphire/Topaz Debit Fees Fees for Debit transactions are now supported. Manager Topaz Deals Interim Mix & Match feature extends the current Mix & Match capabilities in certain applications until they get to a version with full expanded Mix & Match capabilities. Support for interim Mix & Match will be available only on the Topaz platform. The following are main specifics regarding Interim Mix & Match. Configuration and Reporting is same as existing Mix & Match feature. Back Office: Ethernet (IP) connection with a Sapphire PDK Interface NOTE: Gemcom is not supported. POS: Topaz Only. Use the Sapphire Management Suite version that is bundled with your Sapphire Suite Number of Mixes: 200 Number of Items: 10,000 (50 per Mix) Number of Matches or Deals: 200 5
Number of Department Matches: 10 See Deal > Configuration Manager > Sapphire Management Suite documentation on the VeriFone Premier Portal for setting up Mix & Match Deals. RESOLUTIONS Car Wash Ruby/Sapphire/Topaz Previously, the tax reports were not matching the Department Reports if the last car wash PLU included multiple taxes. This was corrected. Loyalty Network Sales 1. Previously, when a cash prepay was fully dispensed, loyalty discount was given, claimed inside, the transaction did not complete and the receipt was missing the a cash line, and then the discount is also applied to next transaction. This was corrected. 2. Previously, when EPS loyalty was involved in a Mannatec transaction, it did not complete. This was corrected. 3. Previously, when EPS Loyalty was part of a Full Service Preset transaction, the Enter Amount was prompted twice. This was corrected. 4. Previously, when a generic loyalty transaction was suspended, in some instances, multiple loyalty discounts could occur. This was corrected. 1. Previously, the POS was dispensing fuel more than the balance of the prepaid card balance. This was corrected. 2. Previously, when a transaction involved a prepay, loyalty, and a SVS card, the PPG price calculated and displayed on the pump was incorrect and allowed additional fueling. This was corrected. Previously, when a PLU or department was entered for a Mix, it was not added to the list. This was corrected. 6
Network Ruby/Sapphire Previously, when a fuel prepay was sent from the Ruby workstation, the Pump ID was not in the message to the network. This was corrected. Network Reports Network Sapphire 1. Previously, in some instances, a message sent from the Sapphire to an external device, it was being blocked by the Fortigate. This was corrected. 2. Previously, EPICS data was not sent out correctly for non-blending sites with SMS configuration. This was corrected. 3. Previously, EPICS data sent the incorrect amounts for manifolded tanks. This was corrected. 1. Previously, the tax reports were not matching the Department Reports if the last car wash PLU included multiple taxes. This was corrected. 2. Previously, the payee name was not printed in the SMS Money Order Report for money order transactions and the Money Order Reports on the Topaz EOD were not printed completely. This was corrected. Topaz Previously, when a preauthorization was completed from the Topaz, the POP PINpad prompted for the debit fee, and Yes was selected, the sale completed but the side bar displayed the fee as if it were collected and the cash drawer did not open. This was corrected. Reports Previously, the DCR Statistical Report on the Topaz EOD Report printed inconsistent values. This was corrected. 7
New In Previous Release: 2.04.03 ENHANCEMENTS Dispenser Card Readers Ruby/Sapphire Wayne The application now includes Wayne protocol efficiency enhancements for Ovation ix red, Ovation ix blue board, QCAT, and Helix dispensers. Sales Topaz PLU t Found A new feature has been added to disallow 'PLU not found' sale on the Topaz. Currently, if the PLU t Found Department parameter is set to 0, the Topaz prompts the user to select a department from a list of all configured departments. A new Sales Configuration parameter has been added that determines whether to prompt for a department on each PLU not found sale. If this property is disabled and the Sales Configuration > Plu t Found Department parameter is 0, the Topaz disallows the PLU sale and does not prompt the user for Plu not found department to be used on the item during the transaction. RESOLUTIONS Dispenser Card Readers Ruby/Sapphire/Topaz Previously, DCR keypad was not accepting the expected number of digits for alternate loyalty ID. This was corrected. Loyalty 1. Previously, after the customer pressed Yes to Generic Loyalty and swiped their card, the DCR displayed PUMP IS ON even though the 8
loyalty host sent an empty display text field message not to display anything. This was corrected. 2. Previously, the wrong product code 300 was sent in a loyalty transaction. This was corrected and now the product code 400. 3. Previously, when a cash prepay transaction was completely dispensed, the ticket level discount was given and it came due inside. After it was claimed, the finalization did not happen and the transaction receipt did not have a cash line with total. The discount was then applied to the next transction. This was corrected. Sales Previously, a reprinted proprietary transaction receipt contained only header information. This was corrected. Sales Ruby/Sapphire 1. Previously, the credit prepay amount was not displayed on the customer display. 2. Previously, when Minimum Ticket Purchase Amount was selected for a car wash PLU Promo, a double discount was given for the car wash promo. This was corrected. Sapphire Management Suite Sapphire Previously, the grouplist.xml in SMS did not have entries for FP Hose and FP Hose Running Reports in the groupsmasterlist element.this was corrected. System 1. Previously, after a power outage the Sapphire was not reconnecting to the Money Order Device. This was corrected. 2. Previously, the Money Order Payout was not working on the Topaz and Money Order totals were missing from the reports. 3. Previously, the Sapphire could not access the Gemcom fueltots dataset. This was corrected. 9
Loyalty Topaz Previously, the alarm message redialing host changed to LOYLT COMMS- RETRYING on the Topaz. Network Reports 1. Previously, the Topaz partial authorization was allowing the customer to fuel out the prepay amount on a credit prepay. This was corrected. 2. Previously, Bad Transaction Data message displayed from a transaction that included a PLU with an applied fee on the Topaz. This was corrected. \ 3. Previously, after changing the fuel prices, the Topaz was not sending the Epics message to the EPS. This was corrected. 1. Previously, negative departments sold with positive fees on the Topaz had the fee amounts subtracted within the department report. This was corrected. 2. Previously, the DCR Statistics Report on the Topaz Close Daily Report was displaying incosnsistent details. This was corrected. 3. Previously, the POP Discount Report and the POP Discount Def Report was not printed in the Topaz Shift Report. This was corrected. 4. Previously, the Topaz Monthly and Yearly Reports were not printing all the data and gave an error Error while getting report from sapphire. This was corrected. 5. Previously, all Topaz reports were missing the SVB# in the header information. This was corrected. 10
New in Previous Release: 2.04.02 ENHANCEMENTS Car Wash Ruby/Sapphire/Topaz Loyalty The POS no longer prompts for car wash when a loyalty card is swiped at the DCR and the customer selects the pay inside key indicating pay inside. Only pay outside transactions initiated at the DCR would prompt for car wash. Network Preauthorization The fueling position is now sent to the network with the outdoor preauthorization request. Sales Smart Grade Prompting Smart Grade Prompting reduces the number of questions asked of the customer by meeting certain criteria. Inside cash prepay transactions should be prompted for grade select only if all of the following are met: Reports The customer qualifies for a promotion that has an associated maximum gallon limit. The cash prepay amount divided by the lowest price of all discounted fuel grades less any discounts is above the applicable maximum gallon limit. Topaz Flash Reports The Dispenser Report is now supported for the current period report. 11
RESOLUTIONS Car Wash Ruby/Sapphire/Topaz 1. Previously, the last car wash option was not displayed on the DCR. This was corrected. 2. Previously, car wash discount printing was inconsistent outside and inside. This was corrected. Dispenser Card Readers Loyalty 1. Previously, the DCR Receipt printed INCL 0.xxx /G DISC even though POP Discount was not in the transaction. This was corrected. 2. Previously, with POP Discount set at Coupon Only, the coupon did not print at the DCR. This was corrected. 1. Previously, when Generic Loyalty was enabled and a price change was performed, it was possible for the POS to bootfix. This was corrected. 2. Previously, there was a rounding issue of total PPG discount amount sent to the EPS that caused incorrect Loyalty Report totals. This was corrected. 3. Previously, the POS was not capturing loyalty refund information when a bad response was sent for a refund authorization. This was corrected. 4. Previously, the Ruby terminal bootfixed when [ENTER] was pressed three times or [EXIT] was pressed at Slide Loyalty Discount Card or Enter Account Number. This was corrected. 5. Previously, EPS Loyalty was rejected at Graphic DCRs. This was corrected. 6. Previously, the manual credit MOP was used for a postpay fuel sale with EPS Loyalty, the ticket level discount was not included and no EPS Loyalty information printed on the receipt. This was corrected. 7. Previously, when EPS Loyalty was combined in same transaction with Mix n Match, loyalty was not completed. This was corrected. 8. Previously, when a transaction included a manual fuel department item, a prepay fuel sale, and loyalty, the loyalty did not complete and no loyalty information printed on the receipt. This was corrected. 9. Previously, when a loyalty card was swiped outside and the Pay Inside button was pressed, the loyalty was not finalized or printed on the receipt inside. This was corrected. 12
Network Reports Sales System 1. Previously, there was a potential card read failure when inconsistent data was sent to the EPS from the POS terminal. This was corrected. 2. Previously, Commercial Fueling Network (CFN) dual legacy cards were not processing at DCR. This was corrected. 3. Previously, Mannatec cards with PIN starting with zero as the first digit, the PIN was not accepted on the Ruby. This was corrected. 1. Previously, when using Full Service Attendant, the card totals were incorrect in the Proprietary Report. This was corrected. 2. Previously, the N/W Product Report was incrementing network amounts as cash amounts. This was corrected. 1. Previously, when a Gift Card was purchased and charged to House Account, the House Account receipt did not include the account information line on the receipt. This was corrected. 2. Previously, when a Prepay with Merchandise for total amount equaled to $9999.99 and was tendered with Credit, t enough funds Press enter to continue was displayed and the transaction was voided. This was corrected. 3. Previously, when Ignore MOP Conflict was set to Yes, a dispenser was prepaid for an amount using a Cash MOP, but tendered with Credit, an incorrect amount and subtotal amount printed on the receipt and the transaction was allowed to dispense over the authorized amount. This was corrected. 4. Previously, the incorrect Full Service attendant name was printed on receipts. This was corrected. 5. Previously, there could be problems with following transactions after the receipt number returns to 0001. This was corrected. Previously, fuel price acknowledgement events were not properly sent to external servers. This was corrected. 13
Network Ruby Previously, when a prepay Mannatec transaction was canceled at the DCR, it caused error messages to display on the Ruby terminal. This was corrected. Reports Previously, the amount and volume were not appearing on the Ruby POP Discount Report for prepay transactions. This was corrected. Previously, the N/W Product Report included loyalty cash transaction amounts. This was corrected. Sales 1. Previously, if the customer did not have enough points for a discount, the Ruby did not send a completion message to the network. This was corrected. 2. Previously, an HH8 Error displayed on the Ruby at finalization of a Prepay Underrun due to an incorrect product code sent to the network. This was corrected. 3. Previously, a double prepay on single fueling point required to exit out of Sales to allow for additional prepays. This was corrected. 4. Previously, when a preset command sent to a Gilbarco dispenser was not accepted, the prepay sale potentially could have been lost. This was corrected. Sapphire Generic Loyalty Sapphire 1. Occasionally, the loyalty network would return a gallon limit for the fuel discounted by a PPG discount. If the customer declined the discount, the POS still enforced the gallon limit. This was corrected. 2. Previously, when there was loyalty with a Fast Credit with Merchandise transaction, the messages were different between the Ruby sites and the Topaz sites. This was corrected and now the message sequence is the same on both terminals. 3. Previously, when a loyalty card barcode was scanned on a Topaz with Sapphire Generic Loyalty enabled, a Card not registered error displayed. This was corrected. 4. Previously, with EPS loyalty disabled and generic loyalty enabled, generic loyalty points were not deducted for postpay transactions. This was corrected. 14
5. Previously, there was an inaccurate PPG discount when fuel prices were changed during a loyalty transaction. This was corrected. 6. Previously, the POS was not capturing loyalty refund information when a bad response was sent for a refund authorization. This was corrected. 7. Previously, the Ruby terminal bootfixed when [ENTER] was pressed three times or [EXIT] was pressed at Slide Loyalty Discount Card or Enter Account Number. This was corrected. 8. Previously, Generic Loyalty was not included in the Topaz Loyalty Reports for Loyalty Outside. This was corrected. 9. Previously, Loyalty Details were not printed for an underrun cash prepay transaction on the Topaz. This was corrected. 10. Previously, with both EPS and generic loyalty enabled at a site and with generic loyalty prompting set to prompt first, there was a potential scenario where the prices would fail to roll back for the generic loyalty transaction. This was corrected. 11. Previously, a fully dispensed cash prepay transaction that is claimed inside reports twice in the Generic Loyalty totals. This was corrected. 12. Previously, there was no response from the Topaz keyboard during fuel grade selection in a Generic Loyalty transaction. This was corrected. 13. Previously, a DCR Cash Acceptor Prepay with qualified EPS loyalty and Generic Loyalty and the prepay fully dispensed, the customer was not notified to see the cashier for a refund. This was corrected. 14. Previously, when a prepay EPS Loyalty transaction with no Generic loyalty was performed, the final receipt contained Generic Loyalty information. This was corrected. 15. Previously, with EPS and Generic Loyalty enabled, the DCR receipt was not printing EPS Loyalty information when using Mannatec. This was corrected. 16. Previously, when a gallon limit was not specified by the Loyalty Host, the POS used a gallon limit from the uninitialized data. This was corrected. Sapphire Management Suite (SMS) Previously, HTTP notifications failed in certain instances. This was corrected. System 1. Previously, the Gemcom Create function removed existing PLUs instead of adding to them. This was corrected. 2. Previously, Sapphire NewPro serial ports were unavailable when accessed from a JAVA application. This was corrected. 15
3. Previously, a potential negative number in a zero field in the TLOG could cause a NaN error in the transaction log for a refund transaction involving a Food Stamp method of payment. This was corrected. 4. Previously, Error 511 displayed when Gemcom attempted to retrieve fuel totals from the Sapphire Site Controller. This was corrected. Loyalty Topaz 1. Previously, when EPS Loyalty and POP Discount by Card type was combined in a transaction, a POP discount was not given on the Topaz. This was corrected. 2. Previously, when the generic loyalty was swiped and the product grade list was displayed on the Topaz, the product grade list continued to display after [Exit] was pressed. This was corrected. 3. Previously, the prepay by volume amount calculation used the full price instead of the loyalty PPG price on the Topaz. This was corrected. 4. Previously, during a postpay transaction using a POP Discount and Generic Loyalty, the Topaz was unable to close out transaction after payment card swipe. This was corrected. 5. Previously, when an EPS or Generic additional loyalty discount was given, the Topaz receipt printed Total and Cash zero amounts. This was corrected. 6. Previously, the Topaz was not giving a POP Discount ticket level discount for a postpay transaction with EPS loyalty enabled. This was corrected. 7. Previously, the Generic Loyalty details were printed incorrectly for a Topaz prepay credit transaction. This was corrected. 8. Previously, the Topaz gave a double EPS Loyalty ticket level discount from VCMG when the Loyalty on Total parameter was set and Generic Loyalty gave a PPG discount. This was corrected. 9. Previously, the Topaz gave a EPS ticket level discount before and after the Total key press causing a double discount. This was corrected. 10. Previously, when a Generic Loyalty line item discount was applied, the Topaz did not apply the EPS Loyalty discount. This was corrected. 11. Previously, a line item was not receiving the Generic Loyalty discount on the Topaz. This was corrected. 12. Previously, when the Exit key was pressed at the grade selection prompt during a Generic Loyalty transaction, the Topaz locked up at the Swipe or Scan the Generic Loyalty Card prompt. This was corrected. 13. Previously, with a fully fueled cash prepay transaction with generic loyalty enabled and EPS loyalty disabled on the Topaz, there was a possibility 16
that a very large negative ticket level discount could be applied which would result in the customer being overcharged. This was corrected. 14. Previously, a prepay credit transaction with generic loyalty set to prompt first was sometimes not completing and caused a Credit Unavailable or Host Unavailable message on the Topaz. This was corrected. 15. Previously for certain fuel product configurations, the Topaz did not approve the pump with the EPS Loyalty PPG discount. This was corrected. Network Sales 1. Previously, when a single or dual CFN (Proprietary) cards was swiped, the Topaz displayed Card not Allowed. This was corrected. 2. Previously, the POP by Card Type Table was not being updated on the Topaz when accessed through Network Manager. This was corrected. 1. Previously, after a Mix n Match or a deal was deleted from SMS, the Topaz Mix n Match or deal transactions failed to commit even though the Topaz was still logged in Sales. This was corrected. 2. Previously, the Topaz printed more than one receipt for the Cash MOP. This was corrected. 3. Previously, the [Enter] and [Arrow] keys were not working on the Topaz for grade selection. This was corrected. 4. Previously, an MOP Conflict error message occurred when Manual Entry was used with a fuel prepay on the Topaz. This was corrected. 5. Previously, the Topaz Discount Percent key gave a dollar discount instead of a percent discount. This was corrected. 6. Previously, if a cashier closes out immediately after performing a fast credit preauthorization and before the transaction is fully dispensed at the pump, an additional open cashier entry gets created in the database when the fueling is eventually completed. Cashier reports do not balance. This was corrected. 7. Previously, the Topaz would approve a fast credit transaction if the preauthorization information was not stored in database. This was corrected and now it is stored in the database before approving. 8. Previously, there was an inaccurate PPG discount when fuel prices were changed during a loyalty transaction. This was corrected. 9. Previously, the In-House transaction could complete on the Topaz without the In-House account number. This was corrected. 10. Previously, with Ignore MOP conflict set to N at Fuel Manager > Site Parameters > Fuel Site Parameters, a partially dispensed fast credit 17
transaction with debit or a prepaid card cannot be completed on Topaz. The only option is to cash out the due sale. This was corrected. 11. Previously, the Topaz printed the EPS ticket level amount, the Total amount, and the Cash amount as positive amounts instead of negative amounts. This was corrected. Sales System 1. Previously, when a fast credit with merchandise transaction was performed on one Topaz, it could not be settled if the same type of transaction was performed on the same DCR from any other Topaz. This was corrected. 2. Previously, when a Fast Credit prepay was initiated with cash, but tendered with credit MOP and the Fast Credit prepay at DCR was canceled before fueling, the Topaz was not sending a $0.00 collect. This was corrected. 3. Previously, POP Discount was not applied for prepay and postpay transactions on the Topaz when the MOP was credit. This was corrected. 4. Previously, when a fuel prepay was entered as cash and tendered as credit, the POS sent a sale completion and not a preauthorization to the network. This was corrected. 5. Previously, when a SVC card with partial amount was used in a prepay fuel and merchandise transaction, the dispenser was authorized and the transaction was not charged to the card. This was corrected. Previously, loyalty transactions with coin changer gave twice the change due on the Topaz. This was corrected. 18
Installation Options Sapphire Installation Options Option Code logserver wuice wut7e mgdelta eps Description This option code is used to assign the IP address of a customer provided server that will receive system log messages from the Sapphire and Topaz. This option code is used when the Western Union ICE6000 Terminal is connected via IP. This option code is used when the Western Union T7e Terminal is connected via serial port. This option code is used when the MoneyGram/ TravelersExpress Delta Network Terminal is connected via IP. This option code is used to configure the Secondary Network IP Address. Topaz Installation Options eps logserver This option code is used to configure the Secondary Network IP Address. This option code is used to assign the IP address of a customer provided server that will receive system log messages from the Sapphire and Topaz. Supported POS Terminals Ruby SuperSystem, Sapphire, Topaz 110, and Topaz XL NOTE: Sites can no longer have both Ruby and Topaz terminals using the same Sapphire. 19
Upgrade Summary NOTE: See VASC Bulletin 0508-001 for checking the reliability of downloaded software releases using MD5 files. NOTE: Gemstall can no longer be used to upgrade a workstation to a controller or a controller to a workstation. In both cases, a complete reload is required. Overview Ruby-only Sites A full new installation of Ruby software must be performed. After completing the steps of Saving Sales Data and Settings by backing up all sales data and settings, use the procedure outlined in Ruby Site New Installation. Sapphire Sites NOTE: When installing EPSPAK software at a site that includes at least one Topaz, see the Addendum for EPSPAK 2.00.00 and above that provides additional required steps for the Topaz, Sapphire, and HPV-20 software installation. Do NOT use the Addendum for Ruby-only and Ruby/Sapphire sites. Upgrading to EPSPAK 2.04.06 is a full new installation of both GemPro, and NewPro: Sapphire sites must use the Sapphire Site New Installation procedure with EPSPAK_V2_04_06_Suite_Production_CD.exe. The package contains: The GemPro zip file named EPSPAK_V2_04_06_GemPro_Production_Software.exe, which is suitable for Gemstall using the procedure outlined in the entry following titled Sapphire Site GemPro Installation Burn the contents of the Suite CD onto a disc for v2.04.06. NOTE: See VASC Bulletin 1210_002 for CD file structure changes. Topaz workstations are upgraded from the same CD containing the Sapphire installation: EPSPAK_V2_04_06_Suite_Production_CD.exe. Topaz installation follows Sapphire installation. See Topaz Workstation Installation. The SMS software package in a folder named SMS v1.09.13 for EPSPAK 2.04.06, which contains setup.exe. The following entries in this Upgrade Summary section are used by Sapphire sites: 20
Sapphire Site New Installation: Provides an overview details on how to download the Sapphire software package, and separate and identify its components for installation. GemPro Installation for Sapphire Sites: Provides details on Gemstalling the GemPro files. NewPro Installation for Sapphire Sites: Provides details on making a CD-ROM disk that will install NewPro through the HPV-20. Topaz Installation for Sapphire Sites: Topaz software is included with the NewPro software and is installed after Sapphire NewPro. SMS Installation: Provides details on installing Sapphire Management Suite on your PC. Sapphire GemPro Board Upgrade to CPU-6 The Sapphire Site Controller GemPro board software is to be upgraded from CPU-5 to CPU-6 if it has not already been upgraded. This software upgrade enhancing the operating system is accomplished at Gemstall time, and the process also converts the CPU-5 Ruby Card to a CPU-6 Ruby Card. Only the software is upgraded. The hardware remains the same. NOTE: Failing to perform this procedure correctly could damage your system. This software upgrade is for Sapphire or Sapphire/Topaz sites only. It is NOT for Ruby-only sites. Documentation on the CPU-6 upgrade may be found on the VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide in the PDF file CPU-6 Installation for Sapphire Base 160. Warning There are now two.vfg upgrade files. If you are upgrading on a Sapphireequipped site, you must use Relsapp.vfg both to Gemstall the application on the Sapphire Site Controller GemPro board and to Gemstall the application on all Ruby terminals. If you are upgrading on a non-sapphire site, you must use Rel.vfg to Gemstall. Use of the wrong file for your site will prevent the upgrade from completing. Questions? If you have any questions while upgrading, the VeriFone Technical Support Center is available for assistance 24 hours a day, 7 days a week at 888-777-3536. Saving Sales Data and Settings Saving Data Use these steps to begin any onsite installation of a new application: 21
1. Close the current report periods. Run Close Cashier Totals and Print Cashier Report at the controller Ruby terminal. In a multiterminal system, run Close Cashier Totals and Print Cashier Report at each workstation also. 2. Run and print close period reports: In a 3-shift configuration, run Close Shift (Close Period 1), Close Daily (Close Period 2), Close Monthly (Close Period 3) and Close Yearly (Close Period 4). Print these reports. In a 12-shift configuration, run Close Shift (Close Period 1) and Close Daily (Close Period 2). Print these reports. 3. Run the Payroll Report using the Close option. Saving Settings List out all of the site s configuration parameters and data. To print out your settings, access each of the following functions and [List] their contents. Keep the printouts for use at the end of the upgrade. Manager mode: All functions Fuel Manager mode: All functions Reports mode: Configuration Maintenance mode: All functions Network Mgr mode: All functions Car Wash Mgr mode (if applicable): All functions Backup of Data and Settings Perform a complete system backup. Ruby Site New Installation After completing the steps of Saving Sales Data and Settings by backing up all sales data and configuration settings, continue here. 1. Double-click on EPSPAK_V2_04_06_Ruby_Production_Software.exe to extract the Ruby files into the C:\GEMSTALL\EPSPAK\V2_04_06\Ruby directory for Gemstalling with Rel.vfg. 2. If HPV-20 is installed, remove Ruby Cards from all Ruby terminals. 3. Place the controller Ruby terminal into SYSMGR mode by pressing and holding (with a ballpoint pen point or paperclip) the forwardmost button on the card holder on the right side of the terminal. 4. Once the terminal is in SYSMGR mode, start Gemstall on your PC. a. Go to the C:\GEMSTALL directory noted above and open the Rel.vfg file. 22
b. Run the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading. c. Run the Install function. Make sure the RAM is erased. 5. Prior to starting the POS after installation, check and verify the following: The serial cable between the POS and the V900 is connected. The V900 is powered up and has received a successful download. Failure will result in a long timeout (longer than 8 minutes) for the POS to completely start up. 6. Replace any Ruby Card removed and reboot the controller Ruby terminal. NOTE: If an update of your operating system is required, the Ruby terminal prompts for confirmation and automatically updates the system. The system then reboots the Ruby terminal as necessary. When the update has been completed successfully, the system reboots, and the updated version displays. 7. Restore all sales data and settings except for settings in Fuel Manager. The Fuel Manager settings must be manually restored using the printouts that you made earlier in Saving Sales And Settings Data. (te that you may want to save the printouts for future reference.) NOTE: Be aware that you are changing to a new and upgraded application and that: If you have a [REST IN GAS] soft key, it will have to be manually restored. Various Ruby configuration menu names may not be restored because they have changed in name or location, or have been eliminated. 8. Make the change to NACS 3-digit product codes: Product Code Conversion te that, as part of the changes made in the EPSPAK application, it now supports the NACS 3-Digit product codes. When restoring the site s departments and PLUs, each item must change its product code to match the new product code from the NACS product code listing. In order to accomplish this, there are a variety of ways to convert the products. Additionally, there a multiple ways in which PLUs and Departments can be setup. Product Code Setup To set up product codes, do one of the following: Assign each PLU and each department a specific product code. Then when a PLU is sold, it will use the product code assigned to that PLU. And 23
when a department is sold it will use the product code assigned to that department. Assign each PLU a product code of zero. If this option is chosen, then each PLU must be assigned a department and that department must have the corresponding NACS product code. Then, when a PLU is sold, it will use the product code assigned to the department that the PLU is associated with. NOTE: Do NOT assign a product code of zero to a department. Converting Product Codes You can use one of the following methods to convert product codes: The product codes can be converted manually once the PLU and Departments are pushed over to the POS by utilizing the POS and selecting each individual PLU and department. The product codes can be converted in the Ruby Manager application. This is a manual process, but the user interface in Ruby Manager allows this to be done quicker then selecting each item on the POS. The product codes can be converted by the customer using their back office product. This process will vary depending on the capabilities of the back office software program. The product codes could be provided by the sites price book provider. Since these product codes are the NACS standard, this data is no longer unique for the POS or the application and, as part of the standard price book that the store receives, they may have the ability to send the items, PLU's, and Departments already assigned with the NACS product codes. Obviously, it is very important that this conversion be correct during the install, so it will be very important that you work closely with the site, manager, or the party responsible for the customer. 9. If you have a workstation Ruby terminal, remove any Ruby Card and place the workstation Ruby terminal into SYSMGR mode by pressing and holding (with a ballpoint pen point or paperclip) the forwardmost button on the card holder on the right side of the terminal. 10. Once the workstation terminal is in SYSMGR mode, run Gemstall. a. Open the Rel.vfg file for the version being installed. b. Run the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading. c. Run the Install function. Make sure the RAM is erased. 11. Replace any Ruby Card and reboot the workstation Ruby terminal. NOTE: If an update of your operating system is required, the Ruby terminal prompts for confirmation and automatically updates the system. The system then reboots the Ruby terminal as necessary. 24
When the update has been completed successfully, the system reboots, and the updated version displays. 12. If there are other workstation Ruby terminals on the site, repeat steps 9, 10, and 11 for every other workstation. Sapphire Site New Installation NOTE: When installing EPSPAK software at a site that includes at least one Topaz, see the VASC Bulletins 0210_004 and 0210_003 that provides additional required steps for the Topaz, Sapphire, and HPV-20 software installation. Do NOT use the Addendum for Ruby-only and Ruby/Sapphire sites. Overview Sapphire GemPro, Sapphire NewPro, Topaz, and SMS for this release are all contained in the self-extracting zip file EPSPAK_V2_04_06_Suite_Production_CD.exe. This file may be downloaded or distributed on a CD disk. In either case, double-click on this file and choose Unzip. The files will be placed in the folder C:\EPSPAK V2.04.06 Suite Production CD. GemPro The GemPro component is EPSPAK_V2_04_06_GemPro_Production_Software.exe. Double-click on it and it will extract to C:\GEMSTALL\EPSPAK\V2_04_06\GemPro where it is Gemstalled using Relsapp.vfg. See GemPro Installation for Sapphire Sites. NewPro The NewPro folders must be burned to the root of a CD-ROM disk for installation. NOTE: See VASC Bulletin 1210_002 for CD file structure changes. NOTE: It may be convenient to place the SMS folder on this CD. The GemPro file does not need to be placed on the CD, although it may be. Whether or not it is placed on the CD, remember to Gemstall from files on your PC s hard drive and not from the CD. See NewPro Installation for Sapphire Sites. Topaz Topaz software is included with the NewPro software and is installed after Sapphire NewPro. See Topaz Installation for Sapphire/Topaz Sites. SMS Sapphire Management Suite files must also be burned to a CD for installation. They may be placed on the CD used to install NewPro or on a CD of their own. 25
See SMS Installation for Sapphire Sites. GemPro Installation for Sapphire Sites This installation uses Gemstall and Relsapp.vfg to install the GemPro software on the Sapphire and on Ruby terminals. NOTE: Always Gemstall GemPro files from your PC s hard drive and not from a CD-ROM disk. After downloading and expanding the Sapphire installation package, go to the directory C:\EPSPAK V2.04.06 Sapphire Production CD, double-click on the file EPSPAK_V2_04_06_GemPro_Production_Software.exe, and choose Unzip. The GemPro files will be unzipped into the directory C:\GEMSTALL\EPSPAK\V2_04_06\GemPro. After completing the steps of Saving Sales Data and Settings by backing up all sales data and configuration settings, continue here to upgrade Sapphire GemPro software for Sapphire sites. NOTE: These are abbreviated instructions. For full details, see The Sapphire Installation Guide available for download from the new VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide. 1. Remove the Ruby Card from the Sapphire Site Controller. 2. Connect the RS-232 cable from your PC to COM 2 of the COM Port Bank 3. Place the GemPro side of the Sapphire Site Controller in SysMgr mode by pressing [+] and [S] on the front panel keypad at the same time for 2 seconds. Release the keys when you hear a short beep. 4. Using the keypad on the front panel of the Sapphire Site Controller, press [1] twice to establish the [Yes] key and [2] twice to establish the [] key. 5. Use the [2] key to answer until the Select SYSMGR Port option appears. 6. Press 1 for [Yes] for Select SYSMGR Port SYSMGR on COM PORT 2 To select the Baud rate of 57600 for Gemstall NOTE: If your PC will not support the high Baud rate, choose 19200. Other questions should be answered with 2 for []. 7. On your PC, start Gemstall. Move to the C:\GEMSTALL directory and then continue to the sub directories for the application, version, and GemPro. Select Relsapp.vfg. NOTE: Gemstall version 2.52 or higher, compatible with USB ports and all Windows versions through Windows XP, should be used at a Baud rate of 57600. The latest Gemstall version is available on the 26
VeriFone Premier Web Portal at Petro Downloads > PC Based Applications > Gemstall. 8. Open the Relsapp.vfg file for the version being installed. a. Run the Edit function. b. At the Sapphire or Ruby prompt, choose Sapphire (controller). c. Continue with the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading. d. Run the Install function. NOTE: Be sure to select the Relsapp.vfg option and Gemstall the Sapphire as a controller of a multiterminal configuration. 9. The Sapphire begins a reboot. To speed up the process, press the [Pause] key on your PC to pause the program before the Sapphire beeps to show the reboot is complete. 10. Once again, repeat the selection of [1] twice to establish the [Yes] key and [2] twice to establish the [] key. 11. Use the [2] key to answer until the Select SYSMGR Port option appears. 12. Press 1 for [Yes] for Select SYSMGR Port SYSMGR on COM PORT 2 To select the Baud rate of 57600 for Gemstall NOTE: If your PC will not support the high Baud rate, choose 19200. Other questions should be answered with 2 for []. 13. Gemstall installs the GemPro software. 14. Remove the Ruby card from the first of up to four Ruby terminal workstations that can work with the Sapphire Site Controller. 15. Connect the PC COM port through a null modem adapter and an RS-232 cable to the controller Ruby terminal s COM 1 port. 16. Place the controller Ruby terminal into SYSMGR mode by pressing and holding (with a ballpoint pen point or paperclip) the forwardmost button on the card holder on the right side of the terminal. 17. Once the terminal is in SYSMGR mode, run Gemstall. a. Open the Relsapp.vfg file for the version being installed. b. Run the Edit function and select Ruby (workstation) at the Sapphire or Ruby prompt. c. Designate the first Ruby as Terminal. 1. The Sapphire uses System Setup on the. 1 workstation terminal to provide managerlevel configuration of the Ruby system to site requirements. 27
d. Continue the Edit function to set the terminal specific requirements such as the correct printer, keyboard, and terminal type for the terminal you are upgrading. e. Run the Install function. 18. In turn, Gemstall any other Ruby workstations with Relsapp.vfg, designating them as Terminal. 2, Terminal. 3, and Terminal. 4 as needed. 19. Prior to starting the POS after installation, check and verify the following: The serial cable between the POS and the V900 is connected. The V900 is powered up and has received a successful download. Failure will result in a long timeout (longer than 8 minutes) for the POS to completely start up. 20. When Gemstall is complete, replace the Ruby Card in the Sapphire Site Controller and reboot by pressing + and R at the same time. 21. Allow the Sapphire to boot up, then replace the Ruby cards in the workstations and power up the workstations. 22. Restore all sales data and settings except for settings in Fuel Manager. The Fuel Manager settings must be manually restored using the printouts that you made earlier in Saving Sales And Settings Data. (te that you may want to save the printouts for future reference.) 23. Make the change to NACS 3-digit product codes: Product Code Conversion te that, as part of the changes made in the EPSPAK application, it now supports the NACS 3-Digit product codes. When restoring the site s departments and PLU's, each item must change its product code to match the new product code from the NACS product code listing. In order to accomplish this, there are a variety of ways to convert the products. Additionally, there a multiple ways in which PLU's and Departments can be setup. Product Code Setup To set up product codes, do one of the following: Assign each PLU and each department a specific product code. Then when a PLU is sold it will use the product code assigned to that PLU. And when a department is sold it will use the product code assigned to that department. Assign each PLU a product code of zero. If this option is chosen, then each PLU must be assigned a department and that department must have the corresponding NACS product code. Then, when a PLU is sold, it will use the product code assigned to the department that the PLU is associated with. NOTE: Do NOT assign a product code of zero to a department. 28
Converting Product Codes You can use one of the following methods to convert product codes: The product codes can be converted manually once the PLU and Departments are pushed over to the POS by utilizing the POS and selecting each individual PLU and department. The product codes can be converted in the Ruby Manager application. This is a manual process, but the user interface in Ruby Manager allows this to be done quicker then selecting each item on the POS. The product codes can be converted by the customer using their back office product. This process will vary depending on the capabilities of the back office software program. The product codes could be provided by the sites price book provider. Since these product codes are the NACS standard, this data is no longer unique for the POS or the application and, as part of the standard price book that the store receives, they may have the ability to send the items, PLUs, and Departments already assigned with the NACS product codes. Obviously, it is very important that this conversion be correct during the install, so it will be very important that you work closely with the site, manager, or the responsible party for the customer. NewPro Installation for Sapphire Sites After backing up your all sales data and configuration settings as described in the Saving Sales Data and Settings section of these Release tes, continue here to install Sapphire NewPro software. The installation CD is made from folders extracted from EPSPAK_V2_04_06_Suite_Production_CD.exe as previously described. 1. Place the installation CD in the V950\HPV-20 PC CD-ROM drive. 2. Power-cycle the V950\HPV-20 PC to transfer the NewPro and Topaz files. 3. Connect your laptop/pc to the SERVICE CONSOLE of the Sapphire Site Controller with an RS-232 cable. 4. Run HyperTerminal to install the NewPro files. NOTE: For full details, see The Sapphire Installation Guide available for download from the new VeriFone Premier Web Connection at Petro Downloads > Sapphire > Sapphire and SMS: Other Documentation > Installation Guide. Upgrading Sapphire Firmware If your application requires you to upgrade the Sapphire Firmware from DK 1.3.0 to DK 1.4.0, you will see the following caution soon after starting Sapphire software installation: 29
CAUTION: This process replaces the firmware in the Sapphire NewPro. This will erase all customer data. Answer no to cancel this process. Follow the prompts to complete the firmware upgrade. CAUTION: This process replaces the firmware in the Sapphire NewPro. This will erase all customer data. Answer no to cancel this process. Proceed with firmware change? <yes or no> y Reprogramming BIOS and Diagnostic Kernel DO NOT INTERRUPT THE PROCESS, OR THE SAPPHIRE MAY BECOME UNUSABLE. ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ >> º Autoflash Program, Version 1.3 º º Copyright 2000-2003 by VeriFone INC. All rights reserved.º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ Preparing to write: System BIOS Version 2.0.3 WARNING -- PRESSING RESET OR TURNING OFF THE POWER DURING THE UPDATE PROCESS WILL RESULT IN INVALID FLASH CONTENTS Flash Memory Map FILE NAME SIZE FLASHED TO bios 0x40000 BIOS device Processing file : bios Flash Programming Succeeded! ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ >> º Autoflash Program, Version 1.3 º º Copyright 2000-2003 by VeriFone INC. All rights reserved.º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** Diagnostic Kernel will be flashed with file dk ** File dk is larger than the DK flashpart! 30
** Remaining 0x6C000 bytes of file dk will be flashed to the beginning of the BIOS flash part. WARNING -- PRESSING RESET OR TURNING OFF THE POWER DURING THE UPDATE PROCESS WILL RESULT IN INVALID FLASH CONTENTS Flash Memory Map FILE NAME SIZE FLASHED TO dk 0xFC0000 DK device dk 0x6c0000 BIOS device Processing file : dk Processing file : dk (BIOS device) Flash Programming Succeeded! BIOS and Diagnostic Kernel versions were successfully updated. Please return the DIAG switch to the down position to restart in the new Diagnostic Kernel and start the application installation process. Please note that you will need to run loadinstallkdi again from the new Diagnostic Kernel. NOTE: These statements repeat until you put the Diag switch down, after which the system reboots automatically. Please return the DIAG switch to the down position to restart in the new Diagnostic Kernel and start the application installation process. Please note that you will need to run loadinstallkdi again from the new Diagnostic Kernel.Rebooting to Linux Installer **** LynxOS is down **** The DK and operating system have been upgraded. Log in again as user install and follow the prompts. Topaz Installation for Sapphire/Topaz Sites After installing Sapphire NewPro software, you will be prompted Do you have a Topaz? Key y, and you will be told to switch the RS-232 cable connected to the 31