Tellstick Duo on a ReadyNax NV+ (Sparc processor)

[bibi21000]

Hello,
I try to install telldus-core on my readynas NV+ (with a sparc-padre processor) : http://www.readynas.com/?cat=4
The kernel is a 2.6.17, with some hacks from Netgear.
I plan to use my tellstick with domogik (http://www.domogik.org/). Domogik is already installed on my NAS.
I follow the How-to on your site : http://developer.telldus.com/wiki/TellS ... tionSource

What I've done :
- Compile and install a recent cmake
- Compile and install gcc 4.
- And compile and install telldus-core (2.1.0 and 2.0.104). The 2.0.4 doesn't compile on my nas.

I can launch the telldusd daemon, add the tellstick using tdadmin without errors.
But when I try to activate a light using tdtool, it says "No tellstick found".

What can I do ? Is there a way to activate debugging stuff in telldus-core or to increase verbosity ?

TIA

[bibi21000]

This thread seems to be related to mine : http://www.telldus.se/forum/viewtopic.p ... 5&start=30
But not really sure as I dont speak swedish

[micke.prag]

Is TellStick inserted before or after telldusd is started?
How do you call tdadmin?

[bibi21000]

The tellstick is inserted before starting the daemon

Here are some informations about my nas :

# lsusb
Bus 003 Device 008: ID 1781:0c31
...

According to this I've updated the modules options
# cat /etc/modprobe.d/tellstick
options ftdi_sio vendor=0x1781 product=0x0c31
udev is not installed on my nas

Here uis the long story

Insert the tellstick duo
# modprobe ftdi_sio

# cat /var/log/syslog
Oct 7 00:01:56 bibi-nas kernel: ::::::<6>usbcore: registered new driver usbserial
Oct 7 00:01:56 bibi-nas kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Oct 7 00:01:56 bibi-nas kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
Oct 7 00:01:56 bibi-nas kernel: ftdi_sio 3-1.2.1:1.0: FTDI USB Serial Device converter detected
Oct 7 00:01:56 bibi-nas kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM
Oct 7 00:01:57 bibi-nas kernel: usb 3-1.2.1: FTDI USB Serial Device converter now attached to ttyUSB0
Oct 7 00:01:57 bibi-nas kernel: ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
Oct 7 00:01:57 bibi-nas kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM
Oct 7 00:01:57 bibi-nas kernel: usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB1
Oct 7 00:01:57 bibi-nas kernel: usbcore: registered new driver ftdi_sio
Oct 7 00:01:57 bibi-nas kernel: drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters DriverO

# tdadmin controller connect --pid=0c31 --vid=1781 --serial=ttyUSB1
# /etc/init.d/telldusd start
Starting the Telldus TellStick daemon : telldusd.
tdtool --on 1
Turning on device 1, Example device - TellStick not found

# /etc/init.d/telldusd stop
Stopping the Telldus TellStick daemon: telldusd.

# tdadmin controller connect --pid=0c31 --vid=1781 --serial=ttyUSB0
# /etc/init.d/telldusd start
Starting the Telldus TellStick daemon : telldusd.
# tdtool --on 1
Turning on device 1, Example device - TellStick not found

[bibi21000]

ttyUSB1 appears to be my usb to parallel adaptater. I remove it and do the same process as above but that doesn't work.

[micke.prag]

This seems to be the problem:

# cat /etc/modprobe.d/tellstick
options ftdi_sio vendor=0x1781 product=0x0c31

Insert the tellstick duo
# modprobe ftdi_sio

This can block tellusd for accessing the device. Remove that.

[bibi21000]

After removing stuff in modprobe (tellstick duo don't use it), and removing kernel modules from memory.
I try :

# /etc/init.d/telldusd start
Starting the Telldus TellStick daemon : telldusd.

# tdadmin controller connect --pid=0c31 --vid=1781

# tdtool --on 1
Turning on device 1, Example device - TellStick not found

and that don't work

I will update the firmware of my nas soon, so I will get a fresh one.
Which release of the following program and library do you use :
gcc
libftdi
libconfuse

TIA

[bibi21000]

Up ...

[stefan.persson]

A small note on this, when using tdadmin, don't forget to use hex and include serial:

Code: Select all

tdadmin controller connect --pid=0x0c31 --vid=0x1781 --serial=<serialnum>

where <serialnum> can be found by running

Code: Select all

lsusb -d 1781: -v | grep iSerial