You can benefit from reading what a Movement Panel is. Here's two links...

1. The getting started guide is a great place to learn how to make a robot. We spent a TON of time on it, so you'll enjoy using it: https://synthiam.com/Support/Get-Started/how-to-make-a-robot/Movement-Style

2. In the support section, there's a USING ARC category that you would benefit from. Good place to visit if you have questions: https://synthiam.com/Support/ARC-Overview/movement-panels

Somehow I posted on this GPS thread rather than The Better Navigator skill. I read up on the movement panels and pretty familiar since I've been already using Auto Position movement panel. Looks like the Better Navigator will need it's own Movement Panel and since only one Movement Panel is allowed per EZ I will just put other motors on a different EZ with different index-problem solved.

That is still incorrect. Please read about the movement panel. All of your servos and motors can be controlled by any robot skills. Except only the motors/servos responsible for movement use a movement panel. Hence the name, Movement Panel = responsible for movement.

you do not need to put other motors on other ezb’s.

I moved your questions here since this is where you meant for it to be - but really it's a question about what a Movement Panel is. I will repeat my previous comments here for you....

You can benefit from reading what a Movement Panel is. Here's two links...

1. The getting started guide is a great place to learn how to make a robot. We spent a TON of time on it, so you'll enjoy using it: https://synthiam.com/Support/Get-Started/how-to-make-a-robot/Movement-Style

2. In the support section, there's a USING ARC category that you would benefit from. Good place to visit if you have questions: https://synthiam.com/Support/ARC-Overview/movement-panels

I'm not sure if you still get it. You do not need to incorporate anything together. The Movement Panel manual is very detailed. Please read the manual before posting.

If you robot uses servos or to walk like a humanoid or hexapod or something, then that needs a gait. In this case, you'll use the Auto Position Movement Panel.

If your robot uses wheels to move, then you will use the Movement Panel that drives the wheel controller.  Please read the links I provided before posting. This conversation is off topic. I will create a new thread for it because it has nothing to do with The Better Navigator.

Here is your new thread. In the meantime, read about movement panels and follow the getting started guide here: https://synthiam.com/Support/Get-Started/how-to-make-a-robot/make-a-diy-robot

Sorry I made a very bad analogy. I was referring to The Better Navigator and how it is configuring for two motors with the Movement Panel taking care of it. I suppose that I've already moved on to the next phase whereas you have multiple glyphs and multiple robots moving around. Just trying to add to the skill and make it better.

The Better Navigator is not configured for two motors. The Better Navigator does not care what kind of motors or how the robot moves. Absolutely no robot skills care about how a robot moves. This is because the Movement Panel does the moving. All the robot skill has to do is say, "Go forward," and the right Movement Panel moves the robot. This is all documented in the links I provided of what a Movement Panel is. I'm repeating precisely what you could be reading on those pages.

If you have a robot with wheels and write the script command "Forward(),".... the robot moves forward. If you have a robot with wheels, chances are you're using an HBridge or Continuous rotation servo movement panel.

Now, you have a robot with servos that walks like a humanoid. and you write a script that says "Forward()"... the robot moves forward. If you have a robot that walks with servo legs, you're most likely using an auto-position movement panel.

It doesn't matter how the robot moves. No robot skills care how the robot moves. The Better Navigator does not care how the robot moves. Movement scripts do not care how the robot moves. Nothing cares how the robot moves. The Movement Panel takes care of how a robot moves. The Camera NMS does not manage how the robot moves. The speech recognition scripts do not care how the robot moves. Absolutely no robot skills care about how the robot moves. It does not matter if the robot has wheels. It does not matter if the robot flies. It does not matter if the robot is made of bananas, springs, and bounces. All the robot skills do is say, "Move forward" or "Turn Left."

Again, I recommend you read the getting started guide. And on this subject, I have provided links for the Movement Panel manuals. Here they are again. All I'm doing in this message is repeating what has been documented in the manuals.

Here are two links again...

1. The getting started guide is a great place to learn how to make a robot. We spent a TON of time on it, so you'll enjoy using it: https://synthiam.com/Support/Get-Started/how-to-make-a-robot/Movement-Style

2. In the support section, there's a USING ARC category that you would benefit from. Here is an excellent place to visit if you have questions: https://synthiam.com/Support/ARC-Overview/movement-panels

Here's a video on how to use the better navigator.

Yes, I saw that and it’s great. I think I may have been the first one to post on it just working out things this morning it’s very close, will get back on it tonight after work

Nice video DJ.  It Just turned up in my LinkedIn feed.  I was wondering that now all you need is the Lidar on board and not expensive realsense if the entire thing could be offloaded to an arduino so we don’t need an on board SBC.  Went to buy a Pi 4 for cyber Monday and it’s cheaper to buy a laptop.   If you hang the Lidar off an arduino you would reduce power consumption and cost and you don’t have to drag an SBC around.

We used to have that with our first experiments. The trouble we ran into was latency with the slam algorithm. Any latency at all warps the map and makes it unusable.

there’s a number of reasons benefits to onboard sbcs, which is why it’s the direction we have been taking. What you can do with remote wifi has been achieved and pretty much maxed out.

Also, the Intel realsense isn’t being used in that video. Just happens to be there because I use that robot for a number of tests.

A raspberry pi makes a terrible sbc. It’s capable but super slow compared to the alternatives.

I’ve been using these Belkin sbcs that are less then $200 Canadian with 128gb storage: Mini PC, Beelink Mini S Intel 11th Gen 4-Cores N5095, Mini Desktop Computer 8GB DDR4 RAM 128GB SSD, Mini Computer Dual HDMI 4K UHD/Gigabit Ethernet/Dual WiFi/BT/VESA for Home/Office https://a.co/d/bzEKRNN

Thanks for the tip on the beelink. Gone are the days of the sub $100 SBC. I ended up not buying anything. I have a NUC and 2 Rock PI X but they are all in bots so I guess I’ll repurpose one.  Ok I understand the latency issue. If your bot is not where it says it was when it took the reading things would drift.  When we can have ultra light SBC and LIDAR on our Drones will be cool.

That drifting was the death of me, haha. I kept pushing the wifi method because, at the time, I was at EZ-Robot, and it was our product. But now, with Synthiam and being hardware agnostic, I get to support whatever is best for the job. Sadly, the cost increases as you get into more advanced technologies, like SLAM. I would like to see the hardware price lower because it seems so high lately. There also haven't been many advancements in hardware to get me excited, specifically with SBCs.