docs: Add changes for v4.7.0.

Author: kwagyeman

docs/library/omv.ml.postprocessing.rst

@@ -28,6 +28,26 @@ Constructors
     E.g. ``[[((x, y, w, h), score)]]``. Note that empty class list are included in the output to ensure the position
     of each class list in the output matches the position of the class index in the model output.
 
+class yolo_lc_postprocess -- YOLO LC
+------------------------------------
+
+Used to post-process YOLO LC model output.
+
+Constructors
+~~~~~~~~~~~~
+
+.. class:: yolo_lc_postprocess(threshold:float=0.6, anchors:List[Tuple[float, float]]=None, nms_threshold:float=0.1, nms_sigma:float=0.1) -> yolo_lc_postprocess
+
+    Create a YOLO LC postprocessor.
+
+    ``threshold`` The threshold to use for postprocessing.
+
+    ``anchors`` A list of anchor points ``(x, y)`` the model was trained on  to use for postprocessing.
+
+    This post-processor returns a list of rect ``[x, y, w, h]`` and score tuples for each class in the model output.
+    E.g. ``[[((x, y, w, h), score)]]``. Note that empty class list are included in the output to ensure the position
+    of each class list in the output matches the position of the class index in the model output.
+
 class yolo_v2_postprocess -- YOLO V2
 ------------------------------------
 
@@ -65,3 +85,21 @@ Constructors
     This post-processor returns a list of rect ``[x, y, w, h]`` and score tuples for each class in the model output.
     E.g. ``[[((x, y, w, h), score)]]``. Note that empty class list are included in the output to ensure the position
     of each class list in the output matches the position of the class index in the model output.
+
+class yolo_v8_postprocess -- YOLO V8
+------------------------------------
+
+Used to post-process YOLO V8 model output.
+
+Constructors
+~~~~~~~~~~~~
+
+.. class:: yolo_v8_postprocess(threshold:float=0.6, nms_threshold:float=0.1, nms_sigma:float=0.1) -> yolo_v8_postprocess
+
+    Create a YOLO V8 postprocessor.
+
+    ``threshold`` The threshold to use for postprocessing.
+
+    This post-processor returns a list of rect ``[x, y, w, h]`` and score tuples for each class in the model output.
+    E.g. ``[[((x, y, w, h), score)]]``. Note that empty class list are included in the output to ensure the position
+    of each class list in the output matches the position of the class index in the model output.

docs/library/omv.rpc.rst

@@ -392,45 +392,3 @@ Be controlled by another ``rpc`` device over Async Serial (UART).
 
    NOTE: Master and slave baud rates must match. Connect master tx to slave rx and master rx to
    slave tx. Finally, both devices must share a common ground.
-
-class rpc_usb_vcp_master - USB VCP Master Interface
----------------------------------------------------
-
-Control another ``rpc`` device over a USB Virtual COM Port.
-
-.. class:: rpc_usb_vcp_master()
-
-   Creates a USB VCP ``rpc`` master. This interface can move data at the USB speed.
-
-class rpc_usb_vcp_slave - USB VCP Slave Interface
--------------------------------------------------
-
-Be controlled by another ``rpc`` device over a USB Virtual COM Port.
-
-.. class:: rpc_usb_vcp_slave()
-
-   Creates a USB VCP ``rpc`` slave. This interface can move data at the USB speed.
-
-class rpc_network_master - Network Master Interface
----------------------------------------------------
-
-Control another ``rpc`` device over a network.
-
-.. class:: rpc_network_master(network_if, port=0x1DBA)
-
-   Creates a Network ``rpc`` master.
-
-   * network_if - Network interface created from ``network.LAN()``, ``network.WLAN()``, or etc.
-   * port - Port to route traffic to.
-
-class rpc_network_slave - Network Slave Interface
----------------------------------------------------
-
-Be controlled by another ``rpc`` device a network.
-
-.. class:: rpc_network_slave(network_if, port=0x1DBA)
-
-   Creates a Network ``rpc`` slave.
-
-   * network_if - Network interface created from ``network.LAN()``, ``network.WLAN()``, or etc.
-   * port - Port to route traffic to.

docs/library/omv.sensor.rst

