LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI OPC severs Q series Mitsubshi, has anyone successfully interfaced the two?

I have a Mitsubishi Q-series PLC and we are running LabView 8.5.1 with the DSC module. I was trying to setup the NI OPC server demo to work with the PLC. I can connect to the PLC, but every time I put a tag in, the com faults and the error is that the PLC says the address specified dosen't exist. I made sure the address exists and that it is entered how the help file suggests. Does anyone have any suggestions as to what I am doing wrong. I want to verify that NI OPC server for Mitsubishi ethernet works before I buy the full version. 
0 Kudos
Message 1 of 7
(5,114 Views)

Hi ServerCorr,


The Mitsubishi Q-series PLC should be supported in by NI-OPC.  Check here for a complete list of supported devices.  As far as your connectivity problem, you might try using an example program just to verify that your programming is correct.  Are you using the demo version of LabVIEW? Maybe include a few screen shots of your code.  Thanks and have a great day.   

Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 2 of 7
(5,084 Views)
I am using the demo version of NI OPC servers. I went through the help files and followed the directions for setting up the server. The connection shows good until I add tags, then I get an error on the OPC server and on the PLC. Creating tags is were my difficulty is right now. Is there anything else on the PLC side that needs setup before you can add tags?
0 Kudos
Message 3 of 7
(5,077 Views)

Hi SeverCorr,

I posted last night but for some reason the post didn't update.  Anyhow, here is a link to the Mitsubishi PLC help file.  Look for the Mitsubishi Ethernet file and download it.  For the Mitsubishi PLC's they prefer UDP rather than TCP/IP and the connection has to be set up from the PLC side.  Without having the PLC it is impossible for me to figure out exactly what the problem is but it sounds like there is some missing configuration on the PLC side that allows you to connect but isn't allowing tags. It could be as simple as an addressing problem, where the tag is set up to references an invalid address on the PLC.  Take a look at the PLC setup help files and the addressing help files.  If you search "tag" in the help file you will find some usefull information on addressing the tag's etc.  Also, if the help file opens but has no internet links you will need to make an adjustment due to Microsoft security.  Right click on the file and go to properties.  In the general tab select the "Unblock" button and press OK.  Then the help file should function just fine.  Thanks and have a great day!

Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 4 of 7
(5,048 Views)
I can send you a copy of the Mitsubishi project as it is currently running on the PLC if that would help
0 Kudos
Message 5 of 7
(5,020 Views)

SeverCorr,

You could post it here on the forum and I am happy to look at it, but without having the actual hardware it will be difficult to figure out.   

Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 6 of 7
(5,007 Views)
I figured it out. I had the wrong network assigned in the device setup. I got thrown of course by an error I was getting. When I used the network 0, like I was supposed to, I continuously got a PLC communication time out. Turns out that the TCP comms setup isn't nearly as stable as the UDP. Also, I needed to pay attention to the scan time that I entered for the device as well as the scan time for the individual tags. In the end I switched over to UDP and slowed my scan time to fix my problems.
0 Kudos
Message 7 of 7
(4,909 Views)