DIVA Error List

Error 4.9x.10.6

Cause

DIVA cannot process the data, that has been received over the serial link.

Description

The external device sends data fast and DIVA2 is not ready to process them. Normally this is a software issue, because of not optimised initialisation internally. In most cases the situation is established without any problem, even if some data is lost (clearing buffer). The x above in the main error refers to the affected UART.

How to fix

• As this is normally a temporary problem, no further measures are needed. Possibly the problem is solved in a newer SW version

Error 4.14.25.2

Cause

An error caused by an internal software bug.

Description

How to fix

• Fixed from version 6.80 or later

Error 4.64.30.19

Cause

Audit printer client is on, printer driver must be defined

Description

No printer device is active with activated audit printer client

How to fix

• Choose a valid printer driver in menu 16

Error 4.76.37.18

Cause

transaction memory was full

Description

Operating mode "delete if memory full" enabled in menu and transaction memory was full. In this case transaction and other mesages will be lost.

How to fix

• Disable this mode.

Error 4.64.42.37

Cause

The recp.00 text where the UserID tag is, is too long for the paper settings

Description

The recp.00 text where the UserID tag is, is too long for the paper settings. UserID need at least 10 free characters to be correctly printed!

How to fix

• Verify the recp.00 file text size.

Error 4.64.42.39

Cause

The page settings are missing on the second line of recp.00 file

Description

The page settings are missing on the second line of recp.00 file

How to fix

• Verify the recp.00 file with SN141

Error 4.64.42.41

Cause

Some texts in recp.00, after rending for printing, overrides the maximum line size

Description

Some texts in recp.00, after rending for printing, overrides the maximum line size

How to fix

• Verify the recp.00 file according to the page settings (line 2 of recp.00)

Error 4.64.42.43

Cause

The receipt failed while printing : Paper jammed, sudden printer error

Description

The receipt failed while printing : Paper jammed, sudden printer error.

How to fix

• Verify the printer paper
• Verify the printer status

Error 4.64.42.44

Cause

The receipt cannot be printed : No printer available, no paper, printer doesn't support some features (logo, barcode, etc.)

Description

The receipt cannot be printed : No printer available, no paper, printer doesn't support some features (logo, barcode, etc.). More errors may be given to specify the cause.

How to fix

• Verify the printer connection
• Verify the printer type and its capabilities

Error 4.64.42.45

Cause

More errors may be given, that specifies the cause of it

Description

The recp.00 file has some format error

How to fix

• Verify the recp.00 file with SN141

Error 4.64.47.40

Cause

No SD Card in slot

Description

The logging function for the SD card is not available if the SD card is missing, DIVA ignores all data that should be saved on the SD card. Only a minimum of data is stored in an internal buffer file!

How to fix

• Insert a valid SD Card

Error 1.9.47.45

Cause

Backup file xxxxxxxx.bxx already exists for this day

Description

SD Card logging day data in file xxxxxxxx.txt was deleted

How to fix

• Correct the DIVA date (use NMT or Menu 03.06)

Error 1.9.47.46

Cause

No SD Card in slot

Date error (old/invalid) audit message has detected

Description

Audit message was deleted during SD card recording Save currently not possible

How to fix

• Insert a valid SD Card
• Correct the DIVA date(NMT/Menu 03.06)

Error 4.64.48.29

Cause

DIVA Operating Number not or wrong configured.

Description

Audit Client for offline Transactions is disabled. Set the DIVA Operating Number in valid range before first use. Default value 0 is not a valid number.

How to fix

• Configure the DIVA Operating Number > 0.

Error 4.64.49.4

Cause

Default value (0) of operating number is not valid

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing configuration of the machine number.

How to fix

• Enter a valid operating number in menu 03.05 (not 0)

Error 4.64.49.5

Cause

The server URL is not configured.

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing server URL configuration.

How to fix

• Enter the valid URL menu 20.21.32 or 20.21.00

Error 4.64.49.6

Cause

The server URL is not in a valid format.

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing server URL configuration.

How to fix

• Enter the valid URL menu 20.21.32 or 20.21.00

Error 4.64.49.7

Cause

The server URL is not in a valid format (no host).

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing server URL configuration.

How to fix

• Enter the valid URL menu 20.21.32 or 20.21.00

Error 4.64.49.8

Cause

The server URL is not in a valid format (protocol not supported).

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing server URL configuration.

How to fix

• Enter the valid URL menu 20.21.32 or 20.21.00

Error 4.64.49.9

Cause

Default value (0) of projectID is not valid

Description

SpiderCloudService LOG is unable to transfer the log file because of a missing projectID configuration.

How to fix

• Enter the valid projectID menu 20.21.32 or 20.21.00 (not 0)

Error 4.64.49.37

Cause

The username/password is wrong in DIVA.

The projectID is not valid.

Description

SpiderCloudService LOG is unable to transfer the log file because of wrong configuration.

How to fix

• Correct the settings Project ID, user name and password
• Disable the service if not used

Error 4.64.49.38

Cause

Wrong URL configured in menu 20 for LOG service

The projectID is wrong.

The LOG feature is not enabled on the server for this project.

Description

The LOG service is part of the SpiderCloudServices (spicls). The LOG service is not functional and DIVA will be blocked later if this error situation remains.

How to fix

• Configure correct URL in the menu 20 for the LOG service.
• Correct the settings Project ID, user name and password
• Disable the service if not used

Error 4.14.49.40

Cause

A server internal error occured

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot process the data because a temporary error situation on the server side.

How to fix

• This error condition will disappear if the server becomes available again.
• This error must be fixed on server side.

Error 4.14.49.41

Cause

A required service is temporary unavailable

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot process the data because a required service is temporary unavailable.

How to fix

• This error condition will disappear if the service becomes available again.
• This error must be fixed on server side.

Error 5.8.49.52

Cause

Wrong network configuration

Network problems

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot be reached because of no network connection. The LOG service is not functional.

How to fix

• Correct the network configuration (Ethernet or GPRS)
• Fix the network problems.

Error 5.8.49.53

Cause

Wrong URL configured in menu 20 for LOG service

Wrong network configuration

Wrong DNS configuration

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot be found because of a wrong URL configuration. The EVADTS service is not functional.

How to fix

• Configure correct URL in the menu 20 for the LOG service.
• Correct the network configuration (Ethernet or GPRS)
• Fix the network problems.

Error 5.8.49.53

Cause

Wrong URL configured in menu 20 for LOG service

Wrong network configuration

Server temporary not running or reachable

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot be reached because of a wrong URL configuration. The LOG service is not functional.

How to fix

• Configure correct URL in the menu 20 for the LOG service.
• Correct the network configuration (Ethernet or GPRS)
• Fix the network problems.

Error 5.8.49.54

Cause

Wrong URL configured in menu 20 for EVADTS service

Wrong network configuration

Server temporary not running or reachable

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot be reached (timeout). LOG service is not functional.

How to fix

• Configure correct URL in the menu 20 for the LOG service.
• Fix the network problems.

Error 5.8.49.55

Cause

Wrong network configuration

Network problems

Description

The LOG service is part of the SpiderCloudServices (spicls). The spicls server cannot be reached because of no network connection. The LOG service is not functional.

How to fix

• Correct the network configuration (Ethernet or GPRS)
• Fix the network problems.

Error 7.1.50.26

Cause

SPICLS: No connection to the host for a longer time. The bufferd internal files are yet full. Every audit message will be trashed!

Description

Log data incomplete

How to fix

• Check host communication to SPICLS

Error 4.14.61.10

Cause

The RTC has been reset because of a battery change.

The RTC has been reset because of first power up of this hardware.

Description

The date and time has been reset to 1970-01-01 00:00:00. The user must correct the clock in menu 3.06.

How to fix

• Adjust date and time settings in menu 3.06.

Error 4.64.103.4

Cause

No Hopper has been enabled

Description

No Hopper has been enabled

How to fix

