Ingenico Input Devices Driver

Input devices can be checked and configured individually. Input values can be seen in the input fields. Force feedback can be disabled for each device. Game controllers. The available input devices are shown in the Game Controllers section. Choose a device and click 'Edit'. On the configuration screen there are 3 blocks. Ive tryed using the vista delete the plug&play file to get it to reload the file and try the device agine as some sites say to do and it wont work eather i tryed a total power wipe so the mother board resets and i tryed other usb ports and i tryed useing other devices in them they work Ive tryed takeing all the sub devices off and restarting.

The Ingenico iSC Touch 250 is a customer-facing, color touchscreen device that features signature capture and supports MSR (magnetic stripe), EMV (chip), and NFC (contactless) payments. Directly connected to Bolt via a wired Ethernet connection, the device protects your transactions with a powerful combination of EMV technology and point-to-point encryption (P2PE), making each transaction secure and PCI compliant.

Ordering an Ingenico iSC Touch 250

To order the Ignecico iSC Touch 250, visit the CardPointe Shop.

Input

What's in the Box?

  • Ingenico terminal
  • Ingenico multi-point mono connector cable
  • Ingenico power supply
  • Ingenico stylus

Connecting the Device

Input
  1. Once your equipment is unboxed, plug the power supply connector into the jack on the Multipoint Interface Cable.
  2. Connect the Multipoint Interface Cable into the Multipoint Port on the back of the Bolt P2PE device.
  3. Connect the other end of the Multipoint Interface Cable to an Ethernet port (router, modem, wall jack, etc.).
  4. Plug the power supply adapter into an available power outlet.

Confirming Connectivity

  1. Once power is supplied to the the Bolt P2PE device, an initiation process begins.
  2. Once the device has successfully established its IP Address, it will attempt to call the Bolt service.
  3. If the connection is successful, the Bolt P2PE device displays Bolted
  4. If the connection is unsuccessful, the device displays Unbolted, at which point you can contact us for troubleshooting.
  5. Once Bolted, the device is ready for use. The device may be left on indefinitely or may be disconnected from power as necessary.

Accessing and Navigating the Bolt S.O.S. Menu

The Bolt S.O.S. menu allows you to access the device Version, Date and Time, Server Properties, and Ethernet Properties.

  • Press +, 7, 6, 7 on the device's number pad to access the Bolt S.O.S. menu.
  • Press + to navigate down.
  • Press - to navigate up.
  • Press O (green button) to select.
  • Press < (yellow button) to clear.
  • Press X (red button) to cancel or return to the main menu.

Setting a Static IP Address for Your Device

Setting a static IP address for your device is optional. Typically, the device is assigned an IP address automatically when connected to the network. To manually set the network settings for the device, follow the steps below.

  1. Check your device's firmware version to confirm it is version 1.6.1 or higher.
    If your device requires a firmware update, contact CardPointe Support.
  2. Press X (red button) on the device's number pad to return to the main menu.
  3. Press + to navigate down the the list to Ethernet Properties.
  4. Press O (green button) to select Ethernet Properties.
  5. Press < (yellow button) to toggle the setting from DHCP to Static.
  6. Press O (green button) to edit the static IP settings.
  7. Press + to cycle between the network setting fields. Press O (green button) to enter a new value using the device number pad. Press < (yellow button) to erase the last value.
  8. Press O (green button) to save the value and continue using + to cycle between fields until all the values have been entered.
  9. When finished, press O (green button) to save.
  10. Press O (green button) to continue with a terminal reset.

Checking Your Device's Firmware Version

  1. Access the Bolt S.O.S menu.
  2. Press O (green button) to select Version in the menu list.
  3. The current firmware version installed is displayed on the screen. Press X (red button) to return to the main menu.

The following topics provide information for troubleshooting your Ingenico iSC Touch 250 device.

Device Unbolted

  1. Verify that you are using the provided multi-point mono connector (Ethernet) cable and power supply. The power supply plugs into the splitter on the Ingenico multi-point mono connector cable.
  2. Verify that the Ethernet jack on the multi-point mono connector cable is plugged securely into your router, modem, networking switch, or Ethernet wall jack.
  3. Verify that your device was provided by CardConnect, or your software provider.
  4. Consult with your IT administrator to verify that the Ethernet port being used has access to the Internet, and that your internal network whitelists Bolt P2PE traffic. This will ensure that a firewall is not blocking the connection.

Device Bolted but Unable to Connect to Application

  • Confirm with your software provider that the device configuration is correctly set within your application.
  • If the device configuration is set correctly, contact CardPointe Support for assistance.

Device Restarting Unexpectedly

The most common cause for a device restarting during the day is the result of an inaccurate time setting on the device. Devices are configured to automatically restart at 4 AM local time. To update your time settings, follow the steps below.

  1. Access the Bolt S.O.S menu.
  2. Press F2 to navigate down the list to Date and Time.
  3. Press O (green button) to access Date and Time settings.
  4. Enter the current date using the device number pad.
  5. Press F2 to navigate down to the time.
  6. Enter the current time in 24-hour format (military time), using the device number pad.
  7. Press O (green button) to save your settings.

Device not Prompting for Tip

Check your device's firmware version to confirm it is version 1.6.3.14 or higher. If your device requires a firmware update, contact CardPointe Support.

Command Cancelled Error

Check that the stylus is securely connected to the terminal. Without a connected stylus, the terminal aborts the signature process with a 'Command Cancelled' error.

