6/14/2023 0 Comments Factorysoft opc clientIt is the link between the CBus OPC server and the Citect.OPC server that fails. ![]() I have no problem changing the CBus side of the network, and the CBus OPC client updates with comms. " SendTextToPipe failed due to a closed pipe" errors towards the end! I hope this proves useful, there are a few ![]() ![]() txt file, and there was too much to post in a thread. The log file has been saved separately using the smart inspect log viewer and can be downloaded from here: Stopped and closed CBus OPC monitoring applicationġ3. I can change the state of the CBus network, but Citect does not respond, and continues to display that everything ins 'on'.ġ2. Turned each value to "0" using OPC client Note: a citect event I had running to check the conditions automatically turned all these points back to zero.ġ1. I can change the state of the CBus network from Citect, and Citect responds. waited for sync (took almost 3 minutes)ġ0. started CBus OPC monitoring applicationĦ. ![]() Opened and ran through CBus OPC Commissioning Applicationĥ. opened the CBus network via toolkit (opens c-gate)Ĥ. deleted existing log file from Clipsal install folder.\Clipsal\CbusOpcServer\LogsĢ. I have generated a detailed log, and made it as small as possible, although its still a fair whack! Just for clarity, this is what I have done:ġ.
0 Comments
Leave a Reply. |