Skip to content

Commit a0a539c

Browse files
canchebagurTaddyHC
andauthored
Update content/hardware/04.pro/shields/portenta-uwb-shield/tutorials/01.user-manual/content.md
Co-authored-by: TaddyHC <[email protected]>
1 parent 65a2042 commit a0a539c

File tree

1 file changed

+1
-1
lines changed
  • content/hardware/04.pro/shields/portenta-uwb-shield/tutorials/01.user-manual

1 file changed

+1
-1
lines changed

content/hardware/04.pro/shields/portenta-uwb-shield/tutorials/01.user-manual/content.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -928,7 +928,7 @@ uint8_t destination[]={0x22,0x22};
928928

929929
***<strong>Important note:</strong> Notice how the MAC addresses are reversed between the two devices; this is critical for proper communication. In UWB communication, each device must know both its own address (`devAddr`) and the address of the device it is communicating with (`destination`). The Portenta UWB Shield identifies itself as `0x2222` and expects to communicate with `0x1111`, while the Arduino Stella identifies itself as `0x1111` and expects to communicate with `0x2222`. If these addresses don't match correctly, the devices won't be able to establish a ranging session. The prefix `0x` indicates these are hexadecimal values, which is a common notation in programming for representing memory addresses and identifiers.***
930930

931-
The MAC addresses used in this example are short (2-byte) addresses for simplicity, but UWB also supports extended (8-byte) addressing for larger networks where unique identification is required. For basic two-device setups, these short addresses are enough, but for multi-node positioning systems, you may want to use extended addressing to avoid conflicts.
931+
The MAC addresses used in this example are short (2-byte) addresses for simplicity, but UWB also supports extended (8-byte) addresses for larger networks where unique identification is required. For basic two-device setups, these short addresses are enough, but for multi-node positioning systems, you may want to use extended addressing to avoid conflicts.
932932

933933
2. **Setup and Initialization**
934934

0 commit comments

Comments
 (0)