Jump to content

Aaron T

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aaron T

  • Rank
    Newbie
  1. Hello, Does anyone know of any problems with including both a Modbus Config and a Protocol config for the same COM port in the same program? I'm talking to a peripheral device which under certain circumstances may need to be sent an ASCII Protocol command to switch it to Modbus mode, so I will need to be able to do both types of communication in the same program on the same port. Can the two coexist, or will I need to re-execute the appropriate Config block when switching from one communications mode to the other?
  2. Hello, I'm trying to help a customer set up UniOPC Server on their end to work with our equipment; this is my first time using UniOPC Server. I was able to install and run the UniOPC Server on my own PC (Windows 7 64-bit with UAC turned off) without trouble, and I saved my .upc configuration file and send it to the customer. They installed the software on their end (I believe also Windows 7 64-bit), but after loading my .upc file, when they clicked "RUN" an error dialog popped up saying "Run-time error '339': Application-defined or object-defined error", with only an OK button, which I believe closed the Server. At my suggestion they uninstalled the software, disabled UAC and reinstalled it, and then ran it as an administrator, but still got that error when clicking RUN. They even installed the UniOPC Server on a second computer (again with UAC disabled) and manually entered the channel and PLC parameters instead of loading my .upc file, but even on a second PC, got "Run-time error '339'" when trying to run the server. Does anyone have any idea of specifically what run-time error 339 signifies, and why they keep having this problem when clicking "RUN"? For reference, here's a cut-and-paste of the settings I had them enter manually: Click the "Channels Collection" button on the toolbar. In the Channels Collection window, click the "Add" button. Enter these PC Communication Parameters: Connection type: TCP/IP (Call) Remote IP: 10.63.5.180 Remote port: 20256 Click "OK". Click "Close". Click the "Add PLC" button on the toolbar. Enter these PLC parameters: Name: IV Monitor Type: Vision Unit ID: Direct Connection Channel: TCP/IP (Call): 10.63.5.180/20256 Enable: Enabled checked Click "OK". In the "File" menu choose "Save" to save the configuration. Click the "RUN" button on the toolbar to start the server.
  3. I agree wholeheartedly, the lack of a proper "Undo" function is a major source of frustration when using the HMI editor. In any other piece of software, "Undo" undoes whatever your last action was, but in VisiLogic it seems to apply to only a very limmited subset of actions. If I accidentally move an object out of position, getting it back is a big pain. That combined with the lack of a configurable alignment grid and a proper "snap to grid" function makes the HMI editor the most painful I've used.
×
×
  • Create New...