Hi Brian, On 09/04, Gix, Brian wrote: > > Since PDO payloads are *not* self-describing (unlike mesh sensor > > messages), the receiving party must be aware of the mapping in order to > > parse the data. > > > > In CANOpen, format is determined by the address - in mesh, it could very > > well be a virtual label. > > I think that this is an interesting use of Virtual Addresses, and in > addition to this, Mesh Virtual Addresses have been suggested as a way > of addressing IPv6 addressing as well... However: > > 1. There is already a way something like this could be used already: > A model could be created that gets subscribed to the Virtual > Addresses that require handling by the node. But the whole idea is that the virtual labels and packing are configured dynamically (by the commissioner) according to their specific needs. If a model doesn't receive the *value* of the label, you would need a separate model for each of the virtuals. This is problematic, because composition data is immutable, so you wouldn't be able to reconfigure these mappings without at least re-provisioning the whole network. > In any case the ability to create simple mesh Apps with minimal > complexity remains intact, and as an added bonus, the Open Source > community (not to mention the Bluetooth Mesh Working Group and larger > SIG) can weigh in on the preferred methodologies. Aren't *we* the community? :P -- Michał Lowas-Rzechonek <michal.lowas-rzechonek@xxxxxxxxxxx> Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND
