Modbus tcp 1.2 problem with labview 8.5

Similar Questions

• Modbuss problem with Labview 12 DURATION

  Hey guys / girls.

  I have a labview.exe work created with Labview 12 on a PC with the completely installed verstion LV12

  As I said created and built and tested again on the pc

  On another pc I just installed labview RT and the exe to bed

  the program consist of modbus

  but it does not work.

  Y at - it an additional package, I need to add more to the Runtime to get my Modbuss to work

  additional information:

  I tried two different com Modules while both B & B electronics is with drivers other works out of the 232/485 with drivers troubleshooting

  It is on Win 7 32 bit labview is 12 32-bit

  -Kurt

  What modbus library are you using? DSC or VISA? You have the runtimes for what you use.

• Signal Express version unknown problem with Labview VI

  Hi all

  I am trying to run 2010 Labview Signal Express VI. It gives me "unknown version" problem. When I checked for Labview versions, he said 10.0f2 and Signal Express can read the version of LabView 2010. I don't understand this. 10.0f2 is not just a patch for version 10.0? I will appreciate if someone can help me with this.

  Kind regards

  Kanu

  Hi Kanu,

  I tried to write a simple VI and its importation to the Express Signal and I have not had any problems. I use 32-bit LV2010f2 and Signal Express 2010. I have attached the VI I used so that you can try it yourself. I followed the instructions of this KB to create a distribution of the source file. If you follow this KB and still can't make it work, can you please post the VI?

  Thank you

• Problem with LabVIEW

  I met a problem when using the peak detection function in LabVIEW...

  Basically, I load a waveform in VI to detect peaks using the function of Ridge detection. of the waveform, it is obvious that the first peak will happen about 10570Hz...

  Using size 3 subgroup, it detected 1 pic to 10567Hz (correct)

  When you use the size of subgroup of 4, it detected 1 pic to 10569Hz (correct)

  When you use the size of subgroup of 5, it detected 1 pic at 12737 Hz (bad)

  When you use the size of subgroup of 6, it detected 1 pic to 10588Hz (correct)

  When you use the size of subgroup of 7, it detected 1 pic to 10588Hz (correct)

  And using other different sizes of subgroup, the freq agrees with waveform... Why when you use the size of subgroup of 5, it does not give good playback? Is there a theory or a reason for this? or just a bug with the LabVIEW function?

  A VI is fixed and the default values are loaded.

  Appreciate any assistance/advice.

  
  

• Problem with Labview communication with Arduino Uno

  Hello

  I tried to run a simple program in labview through my Arduino Uno R3 all morning and keep running into the same problem: no response from my Board of Directors. I'll catch you up on what I've done so far:

  -flashed LIFA Base to my Arduino
  -Downloaded the driver update of VISA

  written-a the block diagram (I hope) for a led on off function

  When I run the program in labview, the RX flashing intermittent, continue for 30 seconds before stopping. The led on pin 13 is not turned off as it should, and I have no control over the power function light. I also tried a program of control of servo with no response and the same flash of RX. Never the TX flashes.

  I am quite stuck, so any help is greatly appreciated. Also I'm not a comp sci guy, I'm just an engineer in mechanics with a half of C++ so keep pg when it comes to the language of the computer.

  I've attached a picture of my diagram of LED, see if you can spot a problem.

  Thanks in advance!

  SOLVED: Reset the Arduino card after that labview had sent his orders (while the RX light was still flashing). Works like a charm.

• Problem with LabVIEW 9.0f2 and VISA 5.0 on Mac OS x 10.6

  Hello

  I'm using MacOSX 10.6 and Labview 9.0f2. I installed the lates VISA (5.0.0) drivers, as they are the only support OSX 10.6.

  Now, I try to run the "basic series write and read" example and get the following error:

  Error 1073807343 has occurred to the property node (arg 1) visa set up a Serial Port (Instr) .vi-> basic series writing and Read.vi

  Possible reasons: VISA: information about insufficient localization (Hex 0xBFFF0011) or the device or resource is not present in the system.

  As I am a newbie to Labview, I'd appreciate any help on this...

  Thank you

  Daniel

  Hello

  You do not have a device series on behalf of resource, you use to write and read and take?

  Did you check with Max OR and log on to this device.

• Problems with labview on TestStand deployment system (usually run without a license of labview)

  I'm trying to deploy a system using testStand for a machine of deployment for the 1st time. I built my Installer and image etc files The files of the installation on the target however machine when I try to run my program in mode operator TestStand I get errors relating to Labview. The only way I can work around this error is to activate a Labview license on the deployment computer, is not viable.

  The error I see when I turn off my Labview license simply indicates that an error has occurred accessing the Labview ActiveX automation server.

  I have included engines of execution etc. in my Installer. As this is my first build is there something obvious I've missed here?

  Thanks for any input.

  Vinny

  Vinny,

  My first guess is that the setting of the LV adapter on the deployment computer is always set to "LabVIEW development environment". You must change this to "runtime".

  hope this helps,

  Norbert

• problems with labview 2013 build specification

  I have a few screws of LV2010 I want to use to create an application to run with RTE2013. I have LV2013 on my computer.

  Without a massive compilation of the LV2010 screws, the element of selection of source files in the build specification has no project file to choose and it won't allow me to go looking for.

  Any ideas why this happens?

  Thank you

  Right, you must create a project and put in all of the screws to be included in the compilation - including one that is the top-level VI. Once this is done, you can save the project, just not to re-record the EIS.

  Now you should be able to define your spec to build according to normal.

  Mike...