@@ -573,6 +573,7 @@ Functions
    * `sensor.IOCTL_RGB_STATS` - Pass this enum to get the RGB statistics from the camera sensor. Returns a tuple of (r, gb, gr, b) values.
    * `sensor.IOCTL_GENX320_SET_BIASES` - Pass this enum followed by a bias enum to set the GENX320 sensor biases.
    * `sensor.IOCTL_GENX320_SET_BIAS` - Pass this enum followed by a bias enum and a bias value to set the GENX320 sensor bias.
+   * `sensor.IOCTL_GENX320_SET_AFK` - Pass this enum followed by `enable, freq_low_in_hz, freq_high_in_hz` to change the GENX320 anti-flickering-filter settings.
 
 .. function:: set_color_palette(palette:int) -> None
 
@@ -1118,6 +1119,11 @@ Constants
 
    Lets you set the GENX320 camera sensor biases. See `sensor.ioctl()` for more information.
 
+.. data:: IOCTL_GENX320_SET_AFK
+   :type: int
+
+   Lets you set the GENX320 camera sensor anti-flickering-filter. See `sensor.ioctl()` for more information.
+
 .. data:: GENX320_BIASES_DEFAULT
    :type: int
 

docs/library/omv.tof.rst

@@ -36,7 +36,7 @@ Functions
    ``type`` indicates the type of thermopile shield:
 
       * `tof.TOF_NONE`: 0 pixels.
-      * `tof.TOF_VL53L5CX`: 8x8 pixels.
+      * `tof.TOF_VL53LX`: 8x8 pixels.
 
    By default type is ``-1`` which will cause `tof.init()` to automatically scan and initialize an
    attached thermal sensor based on the I2C address.
@@ -48,7 +48,7 @@ Functions
    ``type`` indicates the type of thermopile shield:
 
       * `tof.TOF_NONE`: 0 pixels.
-      * `tof.TOF_VL53L5CX`: 8x8 pixels.
+      * `tof.TOF_VL53LX`: 8x8 pixels.
 
    By default type is ``-1`` which will cause `tof.init()` to automatically scan and initialize an
    attached thermal sensor based on the I2C address.
@@ -62,28 +62,28 @@ Functions
    Returns the width (horizontal resolution) of the depth sensor in-use:
 
       * `tof.TOF_NONE`: 0 pixels.
-      * `tof.TOF_VL53L5CX`: 8 pixels.
+      * `tof.TOF_VL53LX`: 8 pixels.
 
 .. function:: height() -> int
 
    Returns the height (vertical resolution) of the depth sensor in-use:
 
       * `tof.TOF_NONE`: 0 pixels.
-      * `tof.TOF_VL53L5CX`: 8 pixels.
+      * `tof.TOF_VL53LX`: 8 pixels.
 
 .. function:: type() -> int
 
    Returns the type of the depth sensor in-use:
 
       * `tof.TOF_NONE`
-      * `tof.TOF_VL53L5CX`
+      * `tof.TOF_VL53LX`
 
 .. function:: refresh() -> int
 
    Returns the refresh rate of the depth sensor in-use:
 
       * `tof.TOF_NONE`: 0 Hz.
-      * `tof.TOF_VL53L5CX`: 15 Hz.
+      * `tof.TOF_VL53LX`: 15 Hz.
 
 .. function:: read_depth(hmirror:bool=False, vflip:bool=False, transpose:bool=False, timeout:int=-1)
 
@@ -266,7 +266,7 @@ Constants
 
    No TOF sensor type.
 
-.. data:: TOF_VL53L5CX
+.. data:: TOF_VL53LX
    :type: int
 
-   VL53L5CX TOF sensor.
+   VL53L5CX or VL53L8CX TOF sensor.

docs/openmvcam/general.rst

@@ -6,16 +6,23 @@ General information about the openmvcam
 Local filesystem and SD card
 ----------------------------
 
-There is a small internal filesystem (a drive) on the openmvcam which is stored
-within the microcontroller's flash memory.
+There is a small internal filesystem (a drive) on the openmvcam, called ``/flash``,
+which is stored within the microcontroller's flash memory.  If a micro SD card
+is inserted into the slot, it is available as ``/sdcard``.
 
 When the openmvcam boots up, it needs to choose a filesystem to boot from.  If
