livebox:universalrfrx

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
livebox:universalrfrx [2013/06/25 10:57] – [Universal RF Rx] brettlivebox:universalrfrx [2017/09/15 12:37] (current) brett
Line 5: Line 5:
 {{:livebox:urfrx-block-diagram.png}} {{:livebox:urfrx-block-diagram.png}}
  
-With the virtual serial port mode this makes it possible to combine the HAHCentral sketch with the RFRX receiver code module.  One piece of hardware can be used to communicate with the [[hah_hahnode|HAHNodes]] and with the 433Mhz RF receiver hardware.+With the virtual serial port mode this makes it possible to combine the HAHCentral sketch with the RFRX receiver code module.  One piece of hardware can be used to communicate with the [[hah_hahnode|HAHNodes]] and with the 433MHz RF receiver hardware.
  
 +It would also allow you to combine say the RFGateway sketch using the Nanode hardware with the RF hardware and have the xap-serial message being dumped directly onto the Ethernet.  Many options available with these architecture choices.
 ===== The receiver ===== ===== The receiver =====
  
 The hardware to slurp and detect what looks like a valid RF signal from all the background noise.  With this hardware we don't pre-code what RF signals we are going to look for, which is what most purpose built RF receivers do. The hardware to slurp and detect what looks like a valid RF signal from all the background noise.  With this hardware we don't pre-code what RF signals we are going to look for, which is what most purpose built RF receivers do.
  
-The source: http://livebox-hah.googlecode.com/svn/trunk/userapps/arduinoYou will also need the RFRX Library .+The source: https://github.com/dbzoo/hah/tree/master/userapps/arduino You will also need the RFRX Library . 
 + 
 +<note>The RFRX library is part of the HAHCentral sketch so by attaching a RF receiver to this existing hardware you can get this functionality for very little extra cost.  Just the cost of a RF Rx unit, which is about 3-4 quid.</note>
  
 The beautiful part of this design is the separation of the signal gatherer from the decoder.  We look for a signal that has a lead-in >10ms and repeats more than once.   If this condition is met we emit the pulse stream for a repeating block out to the serial port for the decoder to deal with. The beautiful part of this design is the separation of the signal gatherer from the decoder.  We look for a signal that has a lead-in >10ms and repeats more than once.   If this condition is met we emit the pulse stream for a repeating block out to the serial port for the decoder to deal with.
Line 64: Line 67:
 rf1.on=010201820436046A015601700436045001700101271018100001820339 rf1.on=010201820436046A015601700436045001700101271018100001820339
 enable=1 enable=1
-usbserial=/dev/ttyUSB1+serialport=/dev/ttyUSB0 
 +vserial=1
 </code> </code>
 +
 +  * vserial - Virtual Serial port (1) or Directly connected hardware (0)
 +  * enable - Start this service automatically 
  
 Each RF<number>.STATE pattern is created as a BSC endpoint.  When a signal comes in that matches our definition the endpoint will have its state changed accordingly and an xAPBSC.event will be generated. Each RF<number>.STATE pattern is created as a BSC endpoint.  When a signal comes in that matches our definition the endpoint will have its state changed accordingly and an xAPBSC.event will be generated.
  • livebox/universalrfrx.1372157841.txt.gz
  • Last modified: 2013/06/25 10:57
  • by brett