• Check the VOL13.03/04 Hopper 1-4. At least one should be enabled

Error 4.64.103.5

Cause

The Jeton output (13.04) is configured with more than 1 jeton type

Description

Only one value is possible for the 4 Jeton Hoppers.

How to fix

• Check the VOL13.04.53-56 hopper value

Error 4.64.105.5

Cause

Test dispense on disabled Hopper

Description

A test dispense was tried on a disabled Hopper

How to fix

• Check the VOL13.03/04 Hopper 1-4

Error 9.79.115.38

Cause

MDB communication problem: DIVA has detected that the command has wrong checksum and discard the telegram.

Description

In case of occasional occurrence there is no negative consequence as the telegrams are repeated in case of CRC error. If the problem happens frequently, a detailed trace analysis must be made.

How to fix

• frequently occurrence: contact the manufacturer or start MDB trace. You may send the result to the manufacturer or Hug-Witschi support team.

Error 4.64.115.44

Cause

Application are already programmed. Keyfile not accepted.

Description

Limit of applications is done.

How to fix

• Reset all applications with the reset permission card and program the desired application again.

Error 4.64.152.103

Cause

This hardware does not support an interface for coin acceptors with G18 compatible interface.

Description

The coin acceptor payment system in 13.00 requires a parallel interface compatible wit h G18 protocol. Since this hardware does not support such an interface the coin acceptor will not work.

How to fix

• Use DIVA2 with option 206 which has a G18 compatible interface.
• If you have connected a MDB coin acceptor enable the MDB coin changer in menu 13.60 instead of coin acceptor menu 13.00.

Error 4.64.156.19

Cause

DIVA Ingenico mode wrong configured with this Ingenico firmware

Description

It's not a valid combination of Ingenico reader firmware and the actual configured function mode in DIVA menu 13.66.50

How to fix

• use a mode in menu 13.66.50 that is supported by the terminal firmware
• Update the Ingenico terminal to a newer version, that supports the desired mode

Error 4.92.161.5

Cause

No reader connected to the MDB Master connector s4

reader is not setup to MDB correctly

Defective cable

Description

DIVA is trying to find a MDB reader on the appropriate interface (s4 normally). As long as the reader does not startup, DIVA is blocked. After a timeout, the DIVA functions are working and the reader is disabled internally. DIVA shows "failure" operating state.

How to fix

• Connect the reader to the corresponding interface (s4 normally)
• Setup the reader correctly

Error 4.64.161.18

Cause

The reader sends "unknown" credit, DIVA is configured to use the maximum price as credit but there is no price information available, e.g. in host (proxy) mode.

Description

Because of wrong configuration DIVA will not show any credit for this user.

How to fix

• Set the credit in menu 13.62.60.0 to a value not equal to 0.

Error 4.63.161.121

Cause

The reader sends a SESSION_CANCEL_REQUEST command, which is not processed correctly

Description

Due to requested SESSION_CANCEL_REQUEST the Master (DIVA) is sending a RESET command in order to restart the MDB communication.

How to fix

• no fix needed.

Error 4.14.162.6

Cause

The cashless reader returns a answer that has a wrong checksum (CRC). Another reason may be that the reader doesn't follow the level rules, i.e. it pretends to support level 2 but returns a answer in level 1 format.

Description

In case of occasional occurrence there is no negative consequence as the telegrams are repeated in case of CRC error. If the problem happens frequently, a detailed trace analysis must be made.

How to fix

• frequently occurrence: contact the manufacturer or start MDB trace. You may send the result to the manufacturer or Hug-Witschi support team.

Error 4.64.167.100

Cause

The user walked away from the rebook station, or the badge wasn't able to load.

Description

The user didn't took the money on the second reader, or the badge was not able to load the old amount (limit).

How to fix

• Add the amount with a sideload loader like MiniPOS.

Error 4.64.177.6

Cause

Protocol level is wrong configured in the coin changer. DIVA does support only level 3 for coin changer/acceptors.

Description

The protocol is not supported, the changer will not work with DIVA. DIVA will show "failure" on the display.

How to fix

• Adjust the MDB protocol level in the coin changer. Refer to manual of the coin changer.

Error 4.64.177.14

Cause

Scaling factor too low in the changer. This is used to calculate the correct payout and exact change conditions.

Description

The scaling factor is used to calculate the correct payout and exact change conditions. If it is set too low, the changer will not work with DIVA.

How to fix

• Adjust the scaling factor in the coin changer. Refer to manual of the coin changer.
• Use a lower return limit in 13.60.63.

See also

• AN 146: Exact change

Error 4.92.177.27

Cause

No coin changer connected to the MDB Master connector s4

coin changer is not setup to MDB correctly

Defective cable

Description

DIVA is trying to find a MDB coin changer on the appropriate interface (s4 normally). As long as the coin changer does not startup, DIVA is blocked. After a timeout, the DIVA functions are working and the coin changer is disabled internally. DIVA shows "failure" operating state.

How to fix

• Connect the coin changer to the corresponding interface (s4 normally)
• Setup the coin changer correctly

Error 4.92.179.55

Cause

The acceptor is not connected or defective.

Defective cable

Description

DIVA is trying to find a MDB bill validator on the appropriate interface (s4 normally). As long as the bill validator does not startup, DIVA is blocked. After a timeout, the DIVA functions are working and the bill bvalidator is disabled internally. DIVA shows "failure" operating state.

How to fix

• Connect the bill validator changer to the corresponding interface (s4 normally)
• Error happens continuously: Replace bill validator

Error 4.92.180.4

Cause

The acceptor is not connected or defective. If the error occurs at power up, the timeout of DIVA may be too short

Description

How to fix

• Error happens continuously: Replace acceptor
• Error occurs only at power on: nothing (use a DIVA SW 7.60.x or newer)

Error 4.12.249.1

Cause

Changing configuration or data collection in certain situations

Description

The flash file system has corrected small inconsistencies (without loss of data)

How to fix

• Wait for new firmware

Error 3.110.249.20

Cause

The live cycle of the battery (10 years) has been elapsed

Description

The lithium battery powers the RTC and non volatile memory. Both are required for statistics and transaction control. Therefore the DIVA remains in the blocked state so no further transactions are possible.

How to fix

• Send DIVA in for repairing.
• Replace Battery in DIVA2 devices: restart DIVA2 right after replacement to avoid rapid discharging of battery

Error 3.14.249.23

Cause

strong EMC distortion due to bad cable installation or wrong earthing concept.

Software dead lock (only on DIVA not DIVA2 family)

Description

How to fix

• If problem happens often, change the hardware board (Base or Option). Check with support team

Error 3.14.249.24

Cause

strong EMC distortion due to bad cable installation or wrong earthing concept.

Software dead lock

Description

How to fix

• If problem happens often, change the hardware board (Base or Option). Check with support team

Error 4.64.373.70

Cause

The firmware was upgraded (or downgraded) to an incompatible version.

Description

To avoid loosing of the reader keys (permission card) the reader has been blocked.

How to fix

• Download a compatible firmware version.
• Format (14.20)
• Delete all reader keys (e.g. using a Legic global reset card SAM 49).

Error 4.64.373.71

Cause

The serial number of the connected RFID reader has changed.

Description

For security reasons the reader has been blocked.

How to fix

• Connect the reader used previously.
• Format (14.20)
• Delete all reader keys (e.g. using a Legic global reset card SAM 49).

Error 4.64.412.31

Cause

The barcode of the product do not match the product mode

Description

The configuration of VOL8.92 for a product do not match the product mode of VOL8.91. E.g. "EAN" mode is used, but no barcode has been configured.

How to fix

• Check the VOL8.92 configuration of the product
• Check the VOL8.91 product mode

Error 4.64.620.12

Cause

Replay information file info.txt parameter 1 (file version) not matched

Description

Clone replay from SD Card to DIVA will check the info.txt first. Only all parameters (1..5) are valid, the replay process begin. The readout file version of info.txt is not equal to DIVA implemented version

How to fix