• IP in chain - timing problem with Windows 10

  Hello

  I was working on a project and noticed something that I wanted to highlight to others and to see if I could get a reasoning as to why this is happening.

  I started this about four months ago and recently updated my computer to Windows 10 up-to-date project. I am under Labview 2014 V14.0f1 (32 bit) and had not seen any problems with labview until I activated an error logging code which reports data to a syslogger.

  We started noticing that the recorder took much longer than usual to deal with errors and in turn slowed down the whole program.

  When we dug in the question, we found the slow down was the INVESTIGATION period to the block of the string that is used to extract the host name. It took about 4.5 seconds to complete. I have run the same code on a windows 7 VM and it run under a 1 ms...

  No idea why IP chain is taken almost 4 500 x times more time in Windows 10 vs Windows 7? We have worked around the issue by making a control that can be set from a file configuration of the value, but I wanted others to know and hopefully get an answer to why this is the case.

  Thank you

  Chris

  LabVIEW 2014 is not technically compatible with Windows 10.

  Compatibility of the versions of Windows with LabVIEW.

  Maybe the search time is affected by something that has changed to win 10.

• Possible GPIB communication through interactive control of Visa, not with Labview

  Hello

  I have a communication problem with Labview with GPIB instruments (with functions of visa).

  I get:

  "Error 1073807298 occurred at the VISA opening

  Possible reasons:

  "VISA: (Hex 0xBFFF003E) failed to perform operation due to i/o error."

  However, it works with an interactive control visa and this is where I am confused!

  Here is my setup:

  -Labview 2011 assessment

  -VISA 5.1.2

  KUSB - 488B with the associated drivers (adapter USB to GPIB of Keithley)

  Because I can speak with my instruments in visaic, I guess the installation of drivers for the Keithley interface is ok.

  Trace IO NOR I see beeing of commands passed through Labview to VISA so that they "see" between them.

  I found a thread where someone had the same problem and its solution was downgrade to Labview 8.5.1, which is not possible for me.

  http://forums.NI.com/T5/instrument-control-GPIB-serial/Keithley-2700-driver-problems/TD-p/1474212/PA...

  You have an idea to solve this problem?

  Kind regards

  Baptist

  Here's a follow-up on this issue.

  I tried with Labview 32-bit on main machine: it works.

  The pleasure is that I have to use Labview 64-bit.

  So the ultimate solution is now to run a client and a server of visa on the machine: Labview 32 bit can directly access my resources GPIB, Labview 64-bit must go through the closure of the network.

• 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

• 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

• Problems with migration from LabVIEW 2012 VBAI 2012.

  Hello.

  Someone had problems with the migration of the VBAI 2012, 2012 to labview?
  I'm filing this disadvantage when use migration in VBAI everything works fine, when I use LabVIEW with 'Vision Acquisition Express' for example, everything works as it should.
   
  The solution I've done has been to work with the control VBAI API and it worked perfectly, but I wonder, if a bug or a known error on this process.

  Thank you.

  Finally, I solved it by installing the "Vision Development Module 2012 SP1". With this update worked correctly migration.

• problem with a block of memory in labview 2009

  Hi all

  I have "ERROR: MapLib:979 - LUT4 symbol" during the compilation process (lots of errors like this), and I discovered that the reason of my problem is block of MEMORY.

  To be sure that the problem is in this block, I did a very simple project in LabView 2009 (on FPGA Target PCI5640R) only with the use of this block you can see in the photo, as well as in file test_memory block.lvproj attached link: https://www.dropbox.com/sh/u87f1oihelmm4dq/Jo_6-bICSf

  

  I have a problem with compiling VI with this block, and I have so many errors like:

  ERROR: MapLib:979 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<0>1.
  (output = window/Thatcher/res000001ed_wi<2>) is the input signal
  "window/Thatcher/res0000020d_wo<1>" that will be deleted. See Section 5 of the
  Map a report file to find out why the input signal will become conveyors.

  or

  ERROR: MapLib:978 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<23>1.
  (output = window/Thatcher/res000001ed_wi<25>) is an equation that uses
  input pin I2, which no longer has a connected signal. Make sure that all the
  the pins used in the equation for this LUT are signals that are not cut
  (see Section 5 of the report file map for details on which signals were
  adjusted).

  Entire report, you can see in the file report.txt on the attached link.

  I would appreciate if someone could take a look at my problem with simple project and suggest me a solution.

  I'm really stuck with my biggest project which need to have this memory block.

  I'm looking forward to hear from you,

  King looks

  ING. Damir Hamidovic

  Hi all

  I find a sollution to my problem.

  In memory-properties-general-setting up, I changed the block to look up Table memory, and I compile memory.vi and run it successfully.

  I did change as you can see on the picture:

  

  Just, can you tell me is it all "bad properties" and limits the use of this type of memory (Look up Table) of the implementation?

  King looks

• RS-232 via TCP/IP with LabView

  Hello

  I have currently a standard equipment is read through a RS232 converter TCP/IP hardware.

  On the computer with labview, I use a third-party serial port virtual that data reads the TCP/IP and converts this COM port data pack

  I then read the port COM normally with VISA.

  I would like to remove the third-party TCP/IP software RS232 and LabView read the TCP/IP port and convert to series.

  How could do?

  More details about the hardware and the 3rd party software;

  thydzik.com/Monitor-cms2000-Inverter-via-tcpip-usr-tcp232-E4-rs232ip-Convertor/

  More information on labview here code;

  thydzik.com/log-Solar-generated-to-pvoutput-with-LabVIEW/

  I don't think it's as complicated as you seem to expect. Try the VISA TCP approach. Create a resource of VISA TCP, in raw mode, as explained in the white paper. Take your existing code, replace the COM resource with the new TCP one, remove the configuration of the port series, and it might work. Make sure to close the resource when you stop the program.

  If you want to go with the TCP functions, look at the examples. You open a connection, read and write strings in it, exactly as you would with a serial port and close it when you are finished.