AzuritBer Firmware (English): Unterschied zwischen den Versionen

Aus www.wiki.ardumower.de
Wechseln zu: Navigation, Suche
(AzuritBer Wiki)
Zeile 1: Zeile 1:
=='''AZURITBER is based on Azurit firmware and use PCB1.3'''==
+
= AZURITBER is based on Azurit firmware and use PCB1.3 =
  
 
TODO structural
 
TODO structural
  
The main difference is in the motor control management, The BER version always use odometry into all movement.
 
  
All the firmware  is write with a raspberry PI (running Python Piardu.py code) connected on DUE usb native port and many message are send and store in the Raspberry console.
+
=Test requirements=
The PI is actualy optional, but help a lot to find trouble in the behaviour.
+
[[File:warning.png]]Security note: For security reasons, always remove mower blades in your first tests!
 +
 
 +
[[File:warning.png]]Important: For your first wheel motor tests, jack your robot so that the tires can run freely without ground contact!
 +
 
 +
=What is AzuritBer and Why=
 +
 
 +
Actual Azurit use timer to control the state change.
 +
It's very good way for many platform and full compatibility with DUE or MEGA board.
 +
 
 +
AzuritBer use Odometry or IMU to control the state change.
 +
The BER version always use odometry into all movement and the timer is only here to help in stuck mode.
 +
The result is a more smooth movement without pause between all the diffrents state.
 +
At the beginning of the dev i need many debug message to perfectly setup the firmware, so i add a raspberry and record all the mowing stage duration in a Console.
 +
Actually PI is optional, but help a lot to find trouble in the behaviour and to communicate (With your PC,or home automation)
 +
Other option is the RFID tag reader that help :
 +
To manage up to 3 mowing area without any wire connection between them.(1 Station sender and 2 wifi sender for other area)
 +
To help the back to station very fast.
 +
To escape from island
 +
To change tracking speed (For example reduce just before docking)
 +
 
 +
 
  
  

Version vom 27. Oktober 2020, 14:51 Uhr

AZURITBER is based on Azurit firmware and use PCB1.3

TODO structural


Test requirements

Warning.pngSecurity note: For security reasons, always remove mower blades in your first tests!

Warning.pngImportant: For your first wheel motor tests, jack your robot so that the tires can run freely without ground contact!

What is AzuritBer and Why

Actual Azurit use timer to control the state change. It's very good way for many platform and full compatibility with DUE or MEGA board.

AzuritBer use Odometry or IMU to control the state change. The BER version always use odometry into all movement and the timer is only here to help in stuck mode. The result is a more smooth movement without pause between all the diffrents state. At the beginning of the dev i need many debug message to perfectly setup the firmware, so i add a raspberry and record all the mowing stage duration in a Console. Actually PI is optional, but help a lot to find trouble in the behaviour and to communicate (With your PC,or home automation) Other option is the RFID tag reader that help : To manage up to 3 mowing area without any wire connection between them.(1 Station sender and 2 wifi sender for other area) To help the back to station very fast. To escape from island To change tracking speed (For example reduce just before docking)



So to start,the Odometry,Arduino DUE are mandatory and IMU highly recommended.

Prerequise to follow this WIKI: BT Module connected on PCB1.3 (ESP32 is also possible) and Arduremote into Android phone