• Create a valid clone file for this DIVA version, this will correct the file info.txt

Error 4.64.620.13

Cause

Replay information file info.txt parameter 2 (DIVA version) not matched

Description

Clone replay from SD Card to DIVA will check the info.txt first. Only all parameters (1..5) are valid, the replay process begin. The readout DIVA version of info.txt is not equal to DIVA firmware version

How to fix

• Create a valid clone file for this DIVA version, this will correct the file info.txt

Error 4.64.620.14

Cause

Replay information file info.txt parameter 3 (Client) not matched

Description

Clone replay from SD Card to DIVA will check the info.txt first. Only all parameters (1..5) are valid, the replay process begin. The readout client of info.txt is not equal to DIVA firmware client

How to fix

• Create a valid clone file for this DIVA version and client, this will correct the file info.txt

Error 4.64.620.15

Cause

Replay information file info.txt parameter 4 (Platform) not matched

Description

Clone replay from SD Card to DIVA will check the info.txt first. Only all parameters (1..5) are valid, the replay process begin. The readout platform of info.txt is not equal to this platform

How to fix

• Create a valid clone file for this platform, this will correct the file info.txt

Error 4.64.620.21

Cause

Replay information file info.txt parameter 5 (configuration version) cannot converted

Description

Clone replay from SD Card to DIVA will check the info.txt first. Only all parameters (1..5) are valid, the replay process begin. The readout configuration version of info.txt has a format error.

How to fix

• Create a valid clone file with valid configuration version format (parameter 5)

Error 4.14.1700.5

Cause

An error situation caused by an internal sw bug.

Description

Due to a updated saldo in the system, DIVA likes to inform the Vending Machine about the balance. An internal blocking situation prevents to send the saldo. The central machine controller module is in a deadlock situation.

How to fix

• Reboot DIVA or the Vending Machine

Error 4.14.1700.9

Cause

The machine is currently heating, the door remains open, the machine is currently not available for vends. In case of a communication problem: machine send disable but no enable or DIVA doesn't see the enable command.

Description

You may verify this error in the machine display (announcing a certain error situation). The green status LED on the DIVA controller is continuously on.

How to fix

• Machine measures: close the door (or use the door plug), wait until the water is hot etc.
• communication problem: tracing the serial link and send to the support team for further analysis

Error 4.65.1700.18

Cause

MDB protocol: Machine has more than 100 products or the selection number is related to the absolute spiral, rather than a consequent product index.

Executive protocol: machine sends the price of a product that cost more than 99 cents.

CCI coffee machines: PLU of the product is >99

Description

At each vend, the machine is sending a product number to the DIVA. DIVA needs a valid selection number in order to process the vend. The supported range is between 0 and 99. If the number is >99, the vend is aborted.

How to fix

• If the number is hardwired in the machine firmware, use the mode "selection as price", which can be setup in menu 01. Now the prices in the machine mean the selection number. Start with price 1 for the first product, 2 for the 2nd and so on. Disadvantage: machine shows wrong price in the display
• Use the host mode of DIVA instead of the normal Vending mode: Menu 25 and 13.xx.24 are setup to a proxy. In this mode, the prices and business logic in the DIVA is disabled.
• Machines with configurable selection number like CCI coffee machines: change the designated selection number of the product. Valid range = 0..99

Error 4.65.1700.27

Cause

MDB protocol: Machine sends a ItemNumber in the CASH SALE command which is higher than the configured number of choices in M01.

Description

For each CASH SALE report, the machine sends a product number to the DIVA. DIVA needs a valid selection number in order to store the statistics data. The maximal supported range is between 0 and 99. If the number is out of range the statistics data will be lost.

How to fix

• For MDB: Set the CASH SALE mode to report all products to selection number 0.
• MDB: Set the CASH SALE configuration to "deactivated". The CASH SALE data will be ignored.
• Increase the number of choices in menu M01.
• Machines with configurable selection number: Change the designated selection number of the product.

Error 4.14.1700.43

Cause

Machine's product delivery takes more than 90s

Description

After elapsing the timeout in DIVA2, the product delivery is judged as successful. So even if the delivery failed afterwards, the user cannot get the money back. In case of successful delivery no further issue happens in the timeout situation.

How to fix

• Assuming that the product delivery cannot be shortened, a SW modification in DIVA in order to extend the timeout is needed. Check with the support team of Hug-Witschi about the possibilities.
• Change machine setting in order to reduce the delivery time

Error 4.95.1740.14

Cause

The vending machine does not poll the interface anymore.

Description

The machine should poll the interface cyclic. There was no telegram received for more than 30 seconds. This is a hint for a not properly implemented machine firmware. There are no restrictions for DIVA functionality.

How to fix

• The vending machine manufacturer should fix the firmware.

Error 4.64.1740.15

Cause

The vending machine is wrongly configured to use the price from DIVA, or the DIVA "Ignore selection" is wrongly set.

Description

The vending machine is wrongly configured to use the price from DIVA, or the DIVA "Ignore selection" is wrongly set. Thus, it exists a contradiction in the application.

How to fix

• The vending machine or the DIVA configuraton should be changed.

Error 4.64.1767.30

Cause

The MDB machine does not send a selection number for the vend request (0xFFFF) and DIVA is configured to use the selection number provided by the vending machine (default).

Description

This configuration is not valid. The product will not be sold.

How to fix

• Use the configuration Selection number from price.
• Configure the vending machine to send the correct item number.

Error 4.64.1767.31

Cause

The MDB machine sends a price >65535 and DIVA is configured to use the price as selection number. (default).

Description

This configuration is not valid. The product will not be sold.

How to fix

• Use the configuration Selection number As product no.
• Configure the prices in the vending machine.

Error 4.64.1767.32

Cause

The MDB machine sends a reload value >65535 and DIVA is configured to use the price as selection number. Only possible for special adapted return machines with MDB level 2.

Description

This configuration is not valid. The refund request will rejected.

How to fix

• Use the configuration Selection number As product no.
• Configure the prices in the vending machine.

Error 4.64.1767.40

Cause

DIVA is configured to update the internal statistics with the data received from the vending machine through the CASH SALE command. The machine sends an "undefined" item number.

Description

The CASH SALE report data can not be mapped to the internal satistics counters. The data will be lost.

How to fix

• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".
• If all reports should be mapped to selection number 0 set Selection number = As product no and Price from = DIVA.
• Fix the vending machine firmware.

Error 4.64.1767.41

Cause

DIVA is configured to use "Price from DIVA", "selection as price" and "CASH SALE = Statistics". This configuration is meaningles.

Description

The CASH SALE feature will be disabled and the statistics data will be lost.

How to fix

• Use another configuration.

Error 4.64.1767.42

Cause

The vending machine sends a CASH SALE command with a foreign currency (level 3).

Description

DIVA can not map sales reported in an foreign currency to the internal statistics data. The data will be lost.

How to fix

• Use another configuration in the vending machine.
• Use MDB level 2.

Error 4.64.1767.50

Cause

The cash payment system is connected directly to the vending machine. The machine reports a cash vend (MDB command CASH SALE).

Description

This configuration is not valid because the transaction and statistics data will be lost. All transactions must be reported to the backend system. This is not possible if the machine does transactions on itself.

How to fix

• Connect the cash system directly to DIVA.
• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".

Error 4.64.1767.51

Cause

The cash payment system is connected directly to the vending machine. The machine reports a token vend (MDB command CASH SALE).

Description

This configuration is not valid because the transaction and statistics data will be lost. All transactions must be reported to the backend system. This is not possible if the machine does transactions on itself.

How to fix

• Connect the cash system directly to DIVA.
• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".

Error 4.64.1767.52

Cause

The machine reports a free vend (MDB command CASH SALE).

Description

This configuration is not valid because the transaction and statistics data will be lost. All transactions must be reported to the backend system. This is not possible if the machine does transactions on itself.

How to fix

• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".
• Configure the vending machine to send a vend request to the cashless system (DIVA) for free vends.