-there is no SD card, then it uses the internal filesystem as the boot
-filesystem, otherwise, it uses the SD card.  After the boot, the current
-directory is set to ``/``.
+there is no SD card, then it uses the internal filesystem ``/flash`` as the boot
+filesystem, otherwise, it uses the SD card ``/sdcard``. After the boot, the current
+directory is set to one of the directories above.
+
+If needed, you can prevent the use of the SD card by creating an empty file
+called ``/flash/SKIPSD``.  If this file exists when the openmvcam boots
+up then the SD card will be skipped and the openmvcam will always boot from the
+internal filesystem (in this case the SD card won't be mounted but you can still
+mount and use it later in your program using ``vfs.mount``).
 
 The boot filesystem is used for 2 things: it is the filesystem from which
-``boot.py`` and ``main.py`` files are searched for, and it is the filesystem
+the ``boot.py`` and ``main.py`` files are searched for, and it is the filesystem
 which is made available on your PC over the USB cable.
 
 The filesystem will be available as a USB flash drive on your PC.  You can
@@ -26,18 +33,7 @@ pyboard.*
 
 .. note::
 
-   The above behavior is different from the pyboard which allows access to the
-   internal file system and SD card at the same time within a script by creating
-   a virtual file system with multiple drives for the internal flash and SD
-   card.  The OpenMV Cam's behavior is different because modern operating systems
-   do not mount the OpenMV Cam's internal flash drive and/or SD Card as a
-   virtual file system but instead as a block device... meaning that modern
-   operating systems do not see a pyboard's file system the same way as the
-   pyboard sees it.  To avoid this situation we only allow one file system at a
-   time to keep the operating system the OpenMV Cam is attached to and what the
-   OpenMV Cam thinks its file system looks like in sync.
-
-   That said, there is another complication.  Because modern operating systems
+   Because modern operating systems
    mount the OpenMV Cam's internal flash drive or SD card as a block device they
    treat it as if it cannot create files itself.  Because of this if you create
    a file onboard your OpenMV Cam in code you must remount the OpenMV Cam after

docs/openmvcam/pinout-openmv-ae3-pag7936.png

@@ -12,6 +12,14 @@ the OpenMV Cam please consider reading the following sections first:
    general.rst
    tutorial/index.rst
 
+.. image:: pinout-openmv-n6-pag7936.png
+    :alt: OpenMV N6 PAG7936 Pinout
+    :width: 700px
+
+.. image:: pinout-openmv-ae3-pag7936.png
+    :alt: OpenMV AE3 PAG7936 Pinout
+    :width: 700px
+
 .. image:: pinout-openmv-cam-rt1062-ov5640.png
     :alt: OpenMV Cam RT1062 OV5640 Pinout
     :width: 700px

docs/openmvcam/pinout-openmv-n6-pag7936.png

@@ -8,6 +8,18 @@ can create a system that's able to "sense", "plan", and "act" in one package.
 
 First, let's take a look at your OpenMV Cam's pinout below:
 
+.. image:: ../pinout-openmv-n6-pag7936.png
+    :alt: OpenMV N6 PAG7936 Pinout
+    :width: 700px
+
+.. image:: ../pinout-openmv-ae3-pag7936.png
+    :alt: OpenMV AE3 PAG7936 Pinout
+    :width: 700px
+
+.. image:: ../pinout-openmv-cam-rt1062-ov5640.png
+    :alt: OpenMV Cam RT1062 OV5640 Pinout
+    :width: 700px
+
 .. image:: ../pinout-openmv-cam-h7-plus-ov5640.png
     :alt: OpenMV Cam H7 Plus OV5640 Pinout
     :width: 700px

docs/openmvcam/quickref.rst

@@ -140,6 +140,11 @@ looking for errors. When OpenMV IDE detects and error it will automatically
 open the file in error and highlight the line in error along with displaying
 a nice error message box. This feature saves you tons of time fixing errors.
 
+.. note::
+
+   The serial terminal in the IDE shows text output from the OpenMV Cam.
+   It does not allow you to send data to the OpenMV Cam.
+
 Anyway, if you want to stop the script just click on the stop button which will
 replace the run button while a script is running. Note that scripts can
 automatically stop by themselves either due to finishing or a compile error. In