Connectors/opcua/high load #1501
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactored OPC-UA connector
smatvienko-tb
approved these changes
Aug 14, 2024
|
The following error is through It's related to this kind of messages it worked in the current master branch BuildInfo(ProductUri='http://xxxxxxxx.com/xxxxxxx/v3.1.6.0', ManufacturerName='xxxxxx', ProductName='xxxxxxx', SoftwareVersion='3.1.6.0', BuildNumber='3.1.6', BuildDate=datetime.datetime(2024, 7, 8, 9, 1, 2, 607366, tzinfo=datetime.timezone.utc)) Here is the config |
|
We found another types: 2024-08-14 15:04:55 - |ERROR| - [tb_gateway_service.py] - tb_gateway_service - __send_to_storage - 1103 - Object of type datetime is not JSON serializable Range corresponds with this sample value: [Range(Low=0.0, High=0.0)] |
|
Started the GW with both connectors disabled. This was the output Enabled both connectors and here is the output: We also detected in TB that configuration was lost in the first connector "MB107_UDC1" but not in the second one
|
build docker script added. requirement for asyncua added
|
Steps followed and their outputs
Full log Much less errors at least :) |
…essing of non primitive types
docker python12 and cleanup
|
Steps followed and their outputs:
Full log |
|
Starting the gateway Full log |
|
Steps followed:
|
|
I got many errors but basically these 3: |
|
@ashdam do you have logs like: "Unsupported data type: ..., will be processed as a string."? |
|
@samson0v no, just those errors over and over on the log |
|
@ashdam added additional log because we can't understand what object type we got in the converter. |
|
@samson0v got this error stack from this commit ed0fe1e |
|
They seem all asyncua OPCUA DataTypes isn't it? |
|
@ashdam I reproduced situtation with config cutting. |
|
Regarding the suddenly missing config topic. I have this on TB server On the other hand telemetry rate on the GW seems good. Thank you! But now the bottleneck is outside GW. We are figuring out what can be ;) |
…, optimized polling and scanning methods calling
…tion parameter, hardcoded for now to be 1MB
…ling (removed disconnection if connector is not stopped), minor fixes in logger
This was
linked to
issues
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains optimization for data reading from the OPC-UA server.
read_valuesmethodawait sleep(.05)