Hi Nink,

Just got back from my farm, as a retired businessman, I was surprised to see no one commented on your post

A business plan to move ahead, what a concept, lol

Hi @EzAng. Thanks, Great to hear you have retired. More time for robotics. I just retired as a CTO and IT Architect. Free at last to stay at home and annoy my wife.

At 55 and I am probably ready for a new adventure but throwing my life savings on a startup is a hard pill to swallow.

The crowd funding model is interesting and there are a lot of robotics projects on kickstarter and gofundme but the successful projects are extremely polished so you really need angel investment in order to build a decent prototype and protect IP first.

Hi Nink, I retired many years ago. I learned, retiring for my corporation, real work began for me.  :-)

Quote:

Quote - At 55 and I am probably ready for a new adventure but throwing my life savings on a startup is a hard pill to swallow.

David, I’m just now reading the older post, but I have a possible solution for you. As you know, I’m also using multiple EZ-Bs in my B9. I plan to have my primary EZ-B (what I’ll call 1st EZB) setup as in AP mode. Of course my computer will log into it. The 1st EZB since it is in AP mode is always assigned Node 0 in ARC. The 2nd EZB will then log into the 1st EZB and be assigned Node 1. The 3rd EZB is going to have a delay relay on its power line with about a 1 second delay. So when the robot’s power is turned on, the 3rd EZB will always log in after the 2nd, thus always getting assigned Node 2. Here’s the delay relay I’m planning on using: https://www.amazon.com/gp/product/B0C6XQXZZ1/ref=ewc_pr_img_1?smid=A6DS8EPUNWIZT&psc=1 I should have this all setup this weekend and I’ll let you know how it turns out.

@jsale, that's an interesting idea. I'm excited to see how it works out.

From what I can understand you are letting the second EZB power up at the same time and connect through client mode to the first (that is in AP mode). Then the third will physically power on after a delay (in client mode) and connect to the first AP mode EZB after the second one is connected hoping the IP address will stay the same at each power up?

This should work if the first AP mode EZB always assigns the EZB that powers up (in client mode) at the same time the same IP number each time.

Have fun!

So this worked, sort of. The AP client EZB always gets IP address 192.168.1.1:23 since it is the router and does the assigning of addresses. The leg EZB, which is the one I have the delay relay on (set for delay of 10 seconds) always gets 192.168.1.4:23since it is always the last device to log into the AP. The issue is now which device gets logged in 2nd the brain EZB or the computer. So I’m going to have to add a delay relay to the brain EZB and put a delay (guessing 5 seconds should work) so the computer always logs in first, and get 192.168.1.2:x, then the brains would get 192.168.1.3:23 and finally the legs, getting 192.168.1.4:23.

Sweet!

What if you go into the router and assign a static IP address to each? That the Computer and the "brain" EZB would always get the same IP?

This would work if you always use the same router. However If you ever travel or get a new router then you would have to reassign the static IP's.

What if you put a little affordable $20 router in it? Probably cheaper than the power delay hardware? I know you’re USA but I bet routers are even cheaper than canada

like this: TP-Link N300 WiFi Router (TL-WR841N) - 2 x 5dBi High Power Antennas, Supports Access Point, WISP, Up to 300Mbps https://a.co/d/gTxlyFG

then you could use dhcp reservation for each ezbs