The Cirrus Link default TLP Definitions and EFM Mapping files can be used as a starting point for configuring the EFM Emerson ROC module.

Once you have customized your configurations, you will likely encounter some issues and the following logged errors should give you clues on where to focus to resolve these issues.


For debugging, break out your poll groups into smaller groups that poll at different rates as a strategy to help isolate issues.

Internally the driver ‘optimizes’ polls to maximize data efficiency. For example, if you have 10 TLPs that are all polled every minute - all of those will be included in a single poll for efficiency. However if one of them fails, they all fail because the response from the ROC turns into an error response. If you modified the 10 TLPs to be in 5 groups of 2 all polled at different rates, only two of the TLPs would fail assuming only one TLP was actually problematic.

If you have two different poll groups that use the same poll rate, those will still be optimized. So, for this strategy to work you must use different poll rates between the groups. Also, this is a suggestion for isolating the config issues and, once everything is cleaned up, you can set up your poll groups as you see fit.


Logger: com.cirruslink.emersonroc.EmersonRocDriver

Error examples:

['M-205' 10.0.40.169:4000] No Orifice meter configuration found at logical number 2
['M-205' 10.0.40.169:4000] No Orifice meter configuration found at logical number 3


Logger: com.cirruslink.emersonroc.protocol.model.opcode.OpCodeDataContainer

Error examples:

Failed to parse TLPs for pointType=7 and parameterNumber=178. Enable 'TRACE' for details.
Failed to parse out TLP Array. Enable 'DEBUG' for details.


Logger: com.cirruslink.emersonroc.protocol.model.point.DynamicPointTypeParameter

Error examples:

Invalid length: 4 for DataType: UINT16 - changing to default length: 2
Invalid length: 1 for DataType: FL - changing to default length: 4
Invalid length: 5 for DataType: UINT32 - changing to default length: 4


Logger: com.cirruslink.common.util.exception.CirrusException

Error examples

Error handling TLPs in the template. Check the TLP definitions for this device and verify the following TLPs are defined. [196,l,25]

Error handling TLPs in the template. Check the TLP definitions for this device and verify the following TLPs are defined. [196,l,26], [196,l,30], [196,l,31], [196,l,32], [196,l,33], [196,l,34], [196,l,39], [196,l,40], [196,l,41], [196,l,42], [196,l,43], [196,l,44], [196,l,45], [196,l,46], [196,l,47], [196,l,48], [196,l,49], [196,l,50], [196,l,51], [196,l,52], [196,l,53], [196,l,54], [196,l,59], [196,l,60], [196,l,68], [196,l,72], [196,l,73], [196,l,75], [196,l,76], [196,l,78], [196,l,79], [196,l,80], [196,l,86], [196,l,87], [196,l,90], [196,l,91], [196,l,94], [196,l,95], [196,l,96], [196,l,97], [196,l,140], [196,l,141], [196,l,142], [196,l,143], [196,l,144], [196,l,145], [196,l,146], [196,l,147], [196,l,148], [196,l,149], [196,l,150], [196,l,151], [196,l,160], [196,l,161], [196,l,162], [196,l,186], [196,l,186], [196,l,187], [196,l,188], [196,l,191], [230,l,40]


To change logging levels, go to the Gateway's Status > Diagnostics > Logs page and click on the  Settings  icon.

On the Log Configuration popup that will open, search for the logger name in the Filter box, and select the desired logging level from the dropdown to the right of the logger name

  • No labels

New to MQTT? Start Here!