16 replies to this topic

[Andreas]

Hi, I'm posting here on advise from Argolis sales and support, I'm having problems with updating the Smargo Smartreader V2 that I purchased/received this week.

 

I've downloaded the smartreader2update and smartreader2tool both for windows and linux, and ran it on several machines (windows 7 all updates/ubuntu 12.04 all updates).

 

On both platforms the device starts blinking blue (LED) upon insertion, but update attempts fail.. below is some information for each platform - if anyone can offer help/suggestion/insight it's appreciated.

 

 

This is the output of "dmesg" in ubuntu:

 

[63464.696069] usb 3-1: new full-speed USB device number 2 using uhci_hcd

[63464.867132] usb 3-1: New USB device found, idVendor=0403, idProduct=6001

[63464.867142] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[63464.867149] usb 3-1: Product: Smartreader2 plus

[63464.867155] usb 3-1: Manufacturer: Argolis BV

[63464.867160] usb 3-1: SerialNumber:         

[63464.943006] usbcore: registered new interface driver usbserial

[63464.943022] usbcore: registered new interface driver usbserial_generic

[63464.943032] usbserial: USB Serial support registered for generic

[63464.954879] usbcore: registered new interface driver ftdi_sio

[63464.954891] usbserial: USB Serial support registered for FTDI USB Serial Device

[63464.954969] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected

[63464.954989] usb 3-1: Detected FT232BM

[63464.954991] usb 3-1: Number of endpoints 2

[63464.954992] usb 3-1: Endpoint 1 MaxPacketSize 64

[63464.954994] usb 3-1: Endpoint 2 MaxPacketSize 64

[63464.954996] usb 3-1: Setting MaxPacketSize 64

[63464.958168] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0

 

But still I get this error when running the update:

 

./smartreader2update 

 

COM_ERROR (/dev/ttyUSB0)

 

 

 

And in Windows 7 no drivers are installed, the device is simply listed as "Smartreader plus" - and the update executable just keeps asking me to insert the device.. please see attached pic of the device manager

 

 

 

Anyone had this problem? I've contacted the selling site, the argolis sales/support - and they pointed me here(?)

 

 

 

//Br, Andreas

Attached Files

•  device-manager.jpg   13.31KB   61 downloads

[Kosh]

Since you are installing the device on the PC and it does not work as expected, they should be the ones helping you.

This is primarily an STB-forum, not for PC support. If you can't get it to run on an STB you might try and ask again here.

[Andreas]

Since you are installing the device on the PC and it does not work as expected, they should be the ones helping you.

This is primarily an STB-forum, not for PC support. If you can't get it to run on an STB you might try and ask again here.

 

 

Yeah, I thought so as well, and included a question on that in my reply to sales/support at argolis:

 

openpli is a forum for the openpli-firmware? I'm not using a box/openpli.. I don't intend to either, why post there? what's the connection to argolis/smargo?

 

 

I have however been using openpli on a dreambox previously, worked perfectly (: I posted this question as they asked/directed me to do so.

 

 

As I stated previously, any insight/thoughts/help is appreciated - but if a moderator/admin thinks this topic should be closed that's of course okay.

[waterpas]

Is it really necessary to update your device? I got it working on an E2 STB, how ever up untill now all 3 readers won't read my Conax-card, Seca3-card works well! Maybe you need some extra plugins to get it working. See below (OScam werkt niet) if you need any translations....

[Andreas]

Is it really necessary to update your device? I got it working on an E2 STB, how ever up untill now all 3 readers won't read my Conax-card, Seca3-card works well! Maybe you need some extra plugins to get it working. See below (OScam werkt niet) if you need any translations....

 

I see your point, but as it is now I don't seem to be able to open communication to the device in any case, that kinda throws a wrench in the system.. and also I'd like to be able to assign the "id" to the device as the product advertises );

[radxnl]

on your linux system start with:

 

cat /dev/ttyUSB0 to see if your access rights are setup correctly ( default distro installation sometimes requires root only access ( = bad ) to serial ports )

[Andreas]

on your linux system start with:

 

