Looking at subscription methods - I am not sure if there is one standard which can support all three kinds at the same time. Some kind of distinguish is necessary, but for an end user (counting myself) - multiple types of subscription happening at the same time are rather unlikely to happen.
Looking from canopen perspective - there is possibility to subscribe to some messages happening directly on the bus if plc4x becomes a so-called master node (that's the way its implemented currently using EVENT subscription kind). There is also possibility to subscribe over coordinator node which is specified by yet another specification which number I don't remember right now. In theory - we could also subscribe to other node messages since canbus is still a bus system so everyone sees everything. Later two cases are currently left unimplemented. Best, Łukasz On 12.11.2020 18:33, Christofer Dutz wrote: > Hi all, > > I’m currently implementing the different subscription types in KNX4Go … and > here I noticed something. > We create a SubscriptionRequestBuilder and here can add different types of > fields and even combinations. > So we could create a subscription request with some on-value-change fields, > some periodically pulled fields and some events/alarms. > > Now does it actually make sense to have this sort of combinations? I mean the > program processing the results has to be very flexible in this case. > > Wouldn’t it make sense to have 3 different types of subscription requests? > > Chris >
