i read the other thread and also DJ's answers...

to be effective it's necessary some kind of web tool where the ideas are submitted, validated, voted, commented, closed.

otherwise DJ will need vitamins to answer all the ideas and duplicates etc.

some ideas are software only or almost impossible to implement in the hardware or not commercially viable...

nevertheless everyone has a list

Im waiting for the V8

1. There will only be one type of connectivity, not both (usb and wifi). That's like asking any usb peripheral to connect to two machines at once - which would be a tremendous amount of synchronization considerations for the very few use-case scenarios.

2. The v4.x/2 has onboard memory for some basic functions like that - which is planned for a future firmware update. It will be limited to disabling pins on disconnect, etc.. I don't have an ETA on this, but it's planned for a future firmware update

3. "Auto Sense" device recognition is a performance limiting impractical approach. Also, it would be a challenge for ez-robot to afford to create a sensor for every sensor in the world. No sensor is "Detectable" because they merely transmit signals. We'd have to create our own PCB's for every sensor... and they would all have to be i2c - and the scanning process of i2c requires a timeout per device.. this means the constant scan to "Detect" devices would be slow and affect other i2c peripherals, which would be 100 ms. So, in theory a scan of 127 i2c addresses at 100ms timeout would take 12,700 ms (12.7 seconds). That means you would only get one response from your i2c device every 12.7 seconds. Use the "Add control" menu option

4. More adc ports or analog ports will be challenging and most likely not possible. If you have ever looked at an ez-b v4 to see the number of traces, because power, gnd, audio, etc... there's absolutely no room for more ports. Even if we were to make it bigger, the traces for power and gnd would need to be even larger due to raising the power consumption. If you understood the amount of power consumption maths and planning to design the current ezb, you would not be asking for more ports. Physics is your enemy at this point... We fit as much into the form factor as possible - use two ez-b's for more ports. Also bandwidth latency issues become a concern. Although, the v4.x/2 does have an approx 400% performance increase, that would compensate for the communication issues - but not the power traces.

5. We have thrown the idea around of having a wifi board that supports 2 cameras for stereo vision.... then we realized, anyone who wants it has an onboard computer. So, buy one of the hundred usb versions that already exist. There's quite a few usb stereo cameras out there - next step is for us or someone to create a control for it. RoboRealm i believe supports it, and they will have an ARC skill plugin pretty soon to make the transition easier.

6. It's impossible to add the fuse in the ez-b for certifications due to energy consumption, size and heat. There's so much physics to design what we already have designed - it cannot be improved very much, if at all. There is also very very very little money in diy hobby products, so any new products will always be clip'n'play and designed for the education/consumer product. The revolution product-line is what supports this forum and the diy builders like yourself. The best solution i recommend for that is to remove the power base by soldering power wires directly to the ez-b... like Dave has done with his b9. Of course, this is dangerous because you wouldn't want to break the ez-b

7. rgb led's - we actually have an rgb led ez-b which will be shipping with all the others soon as the v4.x/2 is online. This has nothing to do with the ez-b, but will exist as an accessory in May

8. There was no room to add an audio jack to the ez-b. The pins for soldering the audio output is your only option. New version will most likely not fit an audio jack either, due to size limitations and well, only 15 people on this forum will benefit from it, sadly.

9. Jeremie has been working hard on an audio filter for an upgraded v4.3/2. It's real hard to isolate the background static due to the very small foot print of the ez-b v4. The v4 is designed to the absolutely smallest size possible for providing the energy it does via power pins, and keeping the traces as close as possible. I think there's a huge overlook on this site regarding the impressive size of the v4 that jeremie took a whole year to engineer. It's probably a good idea to take your v4 out of the shell one day and give it a good look. Really lie down with a flash light and follow the traces and look at it... Seriously, look. It'll blow your mind. It's really really really really small for the amount of current that it is providing and the number of i/o. Every few weeks he thinks there's a breakthrough in removing some of the static - one day he'll get it!

