Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network_protocol_programming_lab:15.3_4_exercise [2021/04/19 12:31] – [Tasks] rathke | network_protocol_programming_lab:15.3_4_exercise [2021/04/19 12:38] (current) – [Requirements] rathke | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| * a ready BeagleBone Black equipped with the CC1200. | * a ready BeagleBone Black equipped with the CC1200. | ||
| - | * 5C attached to a second BeagleBone Black equipped with the CC1200. | + | * 4C attached to a second BeagleBone Black equipped with the CC1200. |
| ===== Tasks ===== | ===== Tasks ===== | ||
| Line 20: | Line 20: | ||
| * enter charters in the the text window. You will see, that '' | * enter charters in the the text window. You will see, that '' | ||
| * export all registers to a file. This means 208 registers must be exported. | * export all registers to a file. This means 208 registers must be exported. | ||
| - | * connect | + | * login to the second |
| - | * copy the export file from SmartRF | + | * copy the export file from 4C Studio to the BeagleBone Black |
| * import the export file into your program and initialize the registers according the values of the export file. | * import the export file into your program and initialize the registers according the values of the export file. | ||
| * verify that the registers have been written correctly. | * verify that the registers have been written correctly. | ||
| * Read chapter 8 about the packet handling of the [[http:// | * Read chapter 8 about the packet handling of the [[http:// | ||
| - | * Bring SmartRF | + | * Bring 4C Studio in “RX Packet Mode", change the '' |
| - | * start the transmitter. At the receiver | + | * start the transmitter. At the receiver, you should now receive the packets |
| If you are able to transmit packets in fixed length mode, the next step will be to transmit packets in variable length mode: | If you are able to transmit packets in fixed length mode, the next step will be to transmit packets in variable length mode: | ||
| - | * go back to SmartRF Studio | + | * go back to 4C and change the '' |
| * look, which registers have been changed. | * look, which registers have been changed. | ||
| * modify the changed registers in your program. You do not need to reexport the complete registers. | * modify the changed registers in your program. You do not need to reexport the complete registers. | ||
| * now, implement variable length packets and test it. | * now, implement variable length packets and test it. | ||
| - | |||
| - | |||
| - | * connect the first BeagleBone Black to your computer and install, execute 4C. | ||
| - | * open "RX Packet Mode" in test window. Some registers in the register view will change their value. | ||
| - | * in the option '' | ||
| - | * now, choose an appropriate length of the '' | ||
| - | * export all registers to a file. This means 208 registers must be exported. | ||
| - | * login to the second BeagleBone Black as superuser. | ||
| - | * copy the export file from 4C to the BeagleBone Black | ||
| - | * import the export file into your program and initialize the registers according the values of the export file. | ||
| - | * verify that the registers have been written correctly. | ||
| - | * Read chapter 8 about the packet handling of the [[http:// | ||
| - | * Bring 4C “TX Packet Mode", change the '' | ||
| - | * start the transmitter. At the receiver, the BeagleBone Black, You should now receive the packets. | ||
| - | |||
| - | If you are able to receive packets in fixed length mode, the next step will be to receive packets in variable length mode: | ||
| - | |||
| - | * go back to 4C and change the '' | ||
| - | * look, which registers have been changed. | ||
| - | * modify the changed registers in your program. You do not need to reexport the complete registers. | ||
| - | * now, implement variable length packets and test it. | ||
| ===== Hints ===== | ===== Hints ===== | ||
| - | * keep in mind, that SmartRF Studio receiver will expect a CRC. | + | * same hints as by receiving packets. |
