The problem appeared to be that the call to Connect failed to recognize that we were trying to make a local connection, and it was instead attempting to make a remote connection: string computer = // get it from somewhere, perhaps getting "127.0.0.1" or "localhost" Trying to make a local OPC connection was failing with: Create Instance Failed: 0x80040112 My solution ended up being a little different, so I'll add this answer in case it helps someone in the future. We thought that Single Node meant OPC communications are restricted to be on one device, which is what we're doing. So, the question is: how do I connect to the local RSLinx Classic Single Node from a client running on the same machine using OpcNetApi/OpcNetApi.Com? I've also tried: server.Connect(url, new Opc.ConnectData(new ())) Url = new Opc.URL("opcda://localhost/RSLinx OPC Server") I've double checked all DCOM config and I'm using the standard connection code: fact = new OpcCom.Factory() Inner Exception: CoCReateInstanceEx: Class is not licensed for use. My client had no problem connecting to RSLinx Classic Gateway, when that version was used on the same machine.īut now that we've replaced Gateway with Single Node, I'm getting the following error sourced from OpcNetApi:Į_NETWORK_ERROR Could not connect to server. The time now is 05:23 AM.My C# OPC client uses OpcNetApi and OpcNetApi.Com and is installed on the same machine as RSLinx Classic Single Node. To save all the if's, but's and maybe's, will you please specify the IP address and type of device you are specifically trying to communicate with instead of calling it the "Unrecognized Device", of which there are many in your screenshot.Ĭan you see the confusion it may be causing?Īll times are GMT -4. In some cases yes, flushing the Harmony files can sort these kinds of issues, but I would be doubly sure on the above first before moving on to that. If you are happy with the EDS file, and it's still not resolved, I would next try recreating the driver, or better yet, create a new one. Again, a proper unregister and re-register of the correct EDS file should sort this. I would also ask if you have attempted to right-click the 1756-ENBT module and if so can you configure it? If you can it could even be as simple as a missing or corrupted icon file. If you haven't rebooted since starting this browse and registering the EDS file from the module, then it could be as simple as turning off for the night and it will miraculously start working the next day. However, once you register a new EDS file, you must stop and restart the RSLinx Classic Service, or else reboot, before it will take affect.
Rslinx classic sort drivers#
after Configuration of drivers I try to Connect PLC its Showing "Unrecognized Device ".Įven i tried EDS file upload from device also Success fully Completed, But showing same.
This is leading some to advise on the Red X problem, which is a Red Herring, pardon the pun.īecause the name is recognized and there is just a Yellow ?, this usually means that the correct EDS file is not registered, as mentioned. I feel our friend may be confusing the situation by referring to the problem device as being an "Unrecognized Device", and while that is somewhat true, it is the other devices, of which we are not interested in, that are all listed as "Unrecognized Device". So we know we are connected and reading the module OK. Of course, the Identity Object does not provide an icon. CIP devices include an Identity Object of which RSLinx Classic can access to call out the device ID. The name can be recognized from certain devices without an EDS file because certain devices support CIP, such as this 1756-ENBT module. Another reason we know the connection is OK, and this is important, is the fact that it's name is recognized. This means that the connection to it is OK. The 1756-ENBT does not have a Red X, just a Yellow ?. So we know that they are on the same Subnet and are most "likely" to be the devices of interest here. So this is the current Subnet that the workstation is using. This is recognized and is using 192.168.1.15.
Rslinx classic sort driver#
If you look at the computer icon this represents the RSLinx Classic Ethernet driver "AB_ETH1" that they are trying to browse. Why can we "deduce", "assume" and "guess" as such?. So those devices, we can only "guess", do not appear to be what our friend is interested in right now. We may "assume" that the Red X devices are remnants of previously browsed devices when the workstation was configured for the 10.1.60.x Subnet. If you read the above carefully, and examine the screenshot closely enough, you can "deduce" that our friend appears to be just referring to the 1756-ENBT that has a Yellow ? and NO Red X. Are you only referring to the device at 192.168.1.20?.
0 kommentar(er)
