Version List

More documents

Recommendations

Info

Transceiver module TRX433-10C2 / TRX868-10C2 (Vers. 1.0E) 12 Example for a continued radio data stream (radio telegram with more than 61 bytes payload) A continued radio data stream (thus a telegram which isn’t limited to 61 bytes payload) can only be realized with Fast send and without CRC16. Also, the RS232-baud rate has to be chosen at least as fast as the RF data rate. With these configurations, a continued radio data stream like in figure 9 can be realized. It is also apparent in Figure 9 how the CTS pin may prevent the transceiver module from outputting the data via RS232 that it received via radio. Also you can see the number of bytes in the transmittion buffer (TX-BUF) of the sending transceiver module and the numbers of bytes in the receiving buffer (RX-BUR) of the receiving transceiver module. module 1 module 2 bytes in TX-BUF RS232, RTS-pin RS232, RxD-pin RF-transmission RS232, TxD-pin RS232, CTS-pin bytes in RX-BUF 0.... 1.... 2.... 3.... 4.... 5.... 6.... 7.... 8.... 9....10...11...12...12...12...13...13...14...14...15...15... Byte 1 Byte 2 Byte 3 Byte 4 32 Bit Preamble +2ms Startup Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10 24 Bit SYNC Byte 11 Byte 12 Byte 13 Byte 1 Byte 14 Byte 15 Byte 2 Byte 16 Byte 17 Byte 3 Byte 18 Byte 19 Byte 4 Byte 20 ... 0........................................................................................ 1....0....1....0.... 1....0....1....0... ....0....1....0....1....0....1..........2..........3...2.....2....1...2.1...0..1....0....1....0....1....0.. Figure 9 Dataflow with Fast send without CRC16, RS232-baud rate = 2x RF data rate Byte 5 Byte 21 Byte 121 60...60...61. 60........59........ 58...59...59...60...60...61.60.... 59........58... 59...59... Example for continued data stream over RS232 With Fast send enabled and CRC16 disabled, a continued data stream can be realized over the RS232interface. For that, the RF data rate has to be chosen higher than the RS232-baud rate. In figure 10, a continued data stream over RS232 is shown by which the RF data rate is adjusted twice as fast as the RS232-baud rate. Further you can see how many bytes are stored in the transmittion buffer (TX-BUF) of the sending transceiver module and in the receiving buffer (RX-BUF) of the receiving transceiver module. module 1 module 2 bytes in TX-BUF RS232, RTS-pin RS232, RxD-pin RF-transmission RS232, TxD-pin RS232, CTS-pin bytes in RX-BUF Byte 1 Byte 2 Byte 3 Byte 4 ...0........... 1...........2...........3........ 2. . 3. 2...1..2.1...0....1...........2...........3......... 2.3..2....1.2...1...0..1...........2...........3..........4.3...2.... 2...1...0.1...........2...........3...........4..3...2..3. 2... Byte 1 Byte 2 32 Bit Preamble +2ms Startup Byte 3 24 Bit SYNC Byte 4 Byte 1 Byte 5 Byte 2 Byte 3 Byte 4 Byte 5 Byte 1 Byte 6 Byte 7 Byte Byte 1 8 32 Bit Preamble +2ms Startup Byte Byte 1 9 24 Bit SYNC Byte Byte 1 10 ...0....................................................... 1... 2...3.2..3...4..3.......... 2...........1.......... 0.1...2...3.2..3...4..3.......... 2...........1..........0.1...2...3.2..3...4..3.......... 2...........1...........0.1.... 2... Byte 60 Byte Byte 1 11 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10 Byte 61 Byte 122 Byte 123 Byte 61 Byte Byte 1 12 Byte 62 Byte 62 Byte 63 Byte Byte 1 13 32 Bit Preamble +2ms Startup Byte 64 Byte Byte 1 14 24 Bit SYNC Byte 124 Byte 65 Byte Byte 1 15 Byte 125 Byte 63 Byte 126 Byte 66 Byte 64 Byte 127 Byte Byte 1 16 Byte 11 Byte 12 Byte 13 Byte 14 Byte 15 Figure 10 Data stream with Fast send without CRC16, RF data rate = 2x RS232-baud rate Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte Byte 1 8 Byte Byte 1 9 Byte Byte 1 10 Byte Byte 1 11 Byte 65 Byte 128 Byte 67 Byte Byte 1 12 Byte 66 Byte Byte 1 17 Byte 67 Byte 68 Byte Byte 1 18 32 Bit Preamble +2ms Startup Byte Byte 1 13 Byte 68 Byte 69 Byte Byte 1 14 Byte 129 Byte 69 Byte Byte 1 19 Byte 70 24 Bit SYNC Byte 130 Byte Byte 1 15 Byte 70 Byte Byte 1 20 Byte 16 Byte 71 Byte 17 Byte 131 60 Byte 16 Byte 21 Byte 18
Transceiver module TRX433-10C2 / TRX868-10C2 (Vers. 1.0E) 13 RSSI of the telegram and no signal condition-RSSI To define the quality of a radio connection, the received sighnal strength indicator (RSSI) of the just received radio telegram can be output over RS232 after every received radio telegram. The signal strength will be output in dBm in addition to the payloads of the radio telegram in a twos complement. The no signal condition - RSSI can be output optionally in addition to the RSSI of the telegram. The RSSIvalue which was measured immediately after the radio telegram will be output as a no signal condition - RSSI. Out of those two RSSI-values, the signal-noise ratio can be calculated. Of course, the no signal condition-RSSI can be read out with the command “READ RSSI current” as well. You can see the output of the telegram-RSSI (RSSI TLG) and of the no signal condition-RSSI (RSSI at no signal condition) added to the payload in figure 11. Note When the function “Output of the telegram-RSSI” respectively “Output of the no signal condition - RSSI” is enabled, then those RSSI-values are buffered in the receive buffer of the transceiver following the payload until they are output over RS232. Depending on the configuration, maximum 2 additional bytes are needed in the receive buffer per radio telegram. module 1 module 2 RS232, RxD-pin RF-transmission RS232, TxD-pin Byte 1 Byte 2 Byte 3 Byte 4 start RF-transmission after 2-3 bytes break 32 Bit Preamble +2ms Startup 24 Bit SYNC Length Byte 1 Byte 2 Byte 3 Byte 4 Figure 11 Output of the telegram-RSSI and the no signal condition-RSSI CRC16 Byte 1 Byte 2 Byte 3 output after checked CRC16 Byte 4 RSSI TLG RSSI Ruhe
Page 1 and 2: Transceiver module TRX433-10C2 / TR
Page 11: Transceiver module TRX433-10C2 / TR

Version List

Create successful ePaper yourself

Delete template?

Save as template?