Error 4.64.1767.53

Cause

The machine reports a test vend (MDB command CASH SALE).

Description

This configuration is not valid because the transaction and statistics data will be lost. All transactions must be reported to the backend system. This is not possible if the machine does transactions on itself.

How to fix

• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".
• Configure the vending machine to send a vend request to the cashless system (DIVA) for test vends.

Error 4.64.1767.54

Cause

The cash payment system is connected directly to the vending machine. The machine reports a negative vend with cash payout (MDB command CASH SALE).

Description

This configuration is not valid because the transaction and statistics data will be lost. All transactions must be reported to the backend system. This is not possible if the machine does transactions on itself.

How to fix

• Connect the cash system directly to DIVA.
• If the transaction data is not used set CASH SALE configuration to "deactivated" or "statistics".

Error 4.64.1851.14

Cause

The DHP Display software application version is not up-to-date

Description

It's an old display application software version that is installed.

How to fix

• Update the display software, according to the specific documentation

Error 4.64.1851.17

Cause

Using DHP with a CompactLoader Basic configuration is forbidden

Description

Using DHP with a CompactLoader Basic configuration is forbidden

How to fix

• Set VOL16 Keyboard to "None" and Display to "RS232".

Error 4.64.1851.18

Cause

Bad VOL01 versus VOL16 configuartion

Description

CompactLoader Touch (EFT, Noten, Combi) is set as a CompactLoader Basic.

How to fix

• Set VOL1 to CompactLoader Basic instead of CompactLoader Noten.

Error 4.64.1851.19

Cause

Bad VOL16 configuartion

Description

VOl16 is not set for CompactLoader Touch

How to fix

• Set VOL16 as specified

Error 4.64.1853.15

Cause

The technician missed to configure the "Invite a friend" amounts

Description

The technician missed to configure the "Invite a friend" amounts.

How to fix

• Configure the amounts in VOL1

Error 4.64.1853.16

Cause

The technician missed to configure the "Invite a friend" products

Description

The technician missed to configure the "Invite a friend" products.

How to fix

• Configure the products in VOL1

Error 4.64.1853.18

Cause

The machine has not been scanned now, or the entered product entry number is wrong

Description

The "invite a friend product" is/are not available/blocked

How to fix

• Verifiy the entry number in VOL1
• Start the machine scan with VOL4

Error 4.14.1853.21

Cause

The storno operation don't work on DIVA. That's why it is implemented like this.

Description

In the future, DIVA will be able cancel a previous transaction.

How to fix

• Statistics have to be adapted

Error 4.64.1853.22

Cause

The DHP Display software application version is not up-to-date

Description

It's an old display application software version that is installed.

How to fix

• Update the display software, according to the specific documentation

Error 4.64.1853.23

Cause

The RTV configuration of that VM mismatches

Description

The RTV tell DIVA to deliver a blocked or invalid product. DIVA or RTV configuration is wrong.

How to fix

• Check RTV configuration vs VM configuration
• Re-scan the VM

Error 4.64.1856.5

Cause

miniPOS : Load and devalue mode are both disabled

Description

miniPOS : Load and devalue mode are both disabled

How to fix

• Enable one or both mode

Error 4.64.1856.7

Cause

miniPOS : Load amount are not rounded of 100 cents

Description

miniPOS : Load amount are not rounded of 100 cents

How to fix

• Set amounts as amount = N * 100

Error 4.64.1858.6

Cause

CoffeeCorner : Bad VOL16 configuration

Description

CoffeeCorner : Keyboard is not enabled or not as DHP configured

How to fix

• Check VOL16 Keyboard

Error 4.64.1858.7

Cause

CoffeeCorner : Bad VOL16 configuration

Description

CoffeeCorner : Display is not enabled or not as DHP configured

How to fix

• Check VOL16 Display

Error 4.64.1858.10

Cause

The DHP Display software application version is not up-to-date

Description

It's an old display application software version that is installed.

How to fix

• Update the display software, according to the specific documentation

Error 4.64.1858.11

Cause

CoffeeCorner : Bad VOL01 configuration

Description

CoffeeCorner : No function has been enabled

How to fix

• Enable at least one function

Error 4.64.1858.12

Cause

CoffeeCorner : Bad VOL01 configuration

Description

CoffeeCorner : Loader only is not supported in CoffeeCorner

How to fix

• Change to Hug-Witschi -> CompactLoader

Error 4.64.1858.18

Cause

CoffeeCorner : Bad VOL01 configuration

Description

CoffeeCorner : Too many product has been configured within the feature, so that the total is > 100

How to fix

• Check "Coffee", "Dispenser" and "Self" function

Error 4.64.1858.19

Cause

CoffeeCorner : Bad VOL01 configuration

Description

CoffeeCorner : No load amounts has been configured

How to fix

• Check the load amounts of VOL01

Error 4.64.1858.20

Cause

CoffeeCorner : Bad VOL01 configuration

Description

CoffeeCorner : The minimum value for the other amount is > than the minimum fixed load amount

How to fix

• Check the load other amount minimum value of VOL01

Error 4.64.1858.22

Cause

CoffeeCorner : Bad VOL01 or VM configuration

Description

CoffeeCorner : The requested selection number is out of the range configured in VOL01

How to fix

• Check the number of product in VOL01
• Check the selection number in the VM

Error 7.1.1858.32

Cause

CoffeeCorner : The dispenser filling was done

Description

CoffeeCorner : The dispenser filling was successfully completed

How to fix

Error 7.1.1858.33

Cause

CoffeeCorner : The door was never opened

Description

CoffeeCorner : The dispenser filling failed, because the filler didn't open the door.

How to fix

• The door need to be opened

Error 7.1.1858.34

Cause

CoffeeCorner : The dispenser service was done

Description

CoffeeCorner : The dispenser service was successfully completed

How to fix

Error 7.1.1858.35

Cause

CoffeeCorner : The door was never opened

Description

CoffeeCorner : The dispenser service failed, because the technical didn't open the door.

How to fix

• The door need to be opened

Error 4.111.2001.6

Cause

This hardware requires a valid licence for the serial display, but no licence was loaded.

Description

Serial display will not work.

How to fix

• Use a hardware which does not require an extra licence.
• Load the licence for this feature (only possible in factory).
• Disable the serial display in the menu.

Error 4.64.2004.9

Cause

The IrDA interface is configured to the wrong connector.

Another system is configured to the same interface.

The hardware does not have such an interface or it is not supported.

Description

Due to wrong interface configuration the IrDA module is not working.

How to fix

• Configure the correct interface in menu 16.14
• DeLight: the hardware might not support the serial communication through the antenna port. Hardware version 4.20 or newer is required.

Error 4.64.2005.7

Cause

The setup mode was not disabled in the menu after instalaltion of the DIVA. As this mode causes additional load on the GPRS base station, it was automatically disabled.

Description

Setup mode is disabled.

How to fix

• To use the setup mode again it must be reenabled manually in the menu.

Error 4.64.2011.4

Cause

DIVA wants to connect to an old version of Spider (1.0, 1.5) with an incompatible protocol.

DIVA wants to connect to a new version of Spider (Spider 2.0 and newer).

Description

The version of Spider and DIVA are not compatible: Communication is not possible. DIVA remains blocked.

How to fix

• Use a newer version of Spider.
• If you want to connect to a Spider 2.0 or newer, update the DIVA firmware so the protocol can be switched dynamicly to the old version of the protocol.

Error 4.14.2011.10

Cause

network problems, Spider not running

Description

This error appears when DIVA2 a long offline situation. See also: 4.14.2244.43, 5.8.2244.52

How to fix

• Fix the network problem

Error 4.64.2011.14

Cause

Default value (0) of operating number is not valid

Description

Spider communication is not possible. DIVA remains blocked.

How to fix

• Enter a valid operating number in menu 03.05 (not 0)

Error 4.64.2011.15

Cause

Default value (0) of projectID is not valid

Description

Spider communication is not possible. DIVA remains blocked.

How to fix

