• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 4 Documentation Website Mango 5 Documentation Website Radix IoT LinkedIn

    RelinquishDefault access

    Scheduled Pinned Locked Moved BACnet4J general discussion
    4 Posts 2 Posters 3.1k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      joolz
      last edited by

      On line 213-216 in BACnetObject.java

              if (pid.intValue() == PropertyIdentifier.priorityArray.intValue())
                  throw new BACnetServiceException(ErrorClass.property, ErrorCode.writeAccessDenied);
              if (pid.intValue() == PropertyIdentifier.relinquishDefault.intValue())
                  throw new BACnetServiceException(ErrorClass.property, ErrorCode.writeAccessDenied);
      ```The BACnet standard states that if the PresentValue is commandable, then the PriorityArray and RelinquishDefault shall be present.
      Clause 19 indicates that the PriorityArray is indeed read only, but I didn't see any mention about RelinquishDefault being read only.
      Is there a reason for this behaviour in BACnet4J?
      1 Reply Last reply Reply Quote 0
      • M Offline
        mlohbihler
        last edited by

        First, thanks for doing some research prior to posting.

        From the text:

        ... R or O properties may also be writable at the implementor's option unless specifically prohibited in the text describing that particular standard object's property.

        ... and:

        An O property, if present in a particular object, is not required to be writable unless specifically identified as such in the text describing that particular standard object's property.

        So, i agree. The "output" objects list the relinquish default as "R", but don't prohibit it from being writable. The "value" objects list it as "O", but similarly don't object specifically to writing. Accordingly, i've changed the code (commented out 215-216) and checked into CVS.

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • J Offline
          joolz
          last edited by

          No worries and thanks.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post