Problems using Modbus TCP accessible by NI OPC Server

Similar Questions

• Problems using the local test on a Mac server

  I defined a local test for my website server: connect you using Local/network; file server: / Users /... / FPPATesting /; Web URL: http://localhost/FPPATesting/; For model server: No.  The site is hosted on a server of InMotion.

  I see that my local server folder was automatically filled with site files, but there are many missing, although the index.shtml file is there. If I drag the index.shtml file in the test folder in the field URL of Safari, it shows pretty much as it should, except that my Include files were not loaded. the Include files are in the folder test, but they aren't repeated. I get the same result if I choose Preview in Safari. And in this case, the files are all taken from the test folder; If the test server seems to be recognized by Dreamweaver.

  Curiously, if in the test folder, I open the file index.shtml, in Dreamweaver, Live View in Dreamweaver displays a seemingly complete site - almost. It is not complete because there not all the image files for the site. But the Include files have been included.

  So my problem is from my test server. I thought that call for a preview in one of the browsers show me the full site. Would it because I chose a server model "None"? I didn't know what else to use, as I am not including any content database. What should I do now?

  This can help working with server-side includes in Dreamweaver.

• problem with a 2012 opc Server

  I use LabVIEW 2010. I installed OPC Server 2012. Configure DCOM. Create tags OPC Server

  

  Create the project and create opc client

  

  But I don't see the tags in the variables:

  

  Can someone help me, I don't see why tags?

  What is under the OPC2 folder?

  Also, I checked my 2012 OPC Server readme (start > all programs > National Instruments > 2012 an OPC Server > Readme) and he said:

  "You can use the OPC servers OR with the following software applications:

  • LabVIEW 2011 SP1 full or Professional Development System
  • LabVIEW DSC Module 2011 SP1"

  This may mean that it is not compatible with your version of LabVIEW.

• You can trigger through communication Modbus TCP/IP PLC data acquisition without using a loop for?

  Hello

  I am trying to contact a facility through a Modbus TCP/IP communication PLC. I'm new to this method, but the idea is that the installation will send the logical (Boolean) values 1 bit by ethernet to my workstation which read and then will begin data acquisition. Basically, I need a triger to come to my pc. I placed my vi inside a structure case T/F which will run according to the signal, it receives data acquisition. However, for it constantly waiting, I put this in a loop for. The works of vi, but playback signals sometimes lagging behind due to the loop for. If I take the loop out and just run labview permanently, it works perfectly, but I know that the option is only for debugging and should not be used. So my question is, is there a better way to wait for an incoming signal?

  Hello!

  Please note that the order of execution of the write operations on the shared variable 000002 is not determined.

  For example, nothing prevents this order of execution:

  (1) value false 000002

  (2) set to true 000002

  (3) execution of the loop

  In what concerns the delay, you might consider placing a waiting vi in the case of 'false', or the loop uses 100% of CPU if I'm not mistaken...

  Kind regards

  Marco