cat /dev/ttyUSB0 to see if your access rights are setup correctly ( default distro installation sometimes requires root only access ( = bad ) to serial ports )

 

Thank you radxnl - that's the ticket (: and I should have thought of that myself (or the manufacturer). I modified my users groups and gained access, and the smartreader2-tools worked as supposed.

 

That enables me to use the product with Ubuntu - but it's still not recognized/installed correctly in Windows (7 in my case) - any thoughts on that?

 

 

EDIT: is there a "thank you"/rep-system? if so I'd like to +1 radxnl for this (:

Edited by Andreas, 7 February 2014 - 08:13.

[Frenske]

 EDIT: is there a "thank you"/rep-system? if so I'd like to +1 radxnl for this (:

Try the green thumb on the right bottom in the posting from Radxnl.

[Andreas]

 EDIT: is there a "thank you"/rep-system? if so I'd like to +1 radxnl for this (:

Try the green thumb on the right bottom in the posting from Radxnl.

 

I don't see it.. not on your post either, do you?

 

[WanWizard]

It's use is restricted to senior members of this forum. This was done to prevent mis-use (users creating dummy accounts, then giving themselfs a lot of thumbs-up).

[Andreas]

It's use is restricted to senior members of this forum. This was done to prevent mis-use (users creating dummy accounts, then giving themselfs a lot of thumbs-up).

 

Makes sense (: sad to have to go out of the way to avoid semi-idiotic behavior (; virtual bragging rights abused to the max

 

A big thanks to radxnl from me instead then (:

 

 

Any thoughts on why the smartreader isn't correctly detected/installed in Windows 7 is appreciated - although you guys already helped a lot! (manufacturer, take notes)

[WanWizard]

Yeah, unfortunately there are people like that...

 

I'll click the "thumbs up" for you.

 

And I can't help you with your question, don't use those readers, and haven't seen Windows in years...

[Andreas]

Yeah, unfortunately there are people like that...

 

I'll click the "thumbs up" for you.

 

And I can't help you with your question, don't use those readers, and haven't seen Windows in years...

 

Thanks (: On any given day (well, work days at least) I see most OS's (; win, *nix, osx, android, ios.. whatever works

[radxnl]

regarding windows7, de-install the 'new' ftdi drivers and install the old ones ( as provided for the 'old' smartreaders )

 

( if you cannot manange i will try to find a download link for you somewhere )

[tedy58]

Hi to all,
Today I have issue with this smartreader too. May be it is little complicated when I drive it but anyway I will explain it and you decide if it worth to do it my way.
 
First of all I use Ubuntu 16.04-2 as system to check if my card works.
2. I add the reader in /etc/udev/rules.d/44-persistent-usb.rules (with correct permissions) if don't have create such a file.

    it contain similar staff inside:

# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.

# USB readers //////////
# Bus 002 Device 011: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
#  idProduct          0x6001 FT232 USB-Serial (UART) IC
# lsusb -v # will give you the device info

SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="reader16",  SYMLINK+="rdrnew"

   here ATTRS{serial}=="reader16" contain the serial name that is find by the

 #lsusb -v 

command where you must find which is your reader.

 

3. restart udev rules with following command:

 #sudo udevadm control --reload-rules && sudo udevadm trigger

4. Then make a reader with similar values:

[reader]
label                         = rdr
description                   = Smargo /dev/rdrnew
protocol                      = smargo
device                        = /dev/rdrnew
smargopatch                   = 1
cacheex_allow_request         = 1
caid                          = CAIDhere
detect                        = cd
mhz                           = 534
cardmhz                       = 369
ident                         = CAIDhere:000000
group                         = 1
emmcache                      = 1,1,2,0

   here you have to change the correct values for you t.e.:

 

device = /dev/rdrnew set here the value that you set in persistent_usb.rules file 

CAIDhere set correct caid,

mhz set correct mhz

 

for me this value works

 

then start your oscam and try it.

[tedy58]

I try to edit my post above and add some more details, but seems forum rules doesn't allow it to members with few post.

[Pr2]

Hi,

 

Or use your smargo in smartreader protocol and forgot about those udev rules.

 

http://www.streamboa...?threadid=42226

 

Pr2