• Enter the valid ProjectID in menu 16.08 (not 0)

Error 4.64.2011.30

Cause

The configured Project ID is unknown by Spider.

Description

Spider communication is not possible. DIVA remains blocked.

How to fix

• Enter the correct Project ID in menu 16.08 (not 0)
• Add this project to the Spider configuration.

Error 4.64.2011.31

Cause

The username/password is wrong in DIVA. The project ID is not correct (tries to login to the wrong project).

Description

Spider communication is not possible. DIVA remains blocked.

How to fix

• Correct the settings user name and password
• Correct the settings Project ID

Error 4.64.2011.32

Cause

The Spider rejects this machine. Cause has to be analyzed at Spider side.

Description

Spider communication is not possible at the moment. DIVA remains blocked. DIVA will retry to connect to the Spider until Spider accepts the connection.

How to fix

• Spider has not enough machine licenses: Increase the number of licensed machines.

Error 4.64.2011.33

Cause

The backoffice rejects this machine.

Description

Spider communication is not possible at the moment. DIVA remains blocked. DIVA will retry to connect to the Spider until Spider accepts the connection.

How to fix

• Add this machine to the backoffice's database.

Error 4.14.2013.2

Cause

The machine door was open for more than 10 minutes.

Description

The machine door is not closed.

How to fix

• Close the door.
• Connect the cable for the door switch.

See also

• AN185

Error 4.14.2013.8

Cause

The door control feature was not able to allocate a hardware interface (e.g. parallel port C on option215) because it is already used by another function enabled by configuration.

Description

Multiple features are enabled for the same hardware interface.

How to fix

• You can only enable one of the features at the same time since there is only a limited number of hardware interfaces available.

Error 4.14.2013.9

Cause

The door control feature was enabled on a hardware wich does not support this feature.

Description

The feature door control is not available for this hardware.

How to fix

• Use a hardware device which does support the feature.
• Disable the feature in the menu.

Error 7.1.2013.20

Cause

The machine door was opened

Description

The machine door was opened.

How to fix

• Nothing to fix.

See also

• AN185

Error 4.14.2111.27

Cause

The handheld sends a inappropriate START command

Description

The DDCMP protocol cannot be established. The external idevice sends data fast and DIVA2 is not ready to process them

How to fix

• Update to newer DIVA2 version

Error 4.64.2244.16

Cause

The server URL in the menu 16.08 is not configured properly.

Description

DIVA can not connect to the Spider server because of an invalid server URL configuration. DIVA remains blocked.

How to fix

• Use the format tcp://192.0.2.10:13000 for fix server IP address.
• Use the format tcp://spider.example.com:13000 for server address resolved using DNS.

Error 4.64.2244.17

Cause

The server URL in the menu 16.08 is not configured properly.

Description

DIVA can not connect to the Spider server because of an invalid server URL configuration. DIVA remains blocked.

How to fix

• Use the format tcp://192.0.2.10:13000 for fix server IP address.
• Use the format tcp://spider.example.com:13000 for server address resolved using DNS.

Error 4.64.2244.18

Cause

The server URL in the menu 16.08 is not configured properly.

Description

DIVA can not connect to the Spider server because of an invalid server URL configuration. DIVA remains blocked.

How to fix

• Use the format tcp://192.0.2.10:13000 for fix server IP address.
• Use the format tcp://spider.example.com:13000 for server address resolved using DNS.

Error 4.64.2244.19

Cause

The server URL in the menu 16.08 is not configured properly.

Description

DIVA can not connect to the Spider server because of an invalid server URL configuration. DIVA remains blocked.

How to fix

• Use the format tcp://192.0.2.10:13000 for fix server IP address.
• Use the format tcp://spider.example.com:13000 for server address resolved using DNS.

Error 4.64.2244.20

Cause

The server URL in the menu 16.08 is not configured properly.

Description

DIVA can not connect to the Spider server because of an invalid server URL configuration. DIVA remains blocked.

How to fix

• Use the format tcp://192.0.2.10:13000 for fix server IP address.
• Use the format tcp://spider.example.com:13000 for server address resolved using DNS.

Error 4.14.2244.43

Cause

Temporary not enough buffer space for TCP/IP in order to connect to Spider. This is possible if DIVA can't connect to Spider several times.

Description

TCP/IP uses a limited memory buffer. This buffer has been exhausted due to many failed connections to the Spider or spicls server. The memory shortage has no consequence for the function of DIVA beside the network connectivity.

How to fix

• This error condition will disappear if connection is possible again.
• In case of continuous occurrence, Check the Spider destination in menu 16.08
• If there is same connection problem for spicls which is running in parallel with Spider: you see also similar errors for the activated spicls services. Check spicls settings in menu 20.

Error 5.8.2244.50

Cause

Spider service not running

Wrong TCP port configuration

TCP port blocked by the server's firewall

Description

The connect via TCP/IP protocol between DIVA2 device and Spider cannot be established. A request from DIVA2 was refused by the server.

How to fix

• Start Spider service
• Check DIVA2 menu 16.08 IP and port setting
• IT infrastructure not correct

Error 5.8.2244.51

Cause

Spider service was stopped or restarted

Description

The Spider service closed an existing connection.

How to fix

• Restart Spider service

Error 5.8.2244.52

Cause

There is no route to the network.

Description

Due to a network problem DIVA cannot connect to Spider in order to send the stored data. If this problem continues, DIVA may enter into a blocking state. So no further transactions will be possible unless the network connection is re-established. For more detailed information refer also to AN111.

How to fix

• network not connected the DIVA (LAN or GSM). Wrong network settings in Menu 16.10. Wrong IP address setting, multiple fix address available.
• wrong IP address of Spider PC in DIVA menu 16.08.
• Spider not running

Error 5.8.2244.53

Cause

The destination host cannot be reached.

Description

Due to a network problem DIVA cannot connect to Spider in order to send the stored data. If this problem continues, DIVA may enter into a blocking state. So no further transactions will be possible unless the network connection is re-established. For more detailed information refer also to AN111.

How to fix

• network not connected the DIVA (LAN or GSM). Wrong network settings in Menu 16.10. Wrong IP address setting, multiple fix address available.
• wrong IP address of Spider PC in DIVA menu 16.08.
• Spider server not running

Error 5.8.2244.58

Cause

The host name could not be resolved to an IP address. So DIVA can not connect to Spider.

Description

DIVA can not connect to the Spider server because of an invalid network configuration. DIVA remains blocked.

How to fix

• Enable the network interface, e.g. Ethernet
• If the DHCP server does not configure the nameservers, setup the nameserver address manually in the ethernet configuration.
• If the network interface uses a fix IP or APIPA configuration, you have to setup the nameserver address manually in the ethernet configuration.
• Use a fix IP address of the Spider server.

Error 4.63.2290.4

Cause

DIVA returns data upon request but the machine doesn't confirm that data package.

Description

DIVA will request an OUT_OF_SEQUENCE so the protocol is resetted. A short interruption happens. Normally the user doesn't recognise anything.

How to fix

• Choose DIVA2 configuration "MDB Slave III"

Error 5.1.2293.7

Cause

Machine SW problem, cable defective, machine off, wrong configuration in the protocol settings of DIVA or the machine.

Description

In MDB the machine must poll the Cashless reader periodically even if it is in service mode. Although some machines come into situations where no communication is done. In this situation the error happens. You may see the little LEDs on the botton of the DIVA2 device below s1 connector. Both LEDs must flicker, so both devices are communicating. If only 1 LED blinks, one of the 2 devices tries to reach the other one, but there is no response.

How to fix

• temporary error depends of machine software
• correct protocol configuration in machine or DIVA2
• check cables

Error 5.63.2294.10

Cause

Answer from Master is not a valid byte

Description

DIVA doesn't process the answer and repeats the call. With this bug, no bad consequences are known so far.

How to fix

• no fix known.

Error 7.1.2300.1xx

Cause

End of generated audit collection

Description