• Modbus tcp 1.2 problem with labview 8.5

  I have a new upcoming project that involves a link to modbus tcp.  I downloaded version 1.2 of the modbus library and installed.  Everything appears on my palette, but if I try to open one of the examples he comes as for version 8.6.  I am currently using 8.5 but the download says it works all the way back to 7.1.  Any ideas?

  Are you sure that you have selected the correct folder for the "installation"? When you download the 1.2 OR Modbus Library (here: http://zone.ni.com/devzone/cda/epd/p/id/4756), you get a zip file. Inside this file, you will see 4 folders, one for LabVIEW 7.1, (issue 71), one for LV 8.2 (case 82) and also records 85 and 86. So make sure that you have done the installation with the correct folder.

  Let us know if this helps or not.

  Kind regards.

  Robst.

• Control PLC Modicon-Quantam of Modbus TCP/IP Ethernet.

  Has anyone use LabVIEW to program a PLC Modicon-Quantam successfully using Ethernet TCP/IP? I tried the examples MB Ethernet (master/slave) in the download nimodbus121 and it doesn't work. I really need to know the best way to connect and communicate to a PLC Modicon-Quantam using LabVIEW, Ethernet Modbus TCP/IP using the Excel spreadsheet. I need to write entry registers (write) shift in and read from holding registers. The software that I SMTX Modbus/TCP Master control ActiveX does not completely for me. I can ping to the controller from cmd prompt. I saw this webcast - creating a server of e/s Modbus TCP with the LabVIEW Datalogging and supervisory Control Module 8. I've also seen a webcast on OLE for process control (OPC). What should I write LabVIEW control and view records by using LabVIEW flags? Someone at - it a LabVIEW example that I can start with? Should I buy the DSP module for $1280,00? This will solve my problems?

  If you have found return data that you do not understand that I recommend trying to send output known of the automaton at least to determine what kind of conversion has to happen. This document talks about the Optomux protocol that can be used with programmable automata. You will need to find specific documents that tells you how to convert these data into LabVIEW. You can also start a new forum, since this is a separate issue from the original.

  -Hunter

• Modbus tcp read holding registers return not requested quantity

  Background: I have a client using ELAU motion system - they record data with records they want to be able to read on a cRIO match with some analog FPGA data (I have digital handshaking going on for this).

  LabVIEW 2010 SP1

  cRIO-9074

  With the help of the library of VI of MOdbus.llb OR communicate with the other system.  I can open the TCP communication without problem and actually get SOME records, but not ALL registry data, I want to read.

  I want to do is read the registers individual operating 330 U16 values.  I know how the data are split to represent different lengths (i.e. most of the data items use 2 records number represent a 32 bit).  I want just to read all of the individual records and analyze the data in another VI to convert it to other data types.

  I provided the .vi MB Ethernet Master Query (poly) with the starting address for the first register, then the amount of 330.  The polymorphic instance selected is "reading record keeping.  The array returned by this VI via 'Holding Registers' is only 74 elements and not requested 330.  I have no exception code and no error in LV.  Is there some intrinsic limit, i.e. the number of Holding Registers that can be read?

  I do not use the (not sure if necessary) MBAP header entry.

  Thank you.

  Simple solution once I dug in the series MODBUS/TCP protocol protocol documentation out there via Google.

  History of the modbus function series is the limitation that carried over TCP - the maximum amount of bytes in the pack a data can be only 256 bytes.  So I was limited to approximately 125 ~ records at a time.

  256 bytes is 2048 bits.  The use of the 16-bit registers which gives maximum 128 registers.  I went with 125 followed making easier totals.

• Timeout when using Modbus vi

  Hello

  I develop a .vi that queries data from two separate flow meters and a N - A via Modbus converter.  The interface on the flowmeters are set to 111 address and cannot be changed, so I can't use the same master to get the data of the two flowmeters.

  Ive attached a picture of the code for reference. Ive included only the part of Modbus to not confuse the issue.

  The problem is, when I change the schedule of the loop to 5 seconds, I take the readings of modbus timeout error 61 and loops from re - connect try but can't re - connect to them. When the time is 3 seconds or faster, they work perfectly.  4 seconds, I get an intermittent error, and the case of re - connect works fine.

  3 seconds or less = works very well

  4 seconds = occasional errors

  5 seconds = no job.

  I'm not an expert in Modbus with certainty.  So please excuse my messy code.  I intend to clean it once I get it working correctly.

  My flowmeters are RS - 485, 38 400 baud, Modbus RTU.  They connect to modules of ADAM 4017 I use the Modbus TCP to connect to.  The A/D converter is also of Modbus RTU and its on the same circuit as the MMin counter and its address is 3.

  Any help or advice would be appreciated. I can reach the entire .vi if necessary.

  First of all, I wanted to note that it looks like you are using a different API the API OR-supported Modbus, to take my answers with a grain of salt.

  A complete shot in the water, it is possible that the device that you communicate through a form of communication for a period otherwise it goes into a resting State after the connection. For example, if you do a Modbus TCP connection and then no communication occurs for more than 4 seconds, the slave goes into an idle state. This doesn't seem like a problem. likely, but it's something to look at. Due to the fact that I'm not familiar with the API you are using, I don't think that there is much more that I can recommend.

• Strange signal Modbus TCP/IP

  Hello everyone:

  I am facing a strange problem on the modbus TCP/IP communication, we have built the connection and use the modbus library OR read the analog signals, it works, but the return signals seems odd, for example (A 40-0 for value: 5, 3F80 for value: 4000 to 1 and 2), I went throngh modbus specification documents , but in these values do not respect the rules, is there anyone has idea about this?

  Thanks in advance.

  Best regards

  Are you waiting for floating point values? Modbus transfers bytes. It's the software front end to convert the bytes floating-point or of other signed/no signed integer values, 32-bit integers...

• Modbus/TCP connection to the controller of power Eurotherm EPack

  There are examples of how to connect to a power controller Eurotherm EPack a modbus/TCP connection?

  I downloaded the Modbus LabVIEW ni_lib_modbus_library library - 1.1.3.32.vip and installed using VIPM.

  However, I am not familiar with the Protocol modbus and terminology such as coils, keeping records.

  I can't even properly run examples for Modbus master and slave to this library :-(

  Most important for me now is just to read the value of the artwork process.

  "ITools" Eurotherm controller software provides information about something I think are an address of memory the value of process I want to read.

  However, I have no idea how to set the various parameters to get successfully connect and read the value of the process.

  Trying to solve my problem, I managed to have basic communication and engineering data conversion.

  Now I can read values of process as the power line frequency, voltage and others.

  Once you know, it's very simple (once you have the modbus library)

  Some things that remain unclear:

  -What values are 32-bit and 16-bit?

  -is the method of addressing identical for all parameters?

  -is it the same for reading and writing?

  I would like to be able to write the target value, for example.

  I'll contact the seller for these outstanding issues. The manual is not really clear (at least not for me). He mentions that some values may be treated differenly (they 16bits, but globally, so 5001 with a scale factor of 100 means actually 50.01 for example).

  See the attachment for reading cover base.

• need to read siemens S7 i/o in labview via Modbus/TCP

  Hi friends,

  We are developing an industrial project and facing a scenario in network as follows...

  Abt Project brief

  Its a treatment to the sweage plant. We use the NOR-PAC and Labview version: 8.5.1 for process control. We got a few 3rd e/s Party which must be monitior in Labview.

  Details of 3rd party

  -Siemens S7 - 200 with EM 277

  In our factory in the entire network is fo - TCP/IP. Now, we must take Siemens of e/s via TCP/IP in labview. To what extent this can be done. If it has to do with Modbus/Profibus converter can we do the configuration online without distrubing plant.

  Thank you & best regards

  Pravin Moussa

  Systems engineer

  Hi Pravin

  I am not sure of your diagram exactly what is your network. You have shown a link of the FO-tcp-ip for the S7-200. How does this happen? Or did you ask here, to work on options?

  Since the S7-200 can be slave profibus DP through the 277, it won't 'see' some other profibus IO anyway. You can use a Siemens CP243 module to give tcp - S7 - 200 ip connectivity. Also, is there a connection of profibus S7-300 and S7-200, all e/s of the S7-200 can be mapped to the S7-300, so you only need to worry about communicating with the S7-300.

  Another option

  Regarding modbus, they charge a lot of money for the Step7 from siemens modbus library. On the other hand, the S7-200 comes with a free modbus library, but it's the modbus RS485, not modbus tcp - ip series. Perhaps you could use this and use one of the many series-to-ethernet doors available.

  -Michael

• LabVIEW Modbus TCP with VFD. Could not establish connection / error 56? Any thoughts?

  Hello

  I'm trying to establish a connection to a VFD (Variable frequency drive) for academic research, for testing purposes. My implementation consists of:

  ---> LabVIEW (Master)

  ---> ABB ACS880 VFD (slave) with adapter from Fieldbus FENA-01

  ---> (ABB motor induction)

  ---> (Internal Combustion Engine)

  First of all, I'm new to Modbus TCP protocol, but I went through all the white papers of NOR, I have read and followed all the instructions from the manual of the VFD and the fieldbus FENA-01 adapter manual. I'm also pretty new to LabVIEW, but I'm confident, I have the knowledge to create the necessary VI.

  I created a simple VI who would be able to read some registers the VFD, which is attached below. The VFD is connected by Ethernet to network local ethernet and the Master PC is connected to the same network. When I run the VI, 56 error, which as I read from other messages of the forum is to not get answer within the given time.

  I tried the things:

  --> Check all cables are connected properly

  --> Double check the manuals

  --> Checking the FENA-01 in the chassis, which gives the indication of waiting for query modbus

  --> Looking for a gateway IP address, but I did not find, so I expected, I don't have to add it to the VFD parameters

  --> FENA-01 refreshing settings that always translates to "offline" status

  -->, I also checked in Labview > tools > Options where you check TCP/IP and there no port 502 written but I do not change it cause I had to leave the laboratory at the time. The port number was something like 3363 (something like that again)

  Issues related to the:

  --> Do I need to specify a new device somewhere in LabVIEW or in the control panel?

  --> What I need to create a separate VI to make the connection?

  --> What 'send 1150 for operating loan' and ' send 1151 for operation "means the control word?

  I would be very grateful if someone had information about this before the end of the week. I'm running tight on my period and I just can't stand this VFD with the limited power of the local command of monitoring mode.

  Thanks in advance for any help.

  Neo

  Hello, the problem is solved, and this could be a solution to problems like these.

  The IP address of the car was not on the same network as the Local Ethernet network connected to it. The IP address of the disk was 192.168.0.16 and the network was on 192.168.1.1. Once the IP address of the network changed to 192.168.0.1 communicated properly.

  I also have ping after and showed the communication.

  Thanks for the reply TST.

  Peace,

  Neo

• Modbus TCP/IP help

  Hello Labviewers,

  So I plugged in just a couple of the Honeywell UDA2182 controllers to my computer via an ethernet connection.  I have established communication using modbus (specifically the Datalogging and Supervisory Control of i/o Modbus server module) and I can say that reading through the computer.

  My problem is that everything is in some weird alien langauge.  I can't tell what settings I am displaying data and data that receives my computer are massively crazy that relate to anything.  My guess is that I'm supposed to somehow convert these numbers but I don't know how to do in this regard.

  Thanks for any help/advice,.

  Mike

  
  

• change comm driver for koyo modbus tcp

  I have a working system that uses a koyo plc and modbus driver.  I change to the controller for a scadpak with modbus tcp.  Is it possible to switch the comm driver without having to recreate all the tags and the screens that were created under the former comm driver?  I know I have to change registers views use to reflect the scadapak controller, but I hope I don't have to start!

  OK, I got it work.   I created a new modbus ethernet driver.  Then I exported an empty xls file to this new driver.  I then exported a xls of the FORMER pilot with the old information.  With the two spreadsheets open, I then cut and pasted the old news into the new xls file.  Then, I changed the former membership numbers for the new numbers, which I used with the new PLC.  It WORKED!   I think it is best when you change the PLC.

• Compaq Evo D5pM - problems using this model number, never find what he listed...

  Compaq Evo D5pM - (Pent4 - 1.7 GHz) problems using this model looking for parts or information number.  Serial number has not been useful.

  Someone said "aka Compaq D510." Trying to buy memory model (found on the case) my number wasn't so I tried to use D510 (it was listed). Apparently not the same computer / mine use 168 pins sticks and D - 510 came 188 pins. I did my 'upgrade' purchase by check the number of pins and using the already installed type.

  My computer is a vertical minitower - looks like D - 510-, but like I said the components are different.

  I was wondering if anyone knows a model Compaq Evo w / same components (P4 1.7 GHz; 168 pin memory) I could use for research purposes. The smallest horizontal model Evo often uses different (smaller) maps, etc..

  Tried the Ctrl-Alt-S keyboard shortcut to bring up the model number (etc.), but my keyboard shortcuts do not work on this computer. Run a search for edge came up with nothing to tune.

  I tried HP support and drivers.  With the help of several model numbers and found that absolutely nothing for HP Compaq or "Compaq" is in the list.

  It is a great 3rd computer that I've updated w / spare parts, use it remotely, especially for music. Only problem was the dark model number. If anyone has something useful to add would be most appreciated. Thanks in advance...

  PS I'm currently trying to identify MB for what it's worth, but a number of alternative model that works would be great.

  Hello:

  Your model is a d500 CMT HP.

  1 GB 128 x 64-133 MHz PC133, 168P DIMM, 3.3V, sync

  Type of memory: , (non - ECC)
  Maximum memory: 3 GB
  Slots: 3

  This is the page for support and drivers for your PC.

  http://h20566.www2.HP.com/portal/site/hpsc/public/PSI/home/?cc=us & lang = in & sp4ts. OID = 96294 & Task = & AC.admitted = 1389381517647.876444892.199480143

  QuickSpecs:

  http://h18000.www1.HP.com/products/QuickSpecs/productbulletin.html#spectype=North_America & type = HTML & docid = 10946

  Because nobody does more than the memory, it will be hard to find and very expensive.

  You can plan on paying more $ $70 / 1 GB chip if you do not find the specification above used on a place like eBay.

  You can buy a newer, faster CMT from HP on eBay for less than $70 delivered.  Memory is much cheaper to buy as well.

  http://www.eBay.com/ITM/HP-DC7600-Pentium-4-3-0GHz-40Gb-512MB-DVDRW-XPPRO-30-day-warranty-/281231108334?PT=Desktop_PCs & Hash = item417aae28ee