10. "Indoor Navigation Capabilities" - this is not an ez-b related question. This is software related and/or hardware accessory.

I do have something very different planned for the v5 in 2017... But until we can find the technology which is small enough, i'm keeping it a secret. It doesn't address the "more ports" or "audio jacks" or "internal fuse" questions. However, it does address something way more uhm... how do we say... self contained.

What i do think you are all asking for are more accessories which are clip'n'play and work out of the box - without needing to read datasheets and configurations etc.. That is what we have focused for 2016, so you will see a lot of new accessories starting May.. including:

• inverted pendulum (finally, but will require the v4.x/2)
• capacative touch
• rgb led
• 8x8 rgb led array
• usb adapter
• new 4-in-1 with an additional micro to "smooth" data
• gps
• digital servos
• and some more but i'm forgetting some of them

Lastly, it's probably a real good idea to try the v4.x/2. Trust me, it's a whole new experience. And the firmware upgrade aspect means new features and a variety of "firmwares" to choose from.

There have already been a few firmware updates distributed with ARC for the pre-release users of the v4.x/2

Umm, hey! What's this about Pre-release users of the v4.x/2? How can I get into this secret clan? What an honor that would be!

Also thanks for the honorable mention! "i recommend for that is to remove the power base by soldering power wires directly to the ez-b... like Dave has done with his b9. Of course, this is dangerous" LOL, Danger is my middle name! Of course the faint of heart robot builders can always place an inline fuse holder in the soldered on power pigtail to protect the EZB and keep the low profile. This will give you back your 20 amp fuse.

I second Techno's request for the 3.5 audio jack. However I truly understand the lack of space. The sound break out mod that allows the builder to channel the sound to an external amp really provides great sound. This lets us to tie into the EZB's audio circuit before the EZB's build in amp and use an external amplified sound system.

Even without my wish list items included, I cant wait to get my hands on the next new EZB!

My power base eliminator. Includes 20 amp fuse. A drop of hot glue holds plug in if needed.

@DJ, Thanks for addressing the feature requests in such detail. (both here and the old thread I referenced). I think it is probably valuable that users keep posting their ideas so you know what we are trying to achieve (for instance, I think the USB module you are adding probably came from so many of us discussing how useful it would be), but I don't really expect you to address every one that you are NOT going to do.

I realize that indoor navigation is more software than hardware, although a couple of years ago when we were discussing this you had mentioned that you were working on a WiFi camera that would be able to be put in a room and used to track the location (or presence) of an EZ-B, so there could be a hardware component.

Have you thought about ptp's idea of having a web page feature for submission and tracking of feature requests, planned feature updates, and bug report status tracking? Advantage is that you don't get a lot of duplicate requests, and if you add voting capability you can get a feel for how important features and bugs are to your users. Disadvantage is that if it is publicly view-able, you lose some competitive advantage. When I was product manager for a large telecommunications software/hardware provider I struggled with this. I had a tool for tracking, but ultimately chose not to make it available to customers. We did put a place on our web site where customers could make requests and discuss them, and if I was absolutely not going to fulfill a request I would comment on the thread, but would only comment on things we were going to do when we publicly announced a release that incorporated the feature. On the other hand, I was able to use this forum to determine which customers I wanted to solicit for Beta testing.

Anyway, I think we have hijacked this thread enough.

Alan

The webpage submission may be a good idea for the future - we're very focused on ez-bit's this year. It takes a great deal of effort and focus to design and manufacture these components and software. I guess ez-robot makes it look ez

As for the indoor navigation with the wifi - that's actually still on the list. I've had it for a while semi-working. The only challenge has been lighting conditions - which i think we have a solution for using a filter and dual cameras. Since 2016 is the year of accessories, i'm confident that you will see the navigation camera soon

I sure don't mind mentioning why we are unable to perform some of the suggestions. It's very educational and that's my motive... to educate. I still do recommend taking a real good look at the ez-b circuitry. It will surprise you how smart the routing is vs. it's size - and consider how many amps it will deliver given it's size!