24.11.2020, 09:21
Hello
I understand that single resident script is better practice. And semaphore is not necessary in this case. But there are some other events (not only timer to start resident script) that can to cause access to RS485 bus. These events can be object change by modbus profile mapping engine or object change from visualization. So I see potential parallel access to RS485.
Now resident script is a test for semaphore usage. And I see that it logs output message continuously with proper timeout when semaphore is not used (commented) and only several logs when semaphore is used.
I think some script debug tips (set breakpoint, steps running) can to help me to describe the problem in more details. But I do not know does debug is available at all for scripts. Can you to suggest me something to implement and report you more information?
Thanks for tip with string.char method usage.
I understand that single resident script is better practice. And semaphore is not necessary in this case. But there are some other events (not only timer to start resident script) that can to cause access to RS485 bus. These events can be object change by modbus profile mapping engine or object change from visualization. So I see potential parallel access to RS485.
Now resident script is a test for semaphore usage. And I see that it logs output message continuously with proper timeout when semaphore is not used (commented) and only several logs when semaphore is used.
I think some script debug tips (set breakpoint, steps running) can to help me to describe the problem in more details. But I do not know does debug is available at all for scripts. Can you to suggest me something to implement and report you more information?
Thanks for tip with string.char method usage.