AzuritBer firmware

Good morning
After 2 weeks away today my mower starts again.
So my firmware is 3 weeks old. With this firmware i have a new problem.
During normal mowing the guy stops, drive back turn and go on direct on gras.
In LOG i can see that he find perimeter. But there is no perimeter.
Are there changes of perimeter sensivity?
With other words: At the borders of my ground the mower detect the wire correct. But now he also find perimeter in the middle of area.
What can i do?
Thanks
Björn
Here is the Log part:

Code:
09:47:09 Save Robot Stats
09:47:08 NORMALMOWING / POUTFOR Dir 1 State changed at 69833846 From state POUTROLL
09:47:06 NORMALMOWING / POUTROLL Dir 1 State changed at 69831472 From state POUTREV
09:47:04 NORMALMOWING / POUTREV Dir 1 State changed at 69829394 From state POUTSTOP
09:47:03 NORMALMOWING / POUTSTOP Dir 1 State changed at 69828562 From state FRWODO
09:47:03 Perimeter trigger at : 69828562
09:47:02 NORMALMOWING / FRWODO Dir 1 State changed at 69827616 From state POUTFOR
09:47:01 NORMALMOWING / POUTFOR Dir 1 State changed at 69826020 From state POUTROLL
09:46:59 NORMALMOWING / POUTROLL Dir 1 State changed at 69824794 From state POUTREV
09:46:57 NORMALMOWING / POUTREV Dir 1 State changed at 69822886 From state POUTSTOP
09:46:56 NORMALMOWING / POUTSTOP Dir 1 State changed at 69821811 From state FRWODO
09:46:56 Perimeter trigger at : 69821811
09:46:54 NORMALMOWING / FRWODO Dir 1 State changed at 69819937 From state POUTFOR
09:46:53 NORMALMOWING / POUTFOR Dir 1 State changed at 69818369 From state POUTROLL
09:46:51 NORMALMOWING / POUTROLL Dir 1 State changed at 69816868 From state POUTREV
09:46:49 NORMALMOWING / POUTREV Dir 1 State changed at 69814899 From state POUTSTOP
09:46:49 NORMALMOWING / POUTSTOP Dir 1 State changed at 69814062 From state FRWODO
09:46:49 Perimeter trigger at : 69814062
09:46:43 NORMALMOWING / FRWODO Dir 1 State changed at 69808105 From state POUTFOR
09:46:41 NORMALMOWING / POUTFOR Dir 1 State changed at 69806507 From state POUTROLL
09:46:40 NORMALMOWING / POUTROLL Dir 1 State changed at 69805310 From state POUTREV
09:46:38 NORMALMOWING / POUTREV Dir 1 State changed at 69803206 From state POUTSTOP
09:46:37 checktimer
09:46:37 NORMALMOWING / POUTSTOP Dir 1 State changed at 69802345 From state FRWODO
09:46:37 Perimeter trigger at : 69802345
09:46:34 NORMALMOWING / FRWODO Dir 1 State changed at 69799236 From state POUTFOR
09:46:32 NORMALMOWING / POUTFOR Dir 1 State changed at 69797694 From state POUTROLL
09:46:30 NORMALMOWING / POUTROLL Dir 1 State changed at 69795850 From state POUTREV
09:46:28 NORMALMOWING / POUTREV Dir 1 State changed at 69793971 From state POUTSTOP
09:46:28 NORMALMOWING / POUTSTOP Dir 1 State changed at 69793087 From state FRWODO
09:46:28 Perimeter trigger at : 69793086
09:46:20 NORMALMOWING / FRWODO Dir 1 State changed at 69785824 From state POUTFOR
09:46:19 NORMALMOWING / POUTFOR Dir 1 State changed at 69784240 From state POUTROLL
09:46:17 NORMALMOWING / POUTROLL Dir 1 State changed at 69782286 From state POUTREV
09:46:15 NORMALMOWING / POUTREV Dir 1 State changed at 69780307 From state POUTSTOP
09:46:14 NORMALMOWING / POUTSTOP Dir 1 State changed at 69779475 From state FRWODO
09:46:14 Perimeter trigger at : 69779475
 
Ok
Strange that you never see this behaviour in the past ?
Certainly noise increase if the grass is high !!
To find a correct value you need to put the mower in the middle area ,start the mow motor to add noise and check the Smag result into Pfod setting.
If you read 300 for example Use 250 as correct value in the Big AREA Smag Center setting (A new warning message appear in the console when the mower detect bad IN/OUT transition in the middle area)
Here a PDF to help into Perimeter setting.
To find the Mini Smag ,Simply unplug your sender ,start the mow motor and read the value into Pfod setting add 50 to this value by safety.
To test, start the mower in auto mode and unplug the sender (The mower need to stop in the next 3 secondes with a correct error message)
Also try manually to force the mower Outside the wire (The mower need to stop in the next 3 secondes with a correct error message)

Perimeterhelper.pdf

Attachment: https://forum.ardumower.de/data/media/kunena/attachments/3545/Perimeterhelper.pdf/
 
Zuletzt bearbeitet von einem Moderator:
Oben