dverespey

I've seen this in action as well. DDE links back to the PLC, driven by VBscript. Error handling can be an issue. Code manitenance can also be ugly.

Thanks, I called the Cypress office. At first they said they didn't do on-sites, after I pressed they gave me a local number, where I've left a message. We'll see what happens.

Thanks for the reply and source code, I've passed it on to the clients maintenance person, hopefully they will be able to take it and run with it.

Based on your reply the MX Components will preform like expected. We use the Automated Solutions tools in our Delphi applications to talk with AB processors. On the configuration front we don't have anyone who can do the Ethernet card configure, that's that help we're trying to dig up.

I have a client that has a system that is utilizing Mitsubishi PLC's. We need to get the processor hooked up the LAN and initially read some data points, later on we hope to replace a barcode scanning station with an HMI. Our in house experience is all Allen Bradley and the client’s maintenance staff is unable to configure the setup. The processor is an A2USHCPU-S1 and the Ethernet card is an A1SJ1E71N3-T. I've purchased the MX Components tools for the PC end. Reading through the past forum posts it appears that some ladder logic is required to config the card and I'm confused as to whether or not the MX Components will do the job on the PC side. Ideally I'm looking for someone locally who can come in and help us with the setup; some experience with the MX Components would be great.

I've been writing various applications for a number of years accessing Allen Bradley devices using the Automated Solutions ActiveX tools. I have a current client that is using Mitsubishi devices (models unknown at this point) that I will need to send and receive data to via Ethernet. I purchased the MX-Component tools after reading a few posts on this board. After installing the activex's I see a slew of available ones to import into Delphi. I imported the ActEther Controls as they seemed like the obvious ones. I now have 12 components on the Activex tab with cryptic names like ActQJ71E71UDP1 and ActQJ71E71TCP1. These might correlate to plc model numbers? So, anyone have a good source for samples, or previous experience with Delphi and these tools?