This commit is contained in:
2025-07-05 17:19:28 -04:00
parent a04b090e1b
commit adcf95d19a
8 changed files with 28 additions and 2 deletions

View File

@@ -20,6 +20,10 @@ It's intended to be sent from a transmitting device (like a remote control or ma
uint8_t motor4_rpm_pwm; uint8_t motor4_rpm_pwm;
} __attribute__((packed)) sensors_data_t; } __attribute__((packed)) sensors_data_t;
When used with communication protocols like ESP-NOW, this struct is **encoded** into a byte stream, then
**transmitted** at regular intervals or in response to user input, and finally
**decoded** on the receiving end to control hardware.
Struct Walkthrough Struct Walkthrough
^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^

View File

@@ -51,6 +51,9 @@ Its intended to be sent from a transmitting device (like a remote control or
<span class="p">}</span><span class="w"> </span><span class="n">__attribute__</span><span class="p">((</span><span class="n">packed</span><span class="p">))</span><span class="w"> </span><span class="n">sensors_data_t</span><span class="p">;</span> <span class="p">}</span><span class="w"> </span><span class="n">__attribute__</span><span class="p">((</span><span class="n">packed</span><span class="p">))</span><span class="w"> </span><span class="n">sensors_data_t</span><span class="p">;</span>
</pre></div> </pre></div>
</div> </div>
<p>When used with communication protocols like ESP-NOW, this struct is <strong>encoded</strong> into a byte stream, then
<strong>transmitted</strong> at regular intervals or in response to user input, and finally
<strong>decoded</strong> on the receiving end to control hardware.</p>
<section id="struct-walkthrough"> <section id="struct-walkthrough">
<h2>Struct Walkthrough<a class="headerlink" href="#struct-walkthrough" title="Link to this heading"></a></h2> <h2>Struct Walkthrough<a class="headerlink" href="#struct-walkthrough" title="Link to this heading"></a></h2>
<p><em>x_axis</em> and <em>y_axis</em> fields capture analog input from a joystick, determining direction and speed. <p><em>x_axis</em> and <em>y_axis</em> fields capture analog input from a joystick, determining direction and speed.

File diff suppressed because one or more lines are too long

View File

@@ -1,4 +1,4 @@
# Sphinx build info version 1 # Sphinx build info version 1
# This file records the configuration used when building these files. When it is not found, a full rebuild will be done. # This file records the configuration used when building these files. When it is not found, a full rebuild will be done.
config: b38705e9208fae3c4e0e02be9136bc77 config: 68e99aaebec40afde1c4d6ea4d6cf9f8
tags: 62a1e7829a13fc7881b6498c52484ec0 tags: 62a1e7829a13fc7881b6498c52484ec0

View File

@@ -640,6 +640,21 @@ It&rsquo;s intended to be sent from a transmitting device (like a remote control
</pre> </pre>
</div> </div>
</div> </div>
<p>
When used with communication protocols like ESP-NOW, this struct is
<strong>
encoded
</strong>
into a byte stream, then
<strong>
transmitted
</strong>
at regular intervals or in response to user input, and finally
<strong>
decoded
</strong>
on the receiving end to control hardware.
</p>
<section id="struct-walkthrough"> <section id="struct-walkthrough">
<h3> <h3>
Struct Walkthrough Struct Walkthrough

View File

@@ -20,6 +20,10 @@ It's intended to be sent from a transmitting device (like a remote control or ma
uint8_t motor4_rpm_pwm; uint8_t motor4_rpm_pwm;
} __attribute__((packed)) sensors_data_t; } __attribute__((packed)) sensors_data_t;
When used with communication protocols like ESP-NOW, this struct is **encoded** into a byte stream, then
**transmitted** at regular intervals or in response to user input, and finally
**decoded** on the receiving end to control hardware.
Struct Walkthrough Struct Walkthrough
^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^