Since last update, if Yarbo steps out by accident while turning slipped out from the path any reason, it is stopping saying that is it out of the selected area, but when you correct, the plan is already stopped and cancelled, even if you are at 80% you will have to start from scratch on top you will have to drive to another area, if pathway or sidewalk since even if it is in the path aligned it says to move it to one, so until you touch another it won’t let you start a plan.
That the ongoing plan gets cancelled, it is super annoying.
1 Like
Have you filed a ticket and taken screenshots and video to help show the issue?
Hi there, thanks for sharing this detailed feedback. Could you please submit a support ticket for this issue? It may require further investigation from our support team. If possible, we’d really appreciate it if you could include the approximate timestamp of when the issue occurred, as that will help us look into it more effectively.
1 Like
Ticket submitted thank you.
1 Like
Hi @Yarbo-Forum I submitted a ticket but it got deleted closed not sure why.
After many other instances I finally saw exactly when this happens which is when it goes into a no go zone, caput, it deletes the plan, you will need to start again from 0 on top you need to move the yarbo to another area, sidewalk or path, or it won’t start a new one, it happened because it slipped and touched one no go zone, it defeats the purpose of these I ended up deleting them as it kept happening. Pls escalate.
@omardumont Hi there, I’ve checked your support ticket #147845 in our system, and it has not been closed or deleted. The ticket is currently on hold while we’re waiting for a conclusion from our R&D team.
Sorry for the delayed response. I’ve already asked the field service engineer handling your case to follow up and share the latest update with you as soon as possible. Thank you for your patience and understanding.
1 Like
For whomever is interested attached the answer I received, basi
cally, sidewalks do not recognize no go zone, which is very bad, I have cars and drops of 2m.
This needs to be added. G
They will recognize them if you place the at the entrance as an example. However you can route a sidewalk through one. This is by design for tight areas. But if you block the start or end of a sidewalk with one (or pathway) it won’t be able to enter. I think this is what you were seeing, the core was putting the nose out into the NGZ causing the out of bounds. Might have been from track slippage or just from maneuvering.
I agree, it kinda recognize them but at least in my case (new, before it didn’t happen) it will cause an error and delete the plan, also the second proposed as to manually adjust the progress, how is that done? I tried today, I cannot drag the bar as mentioned, anyone has tried don’t this before?
When you hit start on the work plan it should bring up the map view and ask for preview or start. You should be able to slide it there. Is that not working for you?
Thanks @bryan.wheeler I’ll give a try.
In regards to no go zone my goal is not to block a path but a safety precaution such as the same labeling applies to areas, NGZ car, tree bush, my sidewalks go near those and when gps fails or slips as a safe guard, so I’ll keep those, better to have a deleted plan than a 2m drop or car with dents as others users have expressed in the past
The reply from Yarbo:
1 Like