Hi:
This is my first post here, so I'll try to state this briefly:
Existing system: Automated Storage/Retrieval machine in a production warehouse, controlled by SLC5/03. Operator station has a PC running a custom application to issue Store and Retrieve commands to the machine (connected via RSLinx using serial DF1). The commands come into the PC as ASCII strings from a VAX work order system via the PC serial port. The custom app then parses the string, puts the appropriate data into the SLC, and sets a bit high for "Execute". Meanwhile, the PC also hosts a couple of terminal emulation sessions so operators can interact with VAX and IBM systems for work order processing and inventory update, etc.
(Whew, that's a new definition of "brief" that hadn't occurred to me before...)
Assignment: Replace the old clunker PCs running NT 4.0 with nifty new panel PC's (XP Pro), AND while we're at it, rewrite the operator application using RSView32 (client's request). The idea would be to wrap everything up into one single app, including embedding the terminal sessions (I've located an ActiveX terminal emulator). I haven't used RSView32 before, but so far I've learned that neither RSView32 or RSLinx can really speak plain old ASCII on a serial port, and this really is the heart of the whole thing.
OK, if you've made it this far, here's the question:
If I'm gonna have to write VB (VBA?) code to handle the VAX serial communications and string parsing, and if I'm using ActiveX components for the terminal emulation, is RSView32 really bringing anything to the party? Couldn't I just write this whole thing in VB? Or am I asking for trouble on the SLC side by using VB with RSLinx? I have RSLinx Single Node, and assume I'd use the DDE/OPC mechanism to communicate with the SLC.
Thanks in advance,
--Mike Gibbons
Engineered Industrial Systems