I am reviving this thread, which dealt with an issue getting my ShipModul MiniPlex to work. We had managed to solve this, but that was using Navigatrix 0.5 (Sept 2013). However, I have been trying to set up Navigatrix 0.5 (August 2014), which seems to be based on a newer kernel.

In doing so, my Shipmodul MiniPlex was once again broken. Applying fixes discussed earlier in the thread did not work this time. In fact, I was set further back than ever before, because /dev/ttyUSBx was never created. I traced this to the ftdi_sio driver not being loaded : lsmod | grep ftdi returned nothing. dmesg further instructed me that :



Thanks to several pages, including http://www.leniwiec.org/en/2014/06/25/ubuntu-14-04lts-how-to-pass-id-vendor-and-id-product-to-ftdi_sio-driver/ which put me on the right track, I found a working solution.

My installation process for the Shipmodul Miniplex has been fairly modified.
I include it hereunder for others which might have the same issue :

Create /etc/modprobe.d/usbserial.conf with content


Include the following content in /etc/rc.local content

Note that here I had to include a chmod permission change, since for some reason I was getting a Permission denied error that others do not seem to get.

Create /etc/udev/rules.d/98-gps.rules with content


GPSD can now find the Miniplex automatically, and alternatively you can use it with the unvarying name /dev/miniplex .

Hello,
I am also trying to get my Miniplex USB working. I am not an experienced linux user.
With text editor i made a text : insmod ftdi_sio and tried to save it in /etc/modprobe.d with the name usbserial.conf
I get a message permission denied.
I understand I have todo something with chmod but What and How.

Hi rein, in most cases, you will need to edit these files using "administrator" (or "root", or "super-user") rights, and not simple "user" rights.

To do so, there are several possibilities, but one of them would be to simply execute this in terminal :


You will be asked for the administrator password, and then you will be editing as administrator : "sudo" stands for "do as super-user". For most configuration files, you will have to edit them using "sudo".

Merci à "belle-isle" pour son travail. Je viens de tester ses derniers suggestions et cela fonctionne parfaitement.

Thank's to "belle-isle" for his work. I just tested his latest suggestions and it works perfectly.