[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problems connecting to Ingenico POS devices with Debian Jessie



Good afternoon,

I'm sending this message here, because the problem is happening only on my Debian machine.

I'm developing applications for Ingenico POS devices EFT 930S and ICT 220. They run Telium platform and I use an Windows application to load the files into the devices.
The vendor provide a  Windows Local Loading Tool (LLT)  that connects through their "serial" interface. Actually, it is a USB interface that works as a serial port.
The tool establishes a PPP link and after that there is a FTP connection.

My environment is a Debian Jessie running Kernel 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux.

This Debian is a VirtualBox host for a Windows XP SP3 (32 bits) guest machine that runs the LLT to connect to the terminals.

The version of the VirtualBox is:
virtualbox-4.3                    4.3.20-96996~Debian~w amd64                 Oracle VM VirtualBox

It was downloaded from the Oracle Repository.

Some time ago, when I was using a different version of the kernel (I'm not sure which one right now) everything was working fine. After the update the things got messy.

I have 2 problems. If the ModemManager daemon is running, it restarts the device few seconds after it's connected to the machine's USB port. So I stopped the ModemManager. (problem solved)

The second problem is that the PPP connection is never established.
I activate the USB device on the VirtualBox, the Windows XP detects it, the LLT recognize that there is a COM port active, but the PPP link is not established. There is this error RAS 777 that the documentation explain as:

Terminal is not responding. Check connection (check the serial cable or USB cable is correctly plugged) and check that terminal is waiting for a connection. If not check Selecting communication port or Installing the null modem driver.

I made all the checks and everything is ok but it keeps returning this error.
It's valid to point that I use the same VM (in this Debian host)  to connect to other vendors' POS using their own software and my Debian connects via Minicom to then to get serial output.

Then I exported my VM and used it on a Ubuntu machine, disabled the ModemManager and everything worked pretty well. (cables and POS devices are the same)

The Ubuntu distro is 14.04 and the Kernel 3.13.0-43-generic #72-Ubuntu SMP.

I did some tests in the Debian machine with the udev and the Linux is recognizing the USB device.

I got this in the /var/log/messages when I plugged the device.

Jan 28 15:53:07 vali kernel: [19860.666924] usb 4-1.4.3.1: new full-speed USB device number 10 using ehci-pci
Jan 28 15:53:07 vali kernel: [19860.776725] usb 4-1.4.3.1: New USB device found, idVendor=079b, idProduct=0028
Jan 28 15:53:07 vali kernel: [19860.776732] usb 4-1.4.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 28 15:53:07 vali kernel: [19860.777217] cdc_acm 4-1.4.3.1:1.0: ttyACM0: USB ACM device
Jan 28 15:53:07 vali mtp-probe: checking bus 4, device 10: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4.3/4-1.4.3.1"
Jan 28 15:53:07 vali mtp-probe: bus: 4, device: 10 was not an MTP device


This in the /var/log/kern.log

Jan 28 15:53:07 vali kernel: [19860.666924] usb 4-1.4.3.1: new full-speed USB device number 10 using ehci-pci
Jan 28 15:53:07 vali kernel: [19860.776725] usb 4-1.4.3.1: New USB device found, idVendor=079b, idProduct=0028
Jan 28 15:53:07 vali kernel: [19860.776732] usb 4-1.4.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 28 15:53:07 vali kernel: [19860.777179] cdc_acm 4-1.4.3.1:1.0: This device cannot do calls on its own. It is not a modem.
Jan 28 15:53:07 vali kernel: [19860.777217] cdc_acm 4-1.4.3.1:1.0: ttyACM0: USB ACM device


And with this udev rule:

KERNEL=="ttyACM*", SUBSYSTEM=="tty", ATTRS{idVendor}=="079b", ATTRS{idProduct}=="0028", MODE="0666", SYMLINK+="telium%n"

I got the link telium0 in the /dev folder.

But when I activate the device in the VirtualBox, so my VM could see it, the link disappears but the VM detects the device.

What else could I send to you, so you could help me to solve this problem?

Thanks in advance.

Kind Regards

Paulo Roberto

Reply to: