[MOV] documentation structure reorganization
This commit aims to improve the documentation's navigability by redefining some categories' purposes and titles. There is a redirection rule for each documentation page moved. This ensures that users won't have a 404 error message. task-3217827 closes odoo/documentation#8064 Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
This commit is contained in:
@@ -0,0 +1,52 @@
|
||||
====================
|
||||
Connect a footswitch
|
||||
====================
|
||||
|
||||
When working in a manufacturing environment, it's always better for an operator to have both hands
|
||||
available at all times. Odoo's :abbr:`IoT (Internet of Things)` box makes this possible when using a
|
||||
footswitch.
|
||||
|
||||
In fact, with a footswitch, the operator is able to go from one screen to another, and perform
|
||||
actions using their foot. This can be configured in just a few steps on the work center in the
|
||||
*Manufacturing* app.
|
||||
|
||||
Connection
|
||||
==========
|
||||
|
||||
To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect the two devices via
|
||||
cable. More often than not, this is done with a :abbr:`USB (Universal Serial Bus)` cable.
|
||||
|
||||
If the footswitch is a `supported device <https://www.odoo.com/page/iot-hardware>`_, there is no
|
||||
need to take further action, since it'll be automatically detected when connected.
|
||||
|
||||
.. image:: footswitch/footswitch-dropdown.png
|
||||
:align: center
|
||||
:alt: Footswitch recognized on the IoT box.
|
||||
|
||||
Link a footswitch to a work center in the Odoo Manufacturing app
|
||||
================================================================
|
||||
|
||||
To link a footswitch to an action, it first needs to be configured on a work center. Navigate to
|
||||
:menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, go to the desired
|
||||
:guilabel:`Work Center` in which the footswitch will be used, and add the device in the
|
||||
:guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a
|
||||
Line`. Doing so means the footswitch can be linked to an option in the :guilabel:`Action` column
|
||||
drop-down, and optionally, a key can be added to trigger it. An example of an :guilabel:`Action` in
|
||||
the *Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as Done` buttons on a
|
||||
manufacturing work order.
|
||||
|
||||
.. image:: footswitch/footswitch-example.png
|
||||
:align: center
|
||||
:alt: Footswitch trigger setup on the Odoo database.
|
||||
|
||||
.. important::
|
||||
It should be noted that the first listed trigger is chosen first. So, the order matters, and
|
||||
these triggers can be dragged into any order. In the picture above, using the footswitch
|
||||
automatically skips the part of the process that's currently being worked on.
|
||||
|
||||
.. note::
|
||||
On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is
|
||||
correctly connected to the footswitch.
|
||||
|
||||
.. seealso::
|
||||
:ref:`workcenter_iot`
|
||||
Reference in New Issue
Block a user