No sequence definition found for vendorId=8

[mlohbihler]

Hi Eric,

Ok, i got the captures. Regarding "Network messages are not supported", i believe this to be a valid exception. A "network message", i.e. a message that is being routed between BACnet networks is being received by BACnet4J. Since BACnet4J is only for application layer use, it should not be receiving these messages. I can provide a means to ignore such messages and silence the exceptions.

For the proprietary message, i'll need you to look up the their sequence definition for their proprietary service with id "1". Given this, i can create a class to parse the data.

[Eric Paradis]

I don't know how and where to look to get the informations for the proprietary message. Do I ask
Delta Controls directly?

Eric

[mlohbihler]

Yes, they will certainly know.

[bobshort]

Has this been resolved? I have the latest bacnet4j distribution (1.1) and a Delta board and get the same error.

[mlohbihler]

You need to get the vendor-specific message format from the vendor. Once you have it you can write the code to handle it in your impl. You might also post it here to be added to the distro.

[bobshort]

I don't need these messages for anything, and I don't really have a Delta rep I can ask for the encodings (I'm doing some contract work for another company that uses Delta boards).

Is there any way to configure the library to simply ignore these messages rather than erroring and filling up my log files?

Regards,

[bobshort]

Just to clarify... I'm not soliciting these messages. They are some sort of broadcast that I'm getting once I create a LocalDevice on the same network as the Delta board.

[mlohbihler]

Understood. Eric had the same problem. I've uploaded a new version of the product to SF, version 1.2. It has some enhancements regarding vendor-specific services. In particular, you will no longer see a stack trace when you receive these messages, but rather just a one liner that provides the vendor id, service number, and the byte queue of the remaining message (with context ids).

If you want to suppress the message (i.e. you have no intention of implementing the sequence definition for the service), the simplest way is to just override the DefaultExceptionListener class and provide a new implementation of the unimplementedVendorService method.

class MyExceptionListener extends DefaultExceptionListener {
    @Override
    public void unimplementedVendorService(UnsignedInteger vendorId, UnsignedInteger serviceNumber, ByteQueue queue) {
        // do nothing.
    }
}

This allows you to be picky if you want to be, and still log messages that you don't expect. In your case of the Delta message you might do this:

class MyExceptionListener extends DefaultExceptionListener {
    @Override
    public void unimplementedVendorService(UnsignedInteger vendorId, UnsignedInteger serviceNumber, ByteQueue queue) {
        if (vendorId.intValue() == 8 && serviceNumber.intValue() == 1) {
            // do nothing
        }
        else
            super.unimplementedVendorService(vendorId, serviceNumber, queue);
    }
}

And finally, you need to register your listener with LocalDevice to get it to work:

LocalDevice.setExceptionListener(new MyExceptionListener());

NOTE: the 1.2 version is now licensed under GPL (replacing LGPL). If you want to use this product commercially, you should contact Serotonin to obtain an alternative license that permits commercial use.

[bobshort]

Works like a charm. Thanks!