I believe that the reason is the device is not mapped to the reader. When you try to read the meter first available reader tries to read it and this causes the problem. UI doesn't support this at the moment, but we can add support it the next week and release a new version at the beginning of November.
Assigning attributes to different readers in DLMS.AMI UI is OK.
But, how to add multiple readers through the JSON file? When added as described above before, I have error: "Unhandled exception. System.FormatException: A duplicate key 'Reader:Disabled' was found."
Hi Mikko
The addtional instance of DLMS.AMI.dll reader does not work as it does not take the new port 64883; it still used 64881 and hence clashes with existing instance and therefore crashes
Am I missing something?
Ajay
Hi,
Hi,
I believe that the reason is the device is not mapped to the reader. When you try to read the meter first available reader tries to read it and this causes the problem. UI doesn't support this at the moment, but we can add support it the next week and release a new version at the beginning of November.
Is this the problem?
This should work if you have only one thread.
BR,
Mikko
Hi,
Hi,
This functionality is added to the new version. Get the latest versions from the Gurux.DLMS.AMI and GXDLMSDirector.
Assigning attributes to
Assigning attributes to different readers in DLMS.AMI UI is OK.
But, how to add multiple readers through the JSON file? When added as described above before, I have error: "Unhandled exception. System.FormatException: A duplicate key 'Reader:Disabled' was found."
Hi,
Hi,
There is only one reader per instance, but you can define how many threads there are in one reader settings Threads in appsettings.json.
Read the instructions here if you want to use multiple readers.
https://www.gurux.fi/node/17172
Get the latest version from Gurux.DLMS.AMI. Database type was earlier set to empty, but now database disabled is set True.
BR,
Mikko
Hi Mikko
Hi Mikko
The addtional instance of DLMS.AMI.dll reader does not work as it does not take the new port 64883; it still used 64881 and hence clashes with existing instance and therefore crashes
Am I missing something?
Ajay