![]() Like anyone communicating in a second language, nuances may be lost as complex information is difficult to express. What’s more, in this specific instances, the vehicles can be thought of communicating in a second language, rather than in their mother tongues. While vehicles from different brands can and do communicate with one another, they require a great deal of coding to set up, and this work must be replicated for each new vehicle that is added to the installation. However, the installations that BlueBotics’ team has seen fall short of the final promise of VDA 5050. Some end-user projects comply with VDA 5050 as it stands today: with vehicle-specific software (and a lot of work ), AGVs can communicate with one another. However, its final publication date has not been confirmed.Īs the standard is not final, vehicles today cannot be fully VDA 5050 compliant. It will evolve over the coming two to five years. VDA 5050 is proposed today as a base standard for discussion and testing. We will discuss this further later in this post. At the time of writing (December 2022), it is questionable as to whether the standard achieves this goal. VDA 5050 intends to provide a more generic version of this functionality, which would enable every compliant AGV to work together. They are increasingly demanding that a fleet management solution should be capable of running a large and, more importantly, diverse fleet of AGVs – whatever the vehicle type or brand.īlueBotics’ ANT server software already enables the management of a diverse fleet of ANT driven vehicles, no matter what the vehicle type (tractor, forklift, underride, etc.) or brand – provided these AGVs are built upon our ANT lite + navigation solution. Lost space – separate AGV brands might need to use completely separate pathsĬustomers, however, want more. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |