cmarcus

Hi Joe, Sorry, this reply is over a year in the making. Yes, the .NET SAP driver was specifically developed to perform production step confirmation transactions in SAP. The broader system is a .NET application with a fancy user interface. The operators bar code scan the relevant SAP production info into the HMI of the .NET application. The .NET application establishes connections with several production devices (thickness gauge, vision inspection camera, weight scale and a Vision PLC with multiple count sensors for tracking various defect modes). The manufacturing process is run and data from all the connected devices is streamed back to the single .NET app on a part by part basis. Live trends, yields, and failure modes are displayed and log files are developed for tractability. When the order is complete, the operator simply clicks the "Close Order" button and we run the SAP transaction in the background, using the bar code scanned order number, material number, operator ID, and the integrated device data for production yield and itemized scrap codes. The operator does not touch the SAP interface, nor do they keystroke anything in the process. The Vision's PLC's .NET driver was a game changer for us. It was the most straight forward way to have machine level / tag level access, and combine this data with the results of our various other devices. Unfortunately, when it comes to the Unistream, I still have not seen any examples as clean and as reliable as the Vision .NET driver to gain tag level access to the data from a stand-alone PC application. Thanks, Chris

Not sure this is the proper location for my question, but will there be a .NET driver or communications protocol for the UniStream as there is for the Vision? I've used literally dozens of Vision PLC's simply because I can tie together PLC operations and production control operations with several other peripheral devices (bar code scanners, RFID readers, measurement gauges, keyboard wedge devices, etc.) into a single PC based application, then integrate it into my customer's production systems or warehouse systems (SAP, SAGE, MFG Pro, and custom SQL databases). I've hesitated migrating to the Unistream models because I haven't seen a method as clean as the Vision .NET driver to read and write to specific memory locations in the PLC. Thanks, -Chris

Flex... no it didn't not include the corrupted file. The corrupted file would crash either way, so I trashed it. The issue that remained after the corrupted file was trashed was that if I double click any .vlp file, Visilogic would crash with that error message. I later discovered that if I opened Visilogic and did a File/Open and navigated it seemed to open ok, but I was never able to simply double click the .vlp file with out it crashing. But I still wanted to just be able to open by double clicking the file itself. I think I have it working now. Here's what I did. 1) Uninstalled Visilogic 9.8.31, looked in Common Files and Program Files and deleted any residual files. 2) Rebooted the PC 3) Installed an old copy of Visilogic 9.7 Build 60. 4) Rebooted the PC 5) Opened one of the example files, and Saved As to the desktop. 6) Closed Visilogic, then double clicked the .vlp file that was saved to the desktop. (It opened with out crashing) 7) Uninstalled Visilogic 9.7 Build 60. 8) Rebooted the PC 9) Installed Visilogic 9.8.31. 10) Rebooted the PC 11) Double clicked the .vlp file that was saved to the desktop. (It sill opened with out crashing) 12) Double clicked my backup file for my current project and it opened with out crashing. Thanks again to all for your support.

Hello Ofir, I do have backups of the project file, so no worries there. I checked the DB folder and I do not have a file called Current_OPLC.udb. I think that may be part of the problem. I think Visilogic is looking for it, and it's not present. Reading the error message again, it looks like there's a function in the UnPrHndl1.dll that has a class call clsDBHandler. This class has a function OpenConnection that opens a connection to a database. The error message indicates that it encountered an error opening the connection and notes an unrecognized format. However the target location where the database should reside does not contain the specified database (Current_OPLC.udb). Could someone send me this file. Maybe if I just drop it into the folder it will satisfy the condition of the OpenConnection function?

Just tried to restore it prior to when the event occurred, no luck. Same error message on start up. Hopefully the support team will have some suggestions. Hate to think I may have to re-install windows just to get Visilogic working normally again.

