drewh

Hey folks (saragani, presumably) I've been out of Unitronics development for several years, after handing our projects off to another developer, who just recently left our company. Now I'm back at it given said departure. I am trying to debug an issue with our app that relies on the Unitronics .NET driver and the first thing I wanted to try was see if the bug went away in a new version of the driver. It doesn't using just the .dll so I'm on to debugging with the source. Unfortunately, the source code download from the website at URL http://www.unitronics.com/Downloads/Support/Communication%20and%20Development/.NET%20Driver%202014.zip seems to be missing the Executers.Container.cs file. Where can I acquire the full source code? Robbie Walker Atlantic Packaging

Bump?

Hi guys, we have been polling for data in the data tables in our application using the .NET api. I was wondering if it's possible to initiate a push/upload to a webserver(ftp/webservice) to get the data out of the V130. I'm thinking I could post an xml file to a webservicetake that data and manipulate it. Thanks for any help.

Why was this done? Thanks for the help.

Thanks for the help

Hi, I'm using the datatables dll to read in datatable information instead of the proposed way in the unitronics documentation. Before(with the old method) it would take a few seconds to read the datatable. With the Datatables dll it takes 10 minutes to read the structure and values. This is the code I'm running. DataTables tables = new DataTables(plc, DataTablesReadOptions.StructureAndValues); If I just specify structure it will read it in a few seconds. With structure and values it takes a very long time. Thanks for any help.

Hi thanks for your help. I'm able to communicate past 16 now. It was a simple issue. I'm guessing I can add to the enum object in the source code for COM ports past 255. I'll try that and see if it works on Windows Server 2008 R2/Windows 7

Yes. We're(at my company) using Unitronics plc's in conjunction with Digi's(www.digi.com) realport driver to communicate with hundreds of locations. At this point we're having to create a new box(virtualized) for every 16 locations. Although 256 is still a lot better than every 16. I will be contacting shortly. On a side note after downloading the latest .NET driver, I still can't communicate via COM17. Thanks for your help.

Hi Alex thanks for your help. Is there a reason 256 is the hard limit? Thanks again.

Is there a reason I cannot connect to a PLC beyond COM16(via Visilogics or .NET driver)? Thanks for your help.