navigation
Home
admin
|
Domotique
October 18th, 2016
|
Je dispose un RFXcom de ce style : http://www.univers-domotique.com/rfxcom/736-rfxcom-interface-rfxlan-tcp-ip-avec-recepteur-43392mhz-et-rfxmitter.html
| Branchement sur une debian |  |
dmesg
Feb 27 16:04:41 po-04 kernel: [359617.500828] usb 3-3: new full-speed USB device number 20 using xhci_hcd
Feb 27 16:04:41 po-04 kernel: [359617.522671] usb 3-3: New USB device found, idVendor=0403, idProduct=6001
Feb 27 16:04:41 po-04 kernel: [359617.522678] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 27 16:04:41 po-04 kernel: [359617.522682] usb 3-3: Product: FT232R USB UART
Feb 27 16:04:41 po-04 kernel: [359617.522685] usb 3-3: Manufacturer: FTDI
Feb 27 16:04:41 po-04 kernel: [359617.522688] usb 3-3: SerialNumber: A800f077
Feb 27 16:04:41 po-04 mtp-probe: checking bus 3, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Feb 27 16:04:41 po-04 mtp-probe: bus: 3, device: 20 was not an MTP device
Feb 27 16:04:41 po-04 kernel: [359617.613231] usbcore: registered new interface driver usbserial
Feb 27 16:04:41 po-04 kernel: [359617.613240] USB Serial support registered for generic
Feb 27 16:04:41 po-04 kernel: [359617.613257] usbcore: registered new interface driver usbserial_generic
Feb 27 16:04:41 po-04 kernel: [359617.613258] usbserial: USB Serial Driver core
Feb 27 16:04:41 po-04 kernel: [359617.620396] USB Serial support registered for FTDI USB Serial Device
Feb 27 16:04:41 po-04 kernel: [359617.620437] ftdi_sio 3-3:1.0: FTDI USB Serial Device converter detected
Feb 27 16:04:41 po-04 kernel: [359617.620458] usb 3-3: Detected FT232RL
Feb 27 16:04:41 po-04 kernel: [359617.620459] usb 3-3: Number of endpoints 2
Feb 27 16:04:41 po-04 kernel: [359617.620460] usb 3-3: Endpoint 1 MaxPacketSize 64
Feb 27 16:04:41 po-04 kernel: [359617.620461] usb 3-3: Endpoint 2 MaxPacketSize 64
Feb 27 16:04:41 po-04 kernel: [359617.620462] usb 3-3: Setting MaxPacketSize 64
Feb 27 16:04:41 po-04 kernel: [359617.620707] usb 3-3: FTDI USB Serial Device converter now attached to ttyUSB0
Feb 27 16:04:41 npo-04 kernel: [359617.620737] usbcore: registered new interface driver ftdi_sio
Feb 27 16:04:41 npo-04 kernel: [359617.620738] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver |
udevadm info --query=all --name ttyUSB0
P: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0
N: ttyUSB0
S: serial/by-id/usb-FTDI_FT232R_USB_UART_A800f077-if00-port0
S: serial/by-path/pci-0000:00:14.0-usb-0:3:1.0-port0
E: DEVLINKS=/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A800f077-if00-port0 /dev/serial/by-path/pci-0000:00:14.0-usb-0:3:1.0-port0
E: DEVNAME=/dev/ttyUSB0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/ttyUSB0/tty/ttyUSB0
E: ID_BUS=usb
E: ID_MM_CANDIDATE=1
E: ID_MODEL=FT232R_USB_UART
E: ID_MODEL_ENC=FT232Rx20USBx20UART
E: ID_MODEL_FROM_DATABASE=FT232 USB-Serial (UART) IC
E: ID_MODEL_ID=6001
E: ID_PATH=pci-0000:00:14.0-usb-0:3:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_3_1_0
E: ID_REVISION=0600
E: ID_SERIAL=FTDI_FT232R_USB_UART_A800f077
E: ID_SERIAL_SHORT=A800f077
E: ID_TYPE=generic
E: ID_USB_DRIVER=ftdi_sio
E: ID_USB_INTERFACES=:ffffff:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=FTDI
E: ID_VENDOR_ENC=FTDI
E: ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
E: ID_VENDOR_ID=0403
E: MAJOR=188
E: MINOR=0
E: SUBSYSTEM=tty
E: UDEV_LOG=3
E: UPOWER_PRODUCT=Watts Up? Pro
E: UPOWER_VENDOR=Watts Up, Inc.
E: UP_MONITOR_TYPE=wup
E: USEC_INITIALIZED=360085966823 |
| XPL-PERL |  |
Préparation du système
perl -MCPAN -e shell
install YAML::Syck |
Repository
Comme indiqué ici http://debian.temporalanomaly.com/, j'installe ensuite le repository qui va bien.
deb http://debian.temporalanomaly.com/ squeeze main |
Installation
apt-get --allow-unauthenticated install xpl-common-perl libanyevent-rfxcom-perl |
le paquet libanyevent-rfxcom-perl permet d'éviter l'erreur "Can't locate AnyEvent.pm"
Tests
Pour que plusieurs modules xpl cohabitent sur une même machine, il est nécessaire de lancer un HUB-xpl qui va récupérer les messages UDP en broadcast sur le port 3865 et les redistribuer aux process internes, on lance donc en premier un hub xpl :
puis on lance le premier module pour recevoir les infos du rfxcom :
xpl-rfxcom-rx --interface eth0 --verbose --rfxcom-rx-tty /dev/ttyUSB0 |
J'ai eu un message d'erreur : "xPL::Dock->new: instance_id, po-04, is invalid."
A priori, le nom de ma machine ne lui convient pas : il y a un tiret dedans !
(Source : http://www.poulpy.com/2011/04/la-zibase-sur-votre-reseau-xpl/)
Solution : export export XPL_HOSTNAME=po04 |
Pour avoir des logs :
A noter que la encore, il faut instancier la variable XPL_HOSTNAME
Et ca marche, je vois les infos de ma sonde oregon...
Source : http://chiroux.org/tag/rfx-com.html
| Tableau des logiciels compatibles |  |
Source : http://blog.domadoo.fr/2011/05/24/guide-pour-choisir-son-interface-rfxcom/
| A continuer |  |
http://syno.haeflinger.com/index.php/Ma_configuration_logicielle_domotique#Installation_de_XPL-PERL
http://www.poulpy.com/page/2/
http://www.touteladomotique.com/forum/viewtopic.php?f=75&t=8575
http://www.conrad.fr/ce/fr/product/084967/Module-1-000-W-54755-Chacon
|
|
Contact
|
|---|
Pour m'envoyer un mail, Pour me laisser un commentaire :richard.brunooo chez gmail.com |  |
|
|