36 replies to this topic

[idreamx]

Taken from http://www.argolis.nl/downloads.html
Assigning the Argolis Triple Reader to new device names.

Place this file iin /etc/udev/rules.d/
By reconnecting the triple reader it will be assigned to the new device names.

Read the serial number of the triplereader: lsusb -d 403:6011 -v | grep iSerial
Serial number: 00000001
Readername: triplereader_TEST

The new names for the triplereader with serial number 00000001 will be:
P1 = /dev/triplereader_TEST00
P2 = /dev/triplereader_TEST01
P3 = /dev/triplereader_TEST02
Serial number: 0000ABCD
Readername: my_READER

The new names for the triplereader with serial number 0000ABCD will be:
P1 = /dev/my_READER00

Edited by idreamx, 17 April 2012 - 14:25.

[Carl]

Thank works great!!

[idreamx]

I have been testing this setup in cccam and oscam, and its working like a charm.

---------------------------------------
Make sure that you use the latest 3rd party software. Most software supports the triple reader automatically.
The old dm drivers don't recognise the vid and the pid of the device. So you can modprobe it manually and the kernel will recognise the 3 devices.

An example:

at first, check what devices you have :

cat /proc/bus/usb/devices | grep 'T:\|S:'

sample output:

Source code
1
2
3
4
5
6
7
8
9
10
11
12
13
[root@a ~]# cat /proc/bus/usb/devices | grep 'T:\|S:'
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
S: Manufacturer=Linux 2.6.32.26-175.timb1.i686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1f.4
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
S: Manufacturer=Linux 2.6.32.26-175.timb1.i686 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1f.2
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
S: Manufacturer=Argolis BV
S: Product=Smartreader plus
S: SerialNumber=BLAAH001


Now you see that you have one Smargo with SerialNumber "BLAAH001", just put "device = Serial:BLAAH001" in oscam.server and configure other needed parameters for this. Do the same for other Smargo slots (each of them should have own specific SerialNumber) and u'r done.
If you cant use smartreader protocol, then you need use /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2 etc. accordingly or bind these Smargo devices with the specific names using udev rules, so you have no mess with device order.
--------------------------------------------------

[DannyD]

Hey!

I wonder if someone familiar with this could give me a little bit of a hand...I've been directed here by the manufacturer for support.

First and foremost, I'd like to point out that I'm using Enigma 2 as the O/S rather than OpenPli, i'd rather not change O/S if I can avoid it.

I've established what the Serial Number is byway of using the menus, Telnetting to the devise and running lsusb -d 403:6011 -v | grep iSerial didn't work what so ever.

I uploaded the file, and changed the Serial Number, removed the second set of "codes" (as I believe this is a duplicate used to demonstrate how to "stack" the device) - and I've written some codes in CCcam's config file matching the above. However, it's not working.

I wonder if someone would be able to please:

1) Advise whether I need more drivers to make it compatible with Engima 2
2) Upload a demonstration of their config files (CCcam.cfg) and an adapted form of the above for their box, I would be most appreciative!

Thanks!

[pieterg]

Please give the output of

lsubs -d 403:6011 -v

and if that does not give any output:

lsusb

Make sure you have installed the driver:

opkg update && opkg install kernel-module-ftdi-sio
load it:
modprobe ftdi_sio

plug the reader, and check whether it is detected, and claimed by the driver:

dmesg

Normally it would now have detected and attached three virtual comports:

/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2

which you can use in your config.

[DannyD]

Thanks for the advise,

However....lsusb doesn't seem to work - please see the attached image:

http://tinypic.com/r/jihytv/6

opkg gives a similar result.

[radxnl]

You are making a typo

Please follow the exact command as pieterg showed it please.

( or use copy paste )

Edited by radxnl, 20 May 2012 - 17:52.

[Bag58]

Be aware the first letter of the command lsusb is a lowercase L!

The first command pieterg listed also contains a typo, that should be
lsusb -d 403:6011 -v

[DannyD]

Thanks for your help thus far, however, as far as I can tell.....it's still not "mapping" correctly - it's detecting as a CD ROM drive and isn't naming the files for me to reference in the CCcam config file.

I believe that the "lsusb" item that I am using may be the source of the problem? I've installed this as a plugin.

I have performed the opkg operations described above in the original reply - thanks! I've uploaded the file into the correct location via FTP.

Please see what I've done/using attached:

http://www.sendspace.com/file/qy0qpt

Please advise how to proceed.

[radxnl]

i think you need to ask on the I-have-a-dreambox forum, that is where the support for the Gemini image is

regards

[pieterg]

