Re: [Bacnet-developers] Read-Property questions
Brought to you by:
skarg
From: Н. Ј. <nik...@eu...> - 2011-09-29 11:25:19
|
Hi, I haven't seen in stadard nor in bacnet stack that the object list for device actually contains device object id. Can you point me to the resource which clarifies this issue? Best regards, Nikola Jelic On Thursday, 29. September 2011. 12.07.41 Henrik Johansson Ekdahl wrote: > Hi! > > Clarification for question 2: > > The object list shall always contain the device object itself. I.e. it can > never be empty. > > Best regards > > Henrik Ekdahl > > ________________________________________ > From: lar...@wa... [lar...@wa...] > Sent: 29 September 2011 11:47 > To: bac...@li... > Subject: Re: [Bacnet-developers] Read-Property questions > > Hello Nikola, > > > 1. When we request the device with magic number 0x3fffff, we > > should automatically select any device. If I understand > > correctly, the response whould contain the real device id, > > not the one with 0x3fffff, but the response from bacnet stack > > gives back magic number. Which behaviour is correct? > > The real device id is correct (although the standard imo does > word it differently). > > > 2. In theory, if we have an empty object list on device (or > > empty address binding list), how do we encode it? Should we > > put NULL value as response, or just close tags? > > Just opening and close tags without content. NULL is a value and > not no value. Also note, that there are optional lists in some > services, like CreateObject - there you encounter a "missing list" > and an "empty list" and both have their unique encoding. > > Best regards, > Lars Friedrich > > -- > > > ___________________________________________________________________________ > ____________ Diese E-Mail einschlie?lich ihrer Anhange ist vertraulich und > daher allein fur den Gebrauch durch den vorgesehenen Empfanger bestimmt. > Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail sowie > jedwedes Vertrauen auf deren Inhalt untersagt. Wir bitten, eine > fehlgeleitete E-Mail unverzuglich vollstandig zu loschen und uns eine > Nachricht zukommen zu lassen. > > This email may contain material that is confidential and/or privileged for > the sole use of the intended recipient. Any review, reliance or > distribution by others or forwarding without express permission is > strictly prohibited. If you are not the intended recipient, please contact > the sender and delete all copies. > > WAGO Kontakttechnik GmbH (nach Schweizer Recht) & Co. KG; Rechtsform: > Kommanditgesellschaft; Sitz: Minden; Registergericht: Bad Oeynhausen, HRA > 6218; Personlich haftender Gesellschafter: WAGO Kontakttechnik > Beteiligungs GmbH; Sitz: Domdidier (Schweiz); Handelsregisteramt > CH-217-3533291-9; Geschaftsfuhrung: Dipl.-Wirtsch. Ing. (FH) Sven Michael > Hohorst; Dipl. Betriebsw. Axel Christian Borner; Dipl.-Ing. (FH) Ulrich > Bohling. > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > BACnet-developers mailing list > BAC...@li... > https://lists.sourceforge.net/lists/listinfo/bacnet-developers > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > BACnet-developers mailing list > BAC...@li... > https://lists.sourceforge.net/lists/listinfo/bacnet-developers |