PPS - 21 Invalid Merchant Error

If you experience a ‚ÄčPPS - 21 Invalid Merchant error on the terminal, contact Merchant Support for assistance.

Our support team is here to help you with device setup and beyond. If you have questions, please contact CardPointe Support.

When contacting CardConnect for support, have your merchant ID and device hardware serial number (HSN) available. You can find the HSN at the top of the device display. Take note of any errors encountered, in order to facilitate the troubleshooting process.

-->Ingenico

This article clarifies some confusion that vendors have experienced about how hardware that complies with PCI Power Management (PCI-PM) interacts with device drivers in the operating system and about how PCI-PM integrates with ACPI. For more information, see https://www.uefi.org/specifications

Device drivers and PCI power management

This discussion assumes that you are familiar with how Windows Driver Model (WDM) drivers handle power management events, as described in the current Windows DDK. In general, the responsibilities for device drivers are as follows:

  • Bus drivers: Bus drivers are responsible for enumerating, configuring, and controlling devices. For PCI-PM, the PCI driver is responsible for reading the PCI-PM registers to determine the capabilities of the hardware. When POWER IRPs request power state changes, the PCI driver writes to the PCI power management registers to set the hardware to different Dx states.

    When a device is enabled for wake-up, the PCI driver writes to PCI-PM registers to enable the device to fire PME (ACPI will also take an action, see the next section). Finally, when ACPI determines that the PCI bus is waking the system, the PCI driver scans PCI configuration space looking for which device is asserting PME, disables PME in that device, and notifies the driver for that device.

  • Device driver: The specific driver for the device is responsible for saving and restoring device context, and requesting power state changes as the policy owner for the device. When the device driver receives a POWER IRP requesting a lower device power state change, the device driver is responsible for saving any proprietary device context needed to later turn on the device. In some cases, there may be nothing to save.

PCI-PM registers are strictly the domain of the PCI driver--the IHV's device driver does not need to access any of these registers. Doing so would cause the system to not work reliably. The device driver's responsibility is to perform only proprietary actions.

Integrating ACPI and PCI PM

Some devices, particularly motherboard video devices in portables, may require both PCI Power Management as well as ACPI Source Language Assembler (ASL) to completely power manage the device. The PCI Power Management registers would control the internal state of a device, such as internal clocks and power planes. ASL would control the external state, such as external clocks and power planes, or in the case of video controllers, ASL would control the video backlights. Note that ASL and PCI-PM can only be combined on motherboard devices.

The OnNow architecture is a layered architecture, handling the integration of the device driver, PCI driver, and ACPI driver (and ASL) naturally. The following scenarios show the order in which drivers are called to handle these devices.

Note

For the above scenarios to work as described, a WDM driver must forward POWER IRPs correctly as described in the current version of the Microsoft Windows DDK.

Scenario 1: Turning off a device

  1. Device driver: Saves proprietary device state.
  2. PCI driver: Saves Plug and Play configuration, disables the device (interrupts and BARs), and puts the device in D3 using PCI-PM registers.
  3. ACPI driver: Runs ASL code (_PS3 and _OFF for power resources no longer in use) to control the state external to the chip.

Scenario 2: PCI power management and device drivers

Ingenico Input Devices Driver Downloads

  1. ACPI driver: Runs ASL code (_PS0 and _ON for any OnNow required power resources) to control the state external to the chip.
  2. PCI driver: Puts the device in D0 using PCI-PM registers and restores Plug and Play configuration (interrupts and BARs--these might be different from what the device was previously on).
  3. Device driver: Restores proprietary context in the device.

Scenario 3: Enabling wake-up

  1. Device driver: Sets proprietary registers in the chip to enable wake-up. For example, in pattern matching network wake-up, this is when the patterns would be programmed into the adapter.
  2. PCI driver: Sets the wake-up enable bits in the PCI PM registers to allow the device to assert PME.
  3. ACPI driver: Enables the GPE in the chip set associated with PME (as described by the _PRW object listed under the root PCI bus).

Scenario 4: Wake-up

Ingenico Input Devices Driver Update

  1. ACPI driver: Wakes and scans the GPE status bits for wake-up events, disabling GPEs for set GPE status bits, and running any _Lxx or _Exx methods associated with set GPE bits. In response to a wake-up notification on the PCI bus, the ACPI driver will complete the PCI driver's WAIT_WAKE IRP to notify the PCI driver that it is waking the system.
  2. PCI driver: Scans configuration space looking for any devices with a set PME status bit. For each device, it disables PME and completes the WAIT_WAKE IRP for that device to inform the driver that it is asserting wake-up. The PCI driver stops scanning for wake devices when it has made a complete pass through all PCI devices having not found any asserting PME and when PME stops being asserted.
  3. Device driver: Requests the device be put in D0 (see scenario 2) and sets any proprietary registers in the chip required to handle the wake-up event.

Call to action on PCI power management and device drivers

Driver

Ingenico Input Devices Drivers

  • Integrate ACPI and PCI-PM capabilities into your devices as described in this article.
  • The PCI Power Management specification is available at https://www.pcisig.com. This link leaves the Microsoft.com site.
  • ACPI Specification available at https://www.uefi.org/specifications. This link leaves the Microsoft.com site.
  • The ACPI Component Architecture (ACPICA) compiler can be found at https://acpica.org/downloads/binary-tools.