04/06/2016 at 1:59 pm #46824
i have an issue with connecting arduino Uno with OPC Client of Ignition SCADA
As per the following code errors
OpcInvalidContinuationPoint 0xC0040403 The continuation point is not valid.06/06/2016 at 7:53 am #47475
I never heard this error….are you using the standar OPC COM protocol? not UA…and have the OPC Redistributable installed?….Happend too with other OPC clients as KASSL OPC Explorer for example?
All the best
ilde06/06/2016 at 8:03 am #47476
I never heard this error….are you using the standar OPC COM protocol? YES I am using OPC DCOM standard
not UA..(according to the installation page OPC UA is not included , is there any way to configure it As OPC UA)
.and have the OPC Redistributable installed?(What is OPC redistributable)
…Happend too with other OPC clients as KASSL OPC Explorer for example? (NO I used KASSL working perfectly but I need to use ignition to interface it with Ignition SCADA Visualization the issue is Ignition Can detect the server of Arduino but i can’t browse the tags this is the issue)
All the best
ilde07/06/2016 at 3:35 am #4747707/06/2016 at 3:40 am #4747807/06/2016 at 3:58 am #47479
do you have configuration guide for ignition SCADA like WinCC and Wounderware intouch guidelines07/06/2016 at 8:08 am #47480
Maybe you cant check this url….I hope you find how to fix the issue
Please, let us know about your progress
all the best
ilde07/06/2016 at 7:51 pm #47481
i try dOPC and Matrikon both are Ok, but with ignition as a server i can added as per attached screen, there is no issue, the issue is when i browse the tags as per above attachments, i hope if you can try it maybe it can be done with you as per link you can download it and try it12/06/2017 at 9:34 pm #47553
Hi, try to use KepServerEX as a wrapper and then connect it to Ignition via OPC-UA, it worked for me.
I have experienced before similar issues trying to establish a OPC HDA connection to Ignition and the support services told me that:
The main issue we were having seemed to come from the fact that our application runs as a service, and the opc server expects to run as an interactive program. Normally when this is the case, we set the dcom settings on the server to specify that it should only run as the ‘interactive user’, which normally prevents multiple instances from running. In this case, however, the server continued launch a second instance. Unfortunately, since we’re using a java COM wrapper, it’s not easy, or sometimes impossible, for us to set more advanced COM security flags on startup. Therefore, some solution based on COM server settings would be the best. The problem may also be an environment issue on this particular windows installation, as we’ve never seen this issue before.
I do not know what does meant but the fact is that we never got the OPC server directly connected to Ignition
Hope it helps to you
You must be logged in to reply to this topic.