Audit collection (readout) with list number 'xx' over DDCMP-Protocol was successful.

How to fix

• only info, nothing to fix...

Error 4.64.2312.7

Cause

The operating number has not been set (=0)

Description

Invalid operating number for accounting

How to fix

• Set a valid operating number (>0).

Error 7.14.2312.33

Cause

the statistic file was issued by a timer or user (closing card)

Description

this event informs that a statistic file (EVADTS, XML ) was created

How to fix

• no fix

Error 4.14.2319.11

Cause

Shortsummary on printer cannot be issued because of inactive OTRA system

Description

If you create a shortsummary to the printer or SDcard, DIVA need an enabled OTRA system in menu 13.57.

How to fix

• Enable the OTRA system in menu 13.57.01.0 = on

Error 4.64.2324.4

Cause

Default value (0) of operating number is not valid

Description

SpiderCloudService EVADTS is unable to create a EVADTS summary because of a missing configuration of the machine number.

How to fix

• Enter a valid operating number in menu 03.05 (not 0)

Error 4.64.2324.37

Cause

The username/password is wrong in DIVA. The projectID is not valid.

Description

How to fix

• Machine measures: close the door (or use the door plug), wait until the water is hot etc.
• communication problem: tracing the serial link and send to the support team for further analysis

Error 4.64.2324.38

Cause

Wrong URL configured in menu 20 for EVADTS service

Description

The EVADTS service is part of the SpiderCloudServices (spicls). The EVADTS server cannot be reached because of a wrong URL configuration. The EVADTS service is not functional.

How to fix

• Configure correct URL in the menu 20 for the EVADTS service.
• In case of the standard spicls service you may format the DIVA (Menu 14.20) or reset all settings (Menu 14.02). This will reset the URL to the factory default value.

Error 5.8.2324.53

Cause

Wrong URL configured in menu 20 for EVADTS service

Wrong network configuration

Server temporary not running or reachable

Description

The EVADTS service is part of the SpiderCloudServices (spicls). The EVADTS server cannot be reached because of a wrong URL configuration. The EVADTS service is not functional.

How to fix

• Configure correct URL in the menu 20 for the EVADTS service.
• In case of the standard spicls service you may format the DIVA (Menu 14.20) or reset all settings (Menu 14.02). This will reset the URL to the factory default value.
• Correct the network configuration (Ethernet or GPRS)
• Fix the network problems.

Error 4.64.2326.7

Cause

The user tried to read a DDCMP standard list, but CEM read is enabled

Description

The user tried to read a DDCMP standard list (1, 2, 12, 50, ...), but CEM read is enabled. This operation is not allowed.

How to fix

• Set CEM disabled in VOL 03.16.00

Error 4.64.2332.10

Cause

The user tried to read a CEM accounting, but CEM read is disabled

Description

The user tried to read a CEM accounting, but CEM read is disabled. This operation is not allowed.

How to fix

• Set CEM enabled in VOL 03.16.00

Error 4.14.2333.22

Cause

DDCMP tried to create a delta and a full clone in one session

Description

The delta clone and full clone cannot be done in a single session.

How to fix

• Close the DDCMP session between clone types

Error 4.64.2340.3

Cause

DIVA Operating Number not or wrong configured.

Description

Operating number is not configured in menu 03.05 and DAS system must used DIVA will remain blocked.

How to fix

• Configure the DIVA Operating Number not equal to 0

Error 4.64.2340.8

Cause

DAS ProjecdID is not configured.

Description

DAS System will be used and DAS ProjecdID is not configured in menu 03.40.00.1

How to fix

• Configure the DAS ProjecdID not equal to 0

Error 4.14.2340.12

Cause

NFC Mobile changed battery with no Aggregator connect

NFC Mobile no/error battery

Description

Error or never set the date/time on present NFC Mobile.

How to fix

• Connect to Aggregator to set actual date/time and try again

Error 4.64.2341.18

Cause

NFC Mobile DAS ProjectID is unset (0)

Description

NFC Mobile DAS ProjectID with zero is not allowed.

How to fix

• Set DAS ProjectID in VOL 03.40.00.1

Error 4.64.2341.19

Cause

DIVA/NFC Mobile DAS operating number invalid is unset(0)

Description

DIVA/NFC Mobile DAS operating number with zero is not allowed.

How to fix

• Set DIVA/DAS operating number in VOL 03.05

Error 4.64.2341.20

Cause

The NFC Mobile user tried to read a CEM accounting, but CEM read is disable

Description

The user with NFC Mobile tried to read a CEM accounting, but CEM read is disabled. This operation is not allowed.

How to fix

• Set DAS to enable in VOL 03.40.00.0

Error 4.64.2342.16

Cause

The user tried to read XML file(s), but XML Offline is disabled

Description

The user tried to read XML file(s), but XML Offline is disabled This operation is not allowed.

How to fix

• Set XML Offline enabled in VOL 15.09

Error 4.14.2701.3

Cause

The SD card inserted is a low voltage type

Description

The hardware of DIVA does not support low voltage types of SD card. The SD card will not work.

How to fix

• Use a compatible SD card.

Error 4.14.2701.7

Cause

The SD card inserted is not backward compatible to protocol version 2.

Description

The SD card uses a newere version of the protocol as it is implemented in the DIVA firmware. This SD card will not work.

How to fix

• Use a compatible SD card.
• Use a newer DIVA firmware.

Error 4.14.2701.8

Cause

The memory card inserted is a MMC not an SD card.

Description

The momory card is not supported by DIVA and will not work.

How to fix

• Use a compatible SD card.

Error 4.64.2705.13

Cause

The operating number has not been set (=0)

Description

Invalid operating number for periodic accounting

How to fix

• Set a valid operating number (>0).

Error 4.64.2711.5

Cause

Missing operating number

Description

The FOTA service in DIVA2 device cannot connect the spicls (Spider Cloud Service) account. Every machine needs a unique "operating number" within the spicls account.

How to fix

• Setup the operating number in menu 03.05.

Error 4.14.2711.38

Cause

Wrong URL configured in menu 20 for FOTA service

Description

The FOTA (Firmware update over the air) service is part of the SpiderCloudServices (spicls). The FOTA server cannot be reached because of a wrong URL configuration. Therefor the status info file cannot be reached and updated. The FOTA service is not functional.

How to fix

• Configure correct URL in the menu 20 for the FOTA service.
• In case of the standard spicls service you may format the DIVA (Menu 14.20) or reset all settings (Menu 14.02). This will reset the URL to the factory default value.

Error 4.8.2711.58

Cause

Wrong spicls settings

no network connection

Description

Due to a network problem DIVA2 cannot connect to the FOTA Spider Cloud Service. FOTA stands for Firmware Update Over The Air. The DIVA2 device tries every day to connect to the server if the service is activated in menu 20.21.20.

How to fix

• network not connected the DIVA (LAN or GSM) properly. Wrong network settings in Menu 16.10. Wrong IP address setting, multiple fix address available.
• wrong spicls login in men 20.21.00 (default connection) or 20.21.20 (individual login for FOTA). No account available: you must order a spicls account

Error 4.64.2903.5

Cause

The configured host name in menu 16.10 is not valid according to RFC 952/RFC 1123.

Description

A built-in host name will be used instead. This host name is sent as host name option in DHCP request (RFC2132).

How to fix

• Enter a valid host name or the empty string in menu.

Error 4.64.2903.9

Cause

The ethernet interface is enabled in the configuartion, but this hardware does not have an ethernet port.

Description

No TCPI/IP connection possible.

How to fix

• Disable the ethernet port in the menu.

Error 4.14.2906.7

Cause

The APN setting in the menu is wrong.

Description

No GPRS connection possible.

How to fix

• Set the APN setting to the correct value in the menu 16.18.

Error 4.64.2906.8

Cause

The authentication settings in the menu are wrong.

Description

No GPRS connection possible.

How to fix

• Set the PPP authentication settings to the correct values in the menu 16.18 (method, user name, password).

Error 4.64.3291.18

