05.04.2019, 05:32
(This post was last modified: 05.04.2019, 05:46 by Erwin van der Zwart.)
Hi,
I guess you restarted the controller as you mentioned ‘read during startup’
I don’t think that enabling that parameter had anything to do with your issue...
Restarting is causing the priority array to be cleared and i think your issue is that you wrote a value in the array at a higher level then the default 16.
If you write any value at a higer prio in the array then this value is overruling the values comming from the GA.
What is the default prio in your 3th party software? I see some manufacturers using 10 as default.
Try to change a value from the client side, and check if it sets the value in the prio array at a higher level then 16.
BR,
Erwin
I guess you restarted the controller as you mentioned ‘read during startup’
I don’t think that enabling that parameter had anything to do with your issue...
Restarting is causing the priority array to be cleared and i think your issue is that you wrote a value in the array at a higher level then the default 16.
If you write any value at a higer prio in the array then this value is overruling the values comming from the GA.
What is the default prio in your 3th party software? I see some manufacturers using 10 as default.
Try to change a value from the client side, and check if it sets the value in the prio array at a higher level then 16.
BR,
Erwin