Customization of debugger log

[FabioLugatoDerga]

Hello there, I read multiple topics on these warnings, but I still can't remove those ones.

I understand they are useful but there may be a way to turn them on and off without restarting node-red, maybe only redeploying? I really need to read other stuff on the logger.

Thanks in advance, (i really appreciate your plugin)

[piwi447]

I have same problem with warning OPC SUBSCRIBE: StatusCode: Good#Overflow (0x00000080)

coming each time my OP subscribe get update of one varabale and this is filling my debug windows but also the log file.... Thanks a lot

[mikakaraila]

As long as status != StatusCodes.Good it will be logged. As nodeId unknown is error!

I could change it to !goodish(status), but then you will not see it if it is like Good#Overflow. Do you need this?

function isGoodish(statusCode: StatusCode): boolean {
  return statusCode.value < 0x40000000;
}

[FabioLugatoDerga]

I don't want to turn off all logging but it would be great if the logging could be enabled/disabled with a checkbox. Because yes the logging is essential but sometimes it clogs up the debug panel. That may be a future feature if you consider it to be useful, for me it would be!

[mikakaraila]

Put it to node-red wishlist, code is using node-red logging. It can be changed in the settings.js by logLevel.

 // Configure the logging output
    logging: {
        // Only console logging is currently supported
        console: {
            // Level of logging to be recorded. Options are:
            // fatal - only those errors which make the application unusable should be recorded
            // error - record errors which are deemed fatal for a particular request + fatal errors
            // warn - record problems which are non fatal + errors + fatal errors
            // info - record information about the general running of the application + warn + error + fatal errors
            // debug - record information which is more verbose than info + info + warn + error + fatal errors
            // trace - record very detailed logging + debug + info + warn + error + fatal errors
            // off - turn off all logging (doesn't affect metrics or audit)
            level: "debug",
            // Whether or not to include metric events in the log output
            metrics: false,
            // Whether or not to include audit events in the log output
            audit: false
        }
    },

[piwi447]

What is the exact meaning of good overflow? I could not find this status code in OPC UA status code list… is there something I can do to avoid this overflow message. Basically my OPCUA communication is working well but generate a lot of error message and warning

Pierre RUWET

Le 30 sept. 2022 à 09:21, Mika Karaila @.***> a écrit :

 As long as status != StatusCodes.Good it will be logged.

I could change it to !goodish(status), but then you will not see it if it is like Good#Overflow. Do you need this?

function isGoodish(statusCode: StatusCode): boolean { return statusCode.value < 0x40000000; } — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[mikakaraila]

It is used for the application level. Let´s say that AnalogDataItem has Range from 0 to 5 bar. Overflow bit can be used to tell that measurement is 6 (over range). No OPC UA error, instead application level information.

[FabioLugatoDerga]

Put it to node-red wishlist, code is using node-red logging. It can be changed in the settings.js by logLevel.

 // Configure the logging output
    logging: {
        // Only console logging is currently supported
        console: {
            // Level of logging to be recorded. Options are:
            // fatal - only those errors which make the application unusable should be recorded
            // error - record errors which are deemed fatal for a particular request + fatal errors
            // warn - record problems which are non fatal + errors + fatal errors
            // info - record information about the general running of the application + warn + error + fatal errors
            // debug - record information which is more verbose than info + info + warn + error + fatal errors
            // trace - record very detailed logging + debug + info + warn + error + fatal errors
            // off - turn off all logging (doesn't affect metrics or audit)
            level: "debug",
            // Whether or not to include metric events in the log output
            metrics: false,
            // Whether or not to include audit events in the log output
            audit: false
        }
    },

Ok but as you know this only affects console logging, not the node-red panel for logging. I already turned it all off. What wishlist?

[mikakaraila]

This seems to be already open on nodered forum... of course errors cannot be turned off. If nodeId is incorrect it should be fixed. You have wrong namespace index ns=1 when it should be perhaps ns=3. Or index number is wrong ns=4;i=1001 as it should be ns=4;i=1007 same with other String or Opaque nodeId formats.

[piwi447]

Hello, I have this case with some structure I am reading. This structure is a combination of 4 float values, 1 integer and one string. This is seen by browser as extension object. The subscribe is working and I am able to decode field names and the values but it generate error message complaining about opaque structure. How can I configure the subscribe to avoid this kind of error message. I saw an example with the build mode of OPC client but did not catch how to use it with a subscribe fonction Thanks for any help

Pierre RUWET

Le 4 oct. 2022 à 15:13, Mika Karaila @.***> a écrit :

 This seems to be already open on nodered forum... of course errors cannot be turned off. If nodeId is incorrect it should be fixed. You have wrong namespace index ns=1 when it should be perhaps ns=3. Or index number is wrong ns=4;i=1001 as it should be ns=4;i=1007 same with other String or Opaque nodeId formats.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[mikakaraila]

Most probably it´s still inside node-opcua. There are still open issues there and root cause is somehow related to these dynamic extension objects. You can check them from the node-opcua issue list.

[piwi447]

Thanks for the feedback… I saw some discussion about dynamic extension object but I thought I was not in that case because my structure definition is static.So my extension object structure is also static. I don’t understand the subscribe claiming about opaque structure when the structure can be decoded easily.