lsusb in your image does not seem to support the -v option (nor the -d option).
I see the triple reader is shown, but you just don't get the details from lsusb.

Do you really need the serialnumber?
If not, just use /dev/ttyUSB0..2

If these don't exist (and your dmesg output does not show that they are created) your image is using an outdated ftdi_sio module version.

[DannyD]

Yeah, the lsusb doesn't seem to work as intended. I've tried installing the "proper way" by way of libusb and usbdriver however, I can't find a libusb compiled for mispel as an ipk package.

I don't particularly need the serial-number, I can see it working on the blue panel, hardware menus - I can identify the serial number here.

However, since it's being detected as a CD ROM - I don't believe it's working right. Surely, the references won't work either?

I've screenprinted out puts of dmesg in the above zip ifle.

Edited by DannyD, 21 May 2012 - 10:14.

[pieterg]

However, since it's being detected as a CD ROM - I don't believe it's working right. Surely, the references won't work either?

no, it is properly detected as a virtual serial port.
lsusb lists all usb devices, so it shows some 'CD ROM' devices as well. But those have different id's, and are not related.

[DannyD]

So, what steps do I need to get it working then?

Surely, even though lsusb isn't working correctly (I believe this is just a tool to list devices...in telenet) I would be able to correctly configure.

In theory therefore, are you saying that if I have the config file setup - as I've already done with the serial number, if I use the same references in CCcam.cfg it'll work?

Thanks in advance.

[radxnl]

if you only have one triplereader you don't need to do the thing with the serial number, the ports are allways the same

/dev/ttyUS0 /dev/ttyUSB1 and /dev/ttyUSB2

just add them in your CCcam.cfg as an extrenal cardreader and that should work just fine

serial reader: /dev/ttyUSBO smartreader+
serial reader: /dev/ttyUSB1 smartreader+
serial reader: /dev/ttyUSB2 smartreader+

further image releated question you have two options:

1 - ask them at the gemini forum ( the image you are running )
2 - flash an openPLi image and we'll go from there

regards

[DannyD]

I appreciate the help. However, unfortunately - for the record of any casual visitor "visiting" - it's still not working. I'll investigate elsewhere I guess.

I'd rather crack one problem at a time, rather than jumping to learning another step - flashing the dreambox. Although, OpenPli looks amazing/superior in terms of English documentation tutorials and is certainly something I will be looking at using in the future.

[hobby11fun]

Is there an explanation to triple reader to rename
Where can I find

[Henksat]

Is there an explanation to triple reader to rename
Where can I find

See the first posting here: http://www.argolis.nl/downloads.html

[boutchous]

Hi , is there a difference between 2.2 and 3.0 base on VU+ ?
With OpenPLI 2.2 argolis can be use , but here i can't use with 3.0 , oscam don't see any USB
With the command : lsusb -d 403:6011 -v | grep iSerial nothing , i can't get serial
Only this command : lsusb give me bus and i can see 403:6011 on 001:002
I thing my VU never use the rules 31-triplereader.rules

Can you help me please ?
Thank you very much

[boutchous]

This exactly what i have here : /etc/udev/rules.d/31-triplereader.rules
# Place the file in /etc/udev/rules.d/
# By reconnect the triple reader it will be assigned to the new device names.
# Read the serial number of the triplereader: lsusb -d 403:6011 -v | grep iSerial

SUBSYSTEMS=="usb" ENV{ID_IFACE}="$attr{bInterfaceNumber}"
KERNEL=="ttyUSB*", ATTRS{serial}=="00000010" SYMLINK+="triplereader$env{ID_IFACE}"

Serial number: 00000010
Readername: triplereader
The new names for the triplereader with serial number 00000010 will be:
P1 = /dev/triplereader00
P2 = /dev/triplereader01
P3 = /dev/triplereader02

#SUBSYSTEMS=="usb" ENV{ID_IFACE}="$attr{bInterfaceNumber}"
#KERNEL=="ttyUSB*", ATTRS{serial}=="0000ABCD" SYMLINK+="my_READER$env{ID_IFACE}"

#Serial number: 0000ABCD
#Readername: my_READER
#The new names for the triplereader with serial number 0000ABCD will be:
#P1 = /dev/my_READER00
#P2 = /dev/my_READER01
#P3 = /dev/my_READER02

vuuno login: root
root@vuuno:~# lsusb -d 403:6011 -v | grep iSerial
root@vuuno:~#

root@vuuno:~# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 0403:6011 # This is the triple reader
root@vuuno:~#

After reboot i never seen /dev/triplereader00 , 01 and 02 or /dev/USB0 , 1 , 2
I don't know where is my problem

Thanks for help