Page 1 of 1
RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Sat Jun 28, 2014 9:05 pm
by digineut
I have received my RFXCOM E type today and tried to use it with domoticz. I installed the latest USB to serial driver. On my recent iMac (OS X 10.9.3) (for testing purposes) it was recognized immediately. It switches my KAKU perfectly. Then I tried to connect the RFXCOM module to the Mac Mini that acts as my actual server. This Mac Mini runs Mac OS X 10.6.8. On this machine the RFXCOM shows errors. The serial port is not working.
What is wrong? Can someone please help me?
This is some of my log:
Code: Select all
Sat Jun 28 20:52:39 2014 Domoticz V1.1812 (c)2012-2014 GizMoCuz
Sat Jun 28 20:52:39 2014 Startup Path: /Users/boss/bin/domoticz/
Sat Jun 28 20:52:39 2014 Stopping all hardware...
Sat Jun 28 20:52:39 2014 Webserver started on port: 8088
Sat Jun 28 20:52:42 2014 RFXCOM: Using serial port: /dev/tty.usbserial-A1XQFD94
Sat Jun 28 20:52:42 2014 Error: Serial Port closed!... Error: Invalid argument
Sat Jun 28 20:52:43 2014 RFXCOM: retrying in 30 seconds...
Sat Jun 28 20:53:12 2014 RFXCOM: Using serial port: /dev/tty.usbserial-A1XQFD94
Sat Jun 28 20:53:12 2014 Error: Serial Port closed!... Error: Invalid argument
Sat Jun 28 20:53:14 2014 RFXCOM: retrying in 30 seconds...
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Sun Jun 29, 2014 8:14 am
by digineut
Some googling gives me the impression that the serial port probably is not accessible. But the basics seem to be OK.
The command
shows
Code: Select all
crw-rw-rw- 1 root wheel 10, 0 29 jun 07:48 /dev/tty.usbserial-A1XQFD94
The command
Code: Select all
stty -f /dev/tty.usbserial-A1XQFD94
shows
Code: Select all
speed 9600 baud;
lflags: -icanon -isig -iexten -echo
iflags: -icrnl -ixon -ixany -imaxbel -brkint
oflags: -opost -onlcr -oxtabs
cflags: cs8 -parenb
(Both results are identical on 10.9.3 and 10.6.
Does anyone have some tips?
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Sun Jun 29, 2014 9:38 am
by digineut
I have installed
rfxcmd to listen to the receiver and everything seems to be fine, so what could be wrong then?
Command
Code: Select all
./rfxcmd.py -d /dev/tty.usbserial-A1XQFD94 -a LISTEN
Output
Code: Select all
RFXCMD Version 0.3 (515)
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:29:30
Packet Length = 0D
Packettype = Interface Message
Subtype = Interface response
Sequence nbr = 00
Response on cmnd = Get Status, return firmware versions and configuration of the interface.
Transceiver type = 433.92MHz (Transceiver)
Firmware version = 226
Display undecoded = Off
Protocols:
Disabled AE (433.92)
Disabled Rubicson (433.92)
Disabled FineOffset / Viking (433.92)
Disabled RFU3
Disabled RFU4
Disabled RFU5
Disabled RFU6
Disabled Mertik (433.92)
Disabled AD (433.92)
Enabled Hideki/UPM (433.92)
Enabled La Crosse (433.92/868.30)
Disabled FS20 (868.35)
Disabled ProGuard (868.35 FSK)
Disabled BlindsT0 (433.92)
Disabled BlindsT1/T2/T3 (433.92)
Enabled X10 (310/433.92)
Enabled ARC (433.92)
Enabled AC (433.92)
Disabled HomeEasy EU (433.92)
Disabled Meiantech (433.92)
Enabled Oregon Scientific (433.92)
Disabled ATI (433.92)
Disabled Visonic (315/868.95)
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:30:37
Packet Length = 0B
Packettype = Lighting2
Subtype = AC
Seqnbr = 00
Id = ***
Unitcode = 1
Command = On
Dim level = 100%
Signal level = 7
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:30:43
Packet Length = 0B
Packettype = Lighting2
Subtype = AC
Seqnbr = 01
Id = ***
Unitcode = 2
Command = On
Dim level = 100%
Signal level = 6
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:30:46
Packet Length = 0B
Packettype = Lighting2
Subtype = AC
Seqnbr = 02
Id = ***
Unitcode = 3
Command = On
Dim level = 100%
Signal level = 6
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:30:50
Packet Length = 0B
Packettype = Lighting2
Subtype = AC
Seqnbr = 03
Id = ***
Unitcode = 1
Command = Group Off
Dim level = 0%
Signal level = 6
------------------------------------------------
Received = ***
Date/Time = 2014-06-29 09:31:54
Packet Length = 08
Packettype = Temperature sensors
Subtype = TS15C
Seqnbr = 04
Id = ***
Temperature = 19.8 C
Battery = 9
Signal level = 4
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Sun Jun 29, 2014 2:29 pm
by b_weijenberg
The baud rate to be used is 38400
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Sun Jun 29, 2014 5:06 pm
by digineut
b_weijenberg wrote:The baud rate to be used is 38400
I did 2 identical installations on different Macs. I did not change any of the default settings for both Domoticz and the RFXCOM driver. So why does the newer iMac work and the Mac Mini not? Perhaps one uses a higher rate than the other? How can I see what baud rate is being used by Domoticz?
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Mon Jun 30, 2014 9:58 am
by b_weijenberg
digineut wrote:How can I see what baud rate is being used by Domoticz?
Good question for the Domoticz forum.
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Mon Jun 30, 2014 10:33 pm
by digineut
Thans for all your support. I have decided to move to openHAB. This does support more stuff and runs more easily on my Mac Mini. RFXCOM is working perfectly now.
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Wed Mar 25, 2015 2:23 pm
by Babblu
I tried to force to assign an ip-adres to its mac-adres but no luck. Something is wrong but what? The networkleds of the RFXcom come on when power is connected but there is no communications. Green led goes after a few blinks. I tried to reset the RFXCOM but i can not figure out how. There is no resetbutton. I read the specs off the lantronic WiPortNR and it have a restpin. But how do i activate it? Documentation is very poor on this version. Who can help my?
Re: RFXCOM serial port problem on Mac OS X 10.6.8
Posted: Wed Mar 25, 2015 5:16 pm
by b_weijenberg
The RFXCOM LAN is not supported by Indigo.
The RFXtrx433E can be used.