Pierre RUWET

Le 5 oct. 2022 à 07:17, Mika Karaila @.***> a écrit :

 Most probably it´s still inside node-opcua. There are still open issues there and root cause is somehow related to these dynamic extension objects. You can check them from the node-opcua issue list.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[piwi447]

I did not find any way to configure a range for my analog values on the server side. If the OPC client claim for overflow, it probably compare the received value to limits. These limits are thus probably defined on client side. My next question is then, where? And what do I need to add in the subscribe configuration to inform OPC client of the right range for each value? Thanks for your support

Pierre RUWET

Le 3 oct. 2022 à 09:19, Pierre Ruwet @.***> a écrit :

Thanks a lot , then I need to investigate how to configure that range on the OPC UAserver side that is a codesys soft plc running on raspberry target.

Pierre RUWET

Le 3 oct. 2022 à 06:47, Mika Karaila @.***> a écrit :

 It is used for the application level. Let´s say that AnalogDataItem has Range from 0 to 5 bar. Overflow bit can be used to tell that measurement is 6 (over range). No OPC UA error, instead application level information.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[mikakaraila]

I expect overflow is generated on server side.

For the extension object structure, can you add screenshot of the structure/variables?

It could help me / Etienne to solve problem... it can be solved with the latest node-opcua as Etienne added some v1.03 nodeset emulation into the node-opcua.

[piwi447]

Hello,

Regarding the Overflow, i tried to anlyse with OPC Expert

The Quality given is always good but wit code 192 which is different from àx00000080 generated by the opc client node.

Le 05-10-22 à 11:30, Mika Karaila a écrit :

I expect overflow is generated on server side.

For the extension object structure, can you add screenshot of the structure/variables?

It could help me / Etienne to solve problem... it can be solved with the latest node-opcua as Etienne added some v1.03 nodeset emulation into the node-opcua.

— Reply to this email directly, view it on GitHub https://github.com/mikakaraila/node-red-contrib-opcua/issues/484#issuecomment-1268185918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARWE4XTN3ZLFNITL3WXE72LWBVDDDANCNFSM6AAAAAAQYXAUZA. You are receiving this because you commented.Message ID: @.***>

-- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

[piwi447]

Hello, I worked teseterday again on more investigation about the overflow status. i saw by logging the status code in the debug windoww that the overflow signal is not linked to a specifict item. when the subscribe produce a value a message with a value in the payload and a topic related to one sunscribed item , the status code is always Good 0x00000000. when the subscribe produce a status code overflow, there is no topic in the message

On 6/10/22 23:12, Pierre Ruwet @.***> wrote:

Hello,

Regarding the Overflow, i tried to anlyse with OPC Expert

The Quality given is always good but wit code 192 which is different from àx00000080 generated by the opc client node.

Le 05-10-22 à 11:30, Mika Karaila a écrit :

I expect overflow is generated on server side.

For the extension object structure, can you add screenshot of the structure/variables?

It could help me / Etienne to solve problem... it can be solved with the latest node-opcua as Etienne added some v1.03 nodeset emulation into the node-opcua.

— Reply to this email directly, view it on GitHub https://github.com/mikakaraila/node-red-contrib-opcua/issues/484#issuecomment-1268185918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARWE4XTN3ZLFNITL3WXE72LWBVDDDANCNFSM6AAAAAAQYXAUZA. You are receiving this because you commented.Message ID: @.***>

-- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

[piwi447]

Thanks a lot , then I need to investigate how to configure that range on the OPC UAserver side that is a codesys soft plc running on raspberry target.

Pierre RUWET

Le 3 oct. 2022 à 06:47, Mika Karaila @.***> a écrit :

 It is used for the application level. Let´s say that AnalogDataItem has Range from 0 to 5 bar. Overflow bit can be used to tell that measurement is 6 (over range). No OPC UA error, instead application level information.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[mikakaraila]

If it is done with AnalogDataItem then it should contain EURange, but most probably it is hard coded with some logic:

[FabioLugatoDerga]

This seems to be already open on nodered forum... of course errors cannot be turned off. If nodeId is incorrect it should be fixed. You have wrong namespace index ns=1 when it should be perhaps ns=3. Or index number is wrong ns=4;i=1001 as it should be ns=4;i=1007 same with other String or Opaque nodeId formats.

Is there anything I can do (also on the code) to catch errors and warnings (the 'catch' node doesn't catch anything coming from the 'Client' node) or to limit the log level of opcua nodes? Sometimes I can't get rid of the errors and warnings because some paths are not available at all times (server-side), and some clients may be offline/have internal errors.

[mikakaraila]

Just a reminder that node-opcua uses own logging that I cannot effect.

You should give some examples which messages are not possible to "catch" as I have added those I think are critical.

[FabioLugatoDerga]

These are some examples:

"subscribe: StatusCode: Bad (0x80000000) The operation failed." and also "Can't work with OPC-UA session" (when it won't reconnect on its own, not a big matter now since there are not many errors like this)

I understand that my specific use case produces several warnings that I can't avoid; these issues are on my end and not a fault of your code, but I was wondering if you could provide a way to catch/suppress these warnings so they don't appear in the debug sidebar. The OPCUA server on the machines sometimes returns an error even when everything is ok.