Before commenting read Forum rules
Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
Forums
The Reader is waiting more exactly about 180 Seconds (3 x 60) for the existing task to finish before starting new task.
So, the wait time and resend count settings of the device template is not used !
Also, number of threads seems not effective, I have about 176 devices on different 32 media interfaces. So I expect if I set threads to 10 for example to have reading time 10% of the reading time if threads is set to only 1, but actually I don't have such performance enhancement.
Hi,
Hi,
You are right on wait time. Reader will always wait one minute and don't use wait time from the drive settings. I have created an issue from this and this is now on testing. A new version is released today.
What communication channel you are using? If you are using the same communication channel (ex. RS-232) only one meter is read at the time. If you are using an example TCP/IP, all the meters are read concurrently.
BR,
Mikko
Hi,
Hi,
The new version is released where this is fixed. Thank you for this info.
BR,
Mikko
I am using Serial to TCP/IP
I am using Serial to TCP/IP converters, each physical serial port is connected to multiple meters and mapped to TCP/IP (Serial over Ethernet).
But I have found something, the AMI "Reader" settings in the database table "GXReaderInfo" for column "Threads" is showing value of Zero whatever the settings in appsettings.json file.
Hi,
Hi,
You are using different appsettings.json. If you are running this on the debugger check appsettings.Development.json values. appsettings.Development.json file is updated to include all default values so it's easier to modify.
BR,
Mikko