Ok just uninstalled/reinstalled as administrator. Still having issues. I cannot double click any .vlp file and have it open, Visilogic just crashes with the same message as above. If I open Visilogic as administrator, then do the File/Open and select the file I was working on, I still get a couple of error messages (see below). If I do File/Open and select any other files they seem to open. I'm thinking the root cause of this is a corrupted file or key and a dirty uninstall where the file or registry key persists. Looking at the registry after an uninstall and reboot, it's filled with Uni entries. As noted above, I already submitted a support email, so hopefully I'll hear back sometime soon.

Hello Everyone, I seemed to have "bricked" Visilogic on my PC. Was connected/online with a PLC, I shut the lid to my laptop, when I opened the lid my computer was off... not sure why or how it completely shut down but it was definitely off. Restarted the PC, tried to restart Visilogic and I get the error message below. Note the file referenced (Current_OPLC.udb) is not present in the specified directory. I uninstalled / reinstalled Visilogic, tried opening other projects, even tried just opening Visilogic with no project loaded. I can get it to open by right clicking and running the .exe as administrator, but it still crashes when I try to open any application. Additional Details: Windows Pro 10 64 Bit, Visilogic 9.8.31, Vision 130-33-T38 PLC. Also sent an email to support but as it was late in the day I haven't heard back as of this time. Any help getting this resolved would be appreciated. -Chris

Ok that makes sense. Thank you very much!

Hi, I have a customer that is looking to use a Unitronics PLC to add additional outputs to their existing system. The main system runs on a .net application, so the PLC would be mainly used to set/reset a MB or Output at a particular time. The response time needs to be pretty fast, likely a few milliseconds from PC send to output state change. Which communication method would be the fastest or would they be roughly the same? - PCOM - .NET driver - Custom protocol with short command sent from PC and received via FB protocol scan. Just getting a feel on how I should build the PLC communications class. Thanks,

Hi Joe. I have a V430--J-T38. Hi Ofir. That worked. Thank you for your help.

Hello Unitronics Team, I just updated to Visilogic ver 9.8.31 and the PLC OS that is packaged with it. When I hold my finger to the touch screen for 5 seconds it goes into Info mode. When I press the "Enter Info Mode" button, I get prompted to enter a password, but no on-screen keyboard shows up.

Wow, that was embarassing! LoL. Guess I just needed another set of eyes to look at this. Thank you very much.

Hello, I'm having an issue with getting the .NET driver to connect and read values. I am having no problems connecting using Visilogic, but when I take those properties and use them in the .NET driver they don't seem to be working. The interesting this is that I'm not getting an exception, so my application believes the driver is connected, but looking at the properties for the Ethernet object it appears not to be. When I put a break point on the oPLC object, it states that the object could not be evaluated because the previous function had timed out. When run it down to the last line and check the response values it is null. Here's the code: Ethernet ethernet = new Ethernet(_cell1PLC_IP, _cell1PLC_Port, EthProtocol.TCP, 3, 3000); PLC oPLC = PLCFactory.GetPLC(ethernet, 1); oPLC.SetExecuter(OperandsExecuterType.ExecuterPartialBinaryMix); // Create the write request // ReadWriteRequest[] readShifts = new ReadWriteRequest[1]; readShifts[0] = new ReadOperands { NumberOfOperands = 1, OperandType = OperandTypes.MB, StartAddress = 0, }; // Extract the shift times // object[] shiftTimes = ((object[])readShifts[0].ResponseValues);

I have a display board with a Red Lion controller that networks 3 V430 PLC's via modbus IP. Everything is connected via the Ethernet card add-on installed into port 2 on each PLC. Is it possible to also remote connect to the PLC tough this same Ethernet card (even though it's in use as a modbus slave)? If so how would I do this? When I try to go live in Visilogic or Remote Operator it cannot establish a connection. Thanks, -Chris

Thank you for the response, Joe. I'll look into changing to a TR34 or TRA22. Best Regards, -Chris