Cause

AutoFormat function is active but no XAM master token used

Description

No Legic master data found (XAM-Card) for Segment COM (see Menu 13.38.71)

How to fix

• Launch DIVA with Legic permission card for COM segment.

Error 4.64.3291.19

Cause

AutoFormat function is active but no XAM master token used

Description

No Legic master data found (XAM-Card) for Segment CASH (see Menu 13.38.72)

How to fix

• Launch DIVA with Legic master token (XAM) for CASH segment.

Error 4.14.3292.39

Cause

The data carrier is not presented to the reader in order to read all data correctly

Description

This error is a hint only, that the card must be hold to the antenna for longer time. No means must be undertaken

How to fix

• wait for new DIVA firmware

Error 4.64.3292.52

Cause

The reader type is set to an external reader type and the RFID stack is set to auto configuartion.

Description

This error is a hint: DIVA will act if the RFID Stack was set to on. If the reader is not connected this will lead to errors.

How to fix

• Set the RFID Stack explicit to on.

Error 4.64.3292.53

Cause

The reader type is set to internal reader and the RFID stack is set to on but there is no internal RFID reader.

Description

The RFID reader will not work.

How to fix

• Configure the external reader correctly with it's type and communication interface.
• Set the RFID Stack explicit to off.
• Set the RFID Stack to auto configuration (PnP).

Error 4.64.3292.64

Cause

The reader type is set to internal reader with an old hardware (LeX with Option211) which is not supported anymore.

Description

The RFID reader will not work.

How to fix

• Use a newer hardware.
• Use an older firmware. The last firmware supporting RFID Stack with Option211 is 8.50 (Kabru).
• If RFID Stack is not used: Set the RFID Stack explicit to off.

Error 4.64.3292.65

Cause

The user presents a permission card to activate a RFID application. This application uses a technology which is not supported by the RFID chip variant or the RFID chip OS version.

Example: Application oCF on LEGIC neon is not supported with the LEGIC 4200 (LeX 4200).

Example: MIFARE classic is not supported by this LEGIC OS version.

Description

The permission card is not accepted, this RFID application will not work with this reader.

How to fix

• Use a newer hardware.

Error 4.64.3292.66

Cause

The user presents a permission card to activate a RFID application. This application uses a technology which is not supported by the current DIVA firmware.

Example: MIFARE Ultralight was not implemented in older firmwares. Newer versions will (probably) support this RFID technology.

Description

The permission card is not accepted, this RFID application will not work with this reader.

How to fix

• Use a newer firmware.

Error 4.64.3292.67

Cause

The user presents a permission card to activate a RFID application. This application is not supported by the current DIVA firmware.

Example: oCF on MIFARE classic was not implemented in older firmwares. Newer versions will (probably) support this application for MIFARE classic.

Description

The permission card is not accepted, this RFID application will not work with this reader.

How to fix

• Use a newer firmware.

Error 4.64.3292.68

Cause

The user presents a permission card to activate a RFID application. This application is not licensed by the current DIVA firmware (customer exclusive application).

Description

The permission card is not accepted, this RFID application will not work with this reader.

How to fix

• Use another firmware (customer specific variant).
• Use another hardware which embeds the license for this feature.

Error 4.64.3292.69

Cause

The user presents a permission card to activate a RFID application. This additional application can not be activaed because the maximal concurrent RFID applications is reached. The quantity of applications is limited by key memory or DIVA firmware.

Description

The permission card is not accepted, this RFID application will not work with this reader.

How to fix

• Delete unused application keys using SAM64, Revocation card or Reset card.
• Use another hardware which supports a bigger quantity of concurrent applications.
• Use a newer firmware which supports more applications for this RFID technology.

Error 4.111.3300.7

Cause

The external reader is not licensed for use with the current firmware.

Description

The reader will stay in the "not initialized" state. No transponders can be read.

How to fix

• Use a Hug-Witschi licensed RFID reader.
• Use a newer firmware which supports this reader.

Error 4.111.3300.7

Cause

The RFID resder chip OS version is not supported by the current firmware.

Description

The reader will stay in the "not initialized" state. No transponders can be read.

How to fix

• Use a newer firmware which supports this reader.

Error 7.14.3306.24

Cause

The subvention block of ComX V100 is invalid and will be initialized

Description

Subvention data for this period are initialized(cleared)

How to fix

• User must wait for the next period to can profit of subvention

Error 7.1.3313.36

Cause

Mifare OpenPayment page pointer was invalid

Description

Mifare OpenPayment page pointer repaired to valid value was successful. The card can be used again

How to fix

• only info. Feature supported from version Kabru

Error 4.14.3334.35

Cause

Add a new COM/COMx Legic segment on the card (AutoFormat)

Description

This feature is only available for Legic Prime cards where 4 Byte UIDs are available. Otherwise the UID doesn't fit into the card number field of the COM/ COMx segment

How to fix

• Use an existing identification segment instead of UID to code the card number in the segment
• Use a Legic Prime card for the segmentation
• Segment Cash Only on the Legic Advant card. No card number would be available then

Error 4.14.3342.53

Cause

Temporary not enough buffer space for TCP/IP in order to connect to any spicls service. This is possible if DIVA can't connect to spicls several times.

Description

TCP/IP uses a limited memory buffer. This buffer has been exhausted due to many failed connections to the Spider or spicls server. The memory shortage has no consequence for the function of DIVA beside the network connectivity.

How to fix

• This error condition will disappear if connection is possible again.
• In case of continuous occurrence, Check the spicls destination in menu 20

Error 4.14.3349.8

Cause

The reset button is already pressed when DIVA switching on

Description

Reset key pressed already on power up with dongle protection (service position) This dongle position is normaly used to clear authorize data (keys/master token)

How to fix

• Check reset button on option 217 (LEX)
• Check reset button on Delight

Error 4.9.3356.0

Cause

Unknow terminal software version

Description

Unknow, reserved code from Ingenico

How to fix

• Ask support Ingenico, or update software from Diva if available

Error 4.9.3356.1

Cause

Unknow terminal software version

Description

Unknow, reserved code from Ingenico

How to fix

• Ask support Ingenico, or update software from Diva if available

Error 4.9.3356.2

Cause

Wrong Card format

Description

terminal reports, that the used card has a erroneous ISO format

How to fix

• Try another card

Error 4.9.3356.5

Cause

Card not valid

Description

Card not valid for various reasons

How to fix

• Try another card

Error 4.9.3356.6

Cause

// falsche Karte eher Invalid transaction

Description

Transaction denied before attempting online connection (for EMV issues, etc.). With EMV transactions, the EMV tags needed to analyse why the transaction is denied will be sent as data to the printer

How to fix

• Try another card

Error 4.9.3356.7

Cause

Not finalised correctly

Description

Transaction not finalised correctly in the online environment

How to fix

• Try again later

Error 4.9.3356.9

Cause

Currency in DIVA doesn't match with the currency in the terminal

Description

Currency from DIVA is not acceppted from Ingenico terminal

How to fix

• Check currency settings in DIVA menu 08.98

Error 4.9.3356.10

Cause

// SW bug

Description

For various commands the Ingenico returns an "approval code" which has a certain meaning. Here a reserved and unknown code received.

How to fix

• Ask support Ingenico

Error 4.9.3356.11

Cause

Diva has detected a timeout in the terminal from the current transaction ('Cancel')

Description

// Transaction cancelled in the Terminal by the user or time-out reached

How to fix

• No fix needed here...

Error 4.9.3356.13

Cause

Terminal not started

Description

// Ingenico Terminal not started

How to fix

• Ask support Ingenico

Error 4.14.3356.24

Cause

Forced reboot from DIVA on powered iuc285 terminal, connection will be asynchronous

low signal on GSM-Modem (bad network connection)

Missing or bad Ethernet connection

Description

Terminal iuc285 will no answer to requested command

How to fix

• Check cable to Ethernet
• Check cable to iuc285
• Adjust the GSM antenna for better signal quality.

