Will anyone be able to purchase the sensors, or will only ai teams be able to?
The sensors will we available to anyone. Usage in RECF competitions will be specified in the official rules.
This is all super amazing news. Individually purchasable especially sounds amazing so teams can try out some of the VAIC stuff to figure out if its something they have interest in.
Can you elaborate on the hardware that the AI Stereo Camera Sensor contains? What is the functionality of the USB ports? Is it possible to log into the sensor and make modifications as it is with the jetson currently?
Additionally, I appreciate the work that vex is putting into training the ML model for recognizing game objects. Are there any plans to release this model separately, or failing that, the dataset used to train the model? Both of these would be invaluable for teams planning to build their own object detection system.
Thank you for the updates Bob. Looking forward to the new GPS Field Code strip & Stereo Camera.
The AI Stereo Camera has a USB Host and Device port. Device is for connection to a computer. Host is for connection to the GPS for low latency location (as opposed to going from GPS to Brain to AI).
The hardware in the AI camera is the NXP i.MX 8M Plus.
Once the hardware is complete, we will look into ways to open up training. It is a little too early to discuss those plans, but we understand the need and want to make it possible.
Bob I just want to say that I really appreciate you making this post on the forum and answering our questions; the transparency about the future of VAIC is much appreciated.
This is great to hear! Releasing these tools will go a long way towards improving the educational ability of the program for advanced students.
This is really cool, and I look forward to seeing how this system will work.
This is interesting to hear. I take it that it would also be possible for a device other than the AI camera to read this data off the GPS (no encryption)? The increased modularity of the system (with the GPS and AI camera being separate modules) is very attractive, and it would be great if it were possible to read the GPS data directly from custom electronics
I have a few more questions:
Many advanced teams (the target audience for VAIC) are accustomed to using other environments for programming the V5 Brain, such as PROS. As far as I know, support for features useful in VAIC such as VexLink is not yet available to the developers of PROS. Are there any plans to make such functionality, as well as support for these new VAIC sensors, available in the 3rd party SDK in time for next season?
Will there be any form of DRM intended to prevent users that are not part of a registered VAIC team from using any of the hardware which you have mentioned?
Are you able to shed any light on what the registration fee for VAIC might look like this coming season? Specifically, will it be mandatory to purchase this hardware at the time of registration or will teams have more freedom to select their own hardware? I understand that this may still be under review
As you mentioned having VEXos broadcast the robot’s location to all other robots, will it be mandatory for every VAIC robot to make use of the GPS system so that their location can be known by all other robots?
Again Bob thank you for spending time to give us some increased transparency on the future of VAIC, it is much appreciated.
That’s something we will have to look at. The current implementation relied on running the scheduler used in VEXcode IIRC, so it’s not quite as simple as just opening up the API to the PROS team, it needs another phase of development and all the associated testing that comes with that.
No there will not be any DRM. Anyone can use the hardware outside of competitions.
RECF will have to answer this.
Yes. Use of GPS so this information is provided will be required.
I am extremely intersted in how the GDC plans on enforcing this. Do you have minimum ranges of field of view of the GPS that need to be unobstructed? Does it have to be mounted to the main chassis, or can it be on some appendage? How does that even apply in non-traditional robot types? It’s a very interesting problem.
I don’t want to give the wrong idea though; I am really interested and looking forward to what VAIC offers in the future.
Presumably it would be feasible to check at robot inspection that the GPS system is present and can see a sufficiently large portion of the barcode strip using some standard test (e.g., place the robot at the center of the field and rotate it through 360 degrees).
Perhaps they could also require that teams provide information about the robot’s maximum dimensions and the location of the GPS sensor within those dimensions, which also gets broadcast to all robots (and the accuracy of that data could also be verified at inspection), that way if someone builds a wallbot or something there’s some ability to tell where the whole robot is on the field vs. just the GPS sensor.
This sounds reasonable, as long as it’s objective and teams are actually able to do it on their own. However, it doesn’t quite take into account the fact that robots change throughout a match. What if I have a lift that occasionally obstructs it?
I do think that having this requirements will let us do much more interesting things with VAIC. However, I am also worried that it might unintentionally restrict engineering creativity in other ways, particularly on robot design. It’s all a question of both priorities and also how effectively this type of rule can be designed.
The tetherbot seen this year in Indiana comes to mind as a weird edge case for this. Maybe position of half the robot is reported, and the other half is “free to move about the country”. Perhaps future games will constrain robots to a maximum width/length as I seem to recall from Turning Point. Perhaps the first game will be more like “volleyball” or Star Struck where teams are constrained to half the field (I hope this is not what happens).
Hi Bob, since we are now about halfway through June, do you have an estimate as to when the new GPS kit will be available?
Hi Bob, We’re just about past halfway through Q3 and I’m wondering if you could give an update on the status of the AI Stereo Camera. Is it on track for release sometime next month? Has a price been decided upon?
Separately, are you able to shed any more light on the GPS location sharing system? Specifically, will it require any VAIC specific hardware for each field, or will it just be robot to robot wirelessly?
For the AI 3D WiFi Camera used for VAIC, delivery is still up in the air due to worldwide issues too many to list. Q3 is looking less likely and Q4 more likely.
The GPS location sharing requires no additional hardware on the robot or the field. Essentially the BLE radio in the AI 3D WiFi Camera will handle this robot-to-robot communications without any user intervention needed.
Hi Bob, We’re solidly into Q4. How’s the AI 3D WiFi Camera production looking?
Not sure what @Bob_Mimlitch_III will say, but it was announced a while back (Dan’s town hall a few weeks ago maybe?) that the season for AI would look a lot like last year as they would be available “before the end of the year”. Events will be extended for some time based on the electronics arriving and will culminate with a championship at IFI next summer. We could see the AI qualification date pushed weeks or months from the standard March 15th for VEX Worlds depending on when things are available and what the dates are for the championship event.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.