FHEM/fhem-mirror
2
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-03-10 09:16:53 +00:00
Code Issues Releases Wiki Activity

# RSSI: radio signal strength with correct negative sign

Browse Source 
git-svn-id: https://svn.fhem.de/fhem/trunk@3745 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
klaus-schauer 2013-08-18 19:14:51 +00:00
parent ffca52b256
commit 72662bf1b7
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
fhem/FHEM/00_TCM.pm
View File

@ -316,10 +316,10 @@ TCM_Read($)
PacketType => $packetType, PacketType => $packetType,
SubTelNum => hex($1), SubTelNum => hex($1),
DestinationID => $2, DestinationID => $2,
RSSI => hex($3), RSSI => -hex($3),
SecurityLevel => hex($4), SecurityLevel => hex($4),
); );
$hash->{RSSI} = hex($3); $hash->{RSSI} = -hex($3);
if ($blockSenderID eq "own" && (hex $id) >= $baseID && (hex $id) <= $lastID) { if ($blockSenderID eq "own" && (hex $id) >= $baseID && (hex $id) <= $lastID) {
Log $ll5, "TCM: $name Telegram from $id blocked."; Log $ll5, "TCM: $name Telegram from $id blocked.";
@ -760,9 +760,10 @@ TCM_Undef($$)
<ul> <ul>
The TCM module serves an USB or TCP/IP connected TCM120 or TCM310 EnOcean The TCM module serves an USB or TCP/IP connected TCM120 or TCM310 EnOcean
Transceiver module. These are mostly packaged together with a serial to USB Transceiver module. These are mostly packaged together with a serial to USB
chip and an antenna, e.g. the BSC BOR contains the TCM120, the EUL from chip and an antenna, e.g. the BSC BOR contains the TCM120, the <a
busware contains a TCM310. See also the datasheet available from <a href="http://www.enocean.com/de/enocean_module/usb-300-oem/">USB 300</a> from
href="http://www.enocean.com">www.enocean.com</a>. EnOcean and the EUL from busware contains a TCM310. See also the datasheet
available from <a href="http://www.enocean.com">www.enocean.com</a>.
<br> <br>
As the TCM120 and the TCM310 speak completely different protocols, this As the TCM120 and the TCM310 speak completely different protocols, this
module implements 2 drivers in one. It is the "physical" part for the <a module implements 2 drivers in one. It is the "physical" part for the <a
@ -784,7 +785,7 @@ TCM_Undef($$)
<code>device</code> can take the same parameters (@baudrate, @directio, <code>device</code> can take the same parameters (@baudrate, @directio,
TCP/IP, none) like the <a href="#CULdefine">CUL</a>, but you probably have TCP/IP, none) like the <a href="#CULdefine">CUL</a>, but you probably have
to specify the baudrate: the TCM120 should be opened with 9600 Baud, the to specify the baudrate: the TCM120 should be opened with 9600 Baud, the
TCM310 with 57600 baud. TCM310 with 57600 baud.<br>
Example: Example:
<ul><code> <ul><code>
define BscBor TCM 120 /dev/ttyACM0@9600<br> define BscBor TCM 120 /dev/ttyACM0@9600<br>