Error 4.14.3356.25

Cause

Forced reboot from DIVA on powered iuc285 terminal, connection is further asynchronous

Signal is low on GSM-Modem (bad network connection)

Missing Ethernet connection

Description

No data can be send to terminal iuc285 or to the host

How to fix

• Check cable to Ethernet
• Check cable to iuc285
• Adjust the GSM antenna for better signal quality.

Error 4.14.3356.26

Cause

Wrong parameter

Description

Error in the format of the message received from the DIVA

How to fix

• Update software from Diva, if available or ask Hug-Witschi support

Error 4.14.3356.27

Cause

Wrong parameter

Description

Error in the format of the message received from the DIVA

How to fix

• Update software from Diva, if available or ask Hug-Witschi support.

Error 4.14.3356.28

Cause

// Incompatible communication protocol

Description

Error in the format of the message either received from the DIVA

How to fix

• Try to update the Diva software

Error 4.14.3356.29

Cause

Terminal performs the vend with DCC which is not supported by DIVA.

Description

Transaction aborted from DIVA on Sale with DCC (direct currency conversion). DCC should not happen in unatended terminals

How to fix

• ask support

Error 4.14.3356.30

Cause

// Terminal performs the vend with DCC which is not supported by DIVA.

Description

Transaction aborted from DIVA on Sale with DCC (direct currency conversion). DCC should not happen in unatended terminals

How to fix

• ask support

Error 4.14.3356.31

Cause

// Terminal performs the vend with DCC which is not supported by DIVA.

Description

Transaction aborted from DIVA on Sale with DCC (direct currency conversion). DCC should not happen in unatended terminals

How to fix

• ask support

Error 4.9.3356.98

Cause

SW bug

Description

For various commands the Ingenico returns an "approval code" which has a certain meaning. Here a reserved and unknown code received.

How to fix

• Ask support Ingenico

Error 4.14.3362.16

Cause

The modem can not connect to the GSM network for more than 2 minutes.

Description

No GPRS connection possible.

How to fix

• Wait until it can connect.
• Adjust the GSM antenna for better signal quality.

Error 4.14.3362.18

Cause

The modem can not connect to the GSM network for more than 2 minutes.

Description

No GPRS connection possible.

How to fix

• Wait until it can connect.
• Adjust the GSM antenna for better signal quality.

Error 4.14.3362.22

Cause

The GPRS modem firmware is not approved to work with the current DIVA firmware.

Description

No GPRS connection possible, modem is disabled (red LED blinks)

How to fix

• Use a newer DIVA firmware with support for this modem firmware version.

Error 4.64.3362.30

Cause

The modem is explicit enabled in the configuration, but this hardware has no modem.

Description

No GPRS connection possible.

How to fix

• Disable the modem in the menu 16.18 or set it to auto mode.

Error 4.64.3362.31

Cause

The modem is explicit enabled in the configuration, but no SIM card is inserted.

Description

No GPRS connection possible.

How to fix

• Insert a valid SIM card.
• Disable the modem in the menu or set it to auto mode.

Error 4.64.3362.32

Cause

The modem is configured in auto mode or no PIN code is configured.

Description

No GPRS connection possible.

How to fix

• Set the PIN code in the menu 16.18.
• Use a SIM card without a PIN.

Error 4.14.3362.33

Cause

The modem is configured in auto mode or no PIN code is configured.

Description

No GPRS connection possible.

How to fix

• Change the SIM card.
• Unlock the SIM card in another device, e.g. mobile phone or SIM card reader.

Error 4.64.3362.34

Cause

The PIN code in the menu 16.18 is wrong.

Description

No GPRS connection possible.

How to fix

• Set the PIN code to the correct value in the menu 16.18.

Error 4.14.3362.42

Cause

The modem can not connect to the LTE network after GSM was connected.

Description

No LTE connection possible.

How to fix

• Wait until it can connect.

Error 4.64.3377.10

Cause

RFID antenna not suitable for all mobile devices

Description

MobileApp needs a special antenna

How to fix

• Change the RFID antenna to version 5.00 or higher and restart

Error 4.64.3377.11

Cause

RFID antenna not suitable for all mobile devices

Description

MobileApp needs a special antenna

How to fix

• Change the RFID antenna to version 5.00 or higher and restart

Error 4.14.3385.13

Cause

Network problems to connect with Hug-Witschi Mobile Payment Server (Twint Gateway)

Description

Twint server cannot be reached. Twint payment not available. Beacon LED remains dark. For details refer to AN168.1

How to fix

• check Ethernet cable or other network connectivity issues (switch, router...)
• adjust the GSM antenna for better signal quality.
• if Twint never worked before: check DIVA2 menu 13.79.51-54 and DIVA2 network settings (menu 16.10 for LAN, 16.18 for GSM)

Error 4.14.3385.14

Cause

Wrong Beacon version

Description

Beacon off -> Mobile Payment is out of order

How to fix

• Connect a Beacon with valid version to connector s5

Error 4.14.3385.14

Cause

Beacon firmware is not supported by this DIVA2 firmware

Description

DIVA checks the beacon firmware at starting up. Only adapted and tested firmware versions can be used. The current beacon wasn't approved, so Twint cannot be used.

How to fix

• Change the Beacon (supported versions for Jannu: 1.11, 2.0.4.0, 2.0.7.0

Error 4.14.3385.15

Cause

Network not available

Network cable not plugged

Description

No connection to Twint server. Twint payment not available.

How to fix

• In case of GSM, adjust the GSM antenna for better signal quality.
• In case of Ethernet check plug, pach panel, firewall etc.

Error 4.64.3385.18

Cause

Wrong setting in Menu 13.79.51

Description

Twint payment not available with wrong URL

How to fix

• Correct settings Menu 13.79.51

Error 4.14.3390.10

Cause

unknow Beacon version (newer, old)

Description

Beacon goes off... Mobile Payment is out of order

How to fix

• Connect Beacon with valid version to connector s5

Error 4.91.3390.101

Cause

No Beacon connected to the Beacon connector s5

Description

DIVA is trying to find a Beacon on the appropriate interface. If the beacon doesn't respond it remains off (LED dark) and the Mobile Payment System doesn't work.

How to fix

• Connect the Beacon to s5 as configured in menu 13.79.23

Error 4.14.3390.101

Cause

No Beacon connected to the Beacon connector

Description

DIVA is trying to find a Beacon on the appropriate interface. If the beacon doesn't respond it remains off (LED dark) and the Mobile Payment System doesn't work.

How to fix

• Connect the Beacon to the corresponding interface

Error 4.64.3391.8

Cause

The beacon interface is configured to the wrong interface.

Another system is configured to the same interface.

The hardware does not have such an interface or it is not supported.

Description

Due to wrong interface configuration the beacon is not working. As a result mobile payment will not work.

How to fix

• Configure the correct interface in menu 13.79.23.
• DeLight: hardware version 4.20 or newer is reqiured

Error 4.64.3443.1

Cause

Identification Protocol only allow exactly ONE payment system

Description

Identification Protocol only allow exactly ONE payment system

How to fix

• Enable only one payment system VOL13.XX.24 for that proxy type

Error 4.64.3443.3

Cause

This DIVA type (b.e. Delight) may not support this COM port

Description

This DIVA type (b.e. Delight) may not support this COM port

How to fix

• Try to use another COM port

Error 4.64.3443.4

Cause

This DIVA type (b.e. Delight) may not support this COM port baudrate

Description

This DIVA type (b.e. Delight) may not support this COM port baudrate.

How to fix

• Try to use another COM port baudrate

Error 7.1.3451.22

Cause

DIVA Sync Number is not/wrong configured

Unknow NFC Mobile

Description

DIVA and NFC Mobile cannot be paired. Authorize data from NFC Mobile are invalid or strange!

How to fix

• Correct the DIVA Sync Number in menu 03.40.02.2
• Try another (correct) NFC Mobile

Error 7.1.3451.24

Cause

Prestored passcode is wrong