LabView 2014 - DSC module with Ethernet Modbus: Error 56

Sorry,
I try to connect modbus by Labview 2014 DSC module like this figure, and it occurred error code 56 at "Read Input Registers",
I have look for many soluctions, but still fail, can someone help me? thank you very much!

Did you confirm the address and port of your slave device is correct? Also, is your device a modbus master device or slave device?
I suggest you to read the help first, and then run the corresponding example
You can run the two example to test if the modbus function is OK. Then you can come back to test your third party device.

Similar Messages

Labview 2014 DSC install error

Tried to install the new DVD's and received an error trying to load the DSC module SQL server 2005 backwards compatability 64 bit wrapper on windows 7 64 bit enterprise version.
Picture attached is the install error. Second picture is the error when installing a download for sql 2005 from a microsoft website. Sounds like the installer is not checking for newer versions.
Is there a way around the install issue in order to get DSC module installed?

What happens if you select the "Yes" option to continue the installation? Does the installation then continue and complete successfully?
By default, the DSC 2014 installer should install SQL Express 2008. Is 2008 (or a later version) already successfully installed on your machine?
In any case, when running the DSC installer, there should be an option to "select features for install." If you deselect SQL 2008, do you still encounter the error?
Regards,

Compile 9076 with LabVIEW 2014 Worked good with 2012 SP1

An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 7 occurred at Open VI Reference in nirviOpenVIRefByNameOrPath.vi->niFpgaRemapObjsAndListIfUnderXNode.vi->niFpgaRemapObjsHandleXNodeSubErrors.vi->nirviMassageErrorList.vi->niFpgaErrorDialog_ParseErrors.vi->niFpgaErrorDialog_ReadErrorData.vi->niFpgaGenerateCode_ErrorDialog.vi
Possible reason(s):
LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
VI Path: C:\Program Files\National Instruments\LabVIEW 2014\rvi\CodeGenErrorUtilities\Diagram Constant
All text parsed:
<CodegenErrorList>
          <CodeGenErr>
            <ErrorCode>-64001</ErrorCode>
            <DynamicText>
              <TreeLineInfo>
                <TreeInfo>
                  <TreeID>1</TreeID>
                </TreeInfo>
              </TreeLineInfo>
            </DynamicText>
          </CodeGenErr>
          <CodeGenErr>
            <ErrorCode>-64001</ErrorCode>
            <DynamicText>
              <TreeLineInfo>
                <TreeInfo>
                  <TreeID>1</TreeID>
                </TreeInfo>
              </TreeLineInfo>
            </DynamicText>
          </CodeGenErr>
          <CodeGenErr>

Hi Nieman,
You have the right compilers for your FPGA targets, based on KB 609GUVBT.
Error -64001 indicates that there is an issue with one of the nodes in your VI. Since you are able to compile a blank FPGA VI, then you should try to identify the node that is causing this problem. When trying to pinpoint this node, I’d recommend executing your FPGA VI with simulated I/O on the development machine, as described in KB 3W6EFRLX,
Also, are you able to reproduce this issue when running one of the LabVIEW Example Finder FPGA VIs that targets your NI 9076? You can find these examples in the Example Finder's Hardware Input and Output>>CompactRIO section.
Regards,
Tunde S.
Applications Engineer
National Instruments

Response time between LabVIEW w/DSC module and RSLinx OPC server hosting FlexLogix PLC tags too long

We are experiencing communication response time delays between LabVIEW with DSC module and RsLinx OPC Server hosting all FlexLogix PLC tags (around 500-600 tags).
The nominal response time for the system watchdog is < 500ms, but we occasionally have spikes of up to 1.5 seconds once every few days even when the system is idling.
Changing more than six PLC connected shared variables at the same time from LabVIEW also causes the watchdog response times to spike above 500ms.
Our watchdog is programmed so that LabVIEW toggles the watchdog bit to 1 as soon the shared variable event detects that the PLC has toggled it to 0. The PLC, however, waits 300 ms until it toggles it.
Our system:
Windows XP SP3
LabVIEW 9 F3
RSLinx Opc Server v2.54
Allen Bradley FlexLogix PLC

What is your update rate set for in the RSLink OPC server?
You aren't toggling the same flag from both ends are you?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Tried to update Photoshop CC and Illustrator CC to CC (2014) - Installation failed with the following error message

Exit Code: 6
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
----------- Payload: Microsoft Visual C++ 2012 Redistributable Package (x64) 11.0.61030.0 {3E272A93-C06B-4206-AD02-0EBE02535E20} -----------
ERROR: Third party payload installer vcredist_x64.exe failed with exit code: 2147942750
ERROR: Failed to repair Microsoft Visual C++ 2012 Redistributable Package (x64). Please try repairing it by double clicking on the executable at

Whitmack please reinstall Microsoft Visual C++ 2012 Redistributable Package (x64) from Latest Supported Visual C++ Downloads.

-1950679035 ethernet modbus conection

Good morning
I am having some problems with mi application in the computer. I'm programming in my computer and testing on my work partner's computer. I am reading or writing data into a PLC (Modicon M430) and I used I/O server to do it (with ethernet modbus).
When I build the application, things work perfectly, and i can execute my application on my computer without any problem.
But when I executed the application on my work partner's computer things are not going well, I can't read or write registers.
I thing that the problem is because the I/O server, but I have tried to compile with the library, or with multiple options but I can't.
When I executed on my computer I can see all data on Distributed system manager and on the other computer say that it's not possible to see the data
The error of the program that gives me is:
-1950679035
Shared Variable in program.vi<APPEND>
This error or warning occurred while reading the following Shared Variable:
\\My Computer\'192.168.2.32'\Sensor 1
\\localhost\'192.168.2.32'\Sensor 1
Anyone have any solution??
Thanks!

If the Distributed System Manager isn't running, then something is seriously wrong! Has it ever worked? Have you ever had a successful deployment of Shared Variables? Have you recently installed a new version or updated LabVIEW? These questions are designed to see if something "broke", or possibly never worked in the first place ...
Bob Schor

Multiple errors with DSC modules modbus master and slave

Hi,
I've searched quite a lot of posts but haven't found solution for my problem. I'm playing with LabVIEW DSC module and it's modbus master and slave functionalities. Even the LabVIEWs own modbus examples (Modbus Simulator and Fundamentals) seem to work randomly or not at all: When checking the Variable Manager utility Modbus Simulator (i.e. modbus slave/server) seems to deploy variables correctly with good quality but Modbus Fundamentals (i.e. modbus master/client) most often shows unknown value or bad quality for all the variables. When running the VIs I get 'Error -1950679035 Unable to locate variable in the Shared Variable Engine' and sometimes some other errors too. If the Modbus Simulator (slave/server) is expected to work fine I guess I should get two slaves communicating, but this isn't happening either. So maybe Modbus Simulator example isn't working either.
I've tried undeploying and deploying the libraries, stopping and starting the SVE, booting PC, reinstalling DSC module, and setting firewall and antivirus software off. This problem is going on with two different computers, both of which have recently installed LabVIEW 2011, first PC with Win XP and second PC with Win 7. No other OPC servers should be installed to these computers. And what is really interesting, the problem seems to have nothing to do with my network since Simulator and Fundamentals examples are not working even if the network cable is unplugged!
Any suggestions? Replies are highly appreciated!

V8 has the same feature, but the words are different.
The Generator typically uses the Driver time base, and the Gl. Var Write is writing once per block.
So, to see all values, you must have a block size of one.
I set up the Driver timebase to 10 Hz, block size of 1. The Generator and the Read Variable default to the Driver timebase.
The Generator is making a 2 Hz Rectangle waveform. YOu can see that it's shifted, but otherwise intact.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Is it possible to connect labview with opc server without using NI dsc Module ?

Hellow sir,
I want to get data over labview using OPC server and i am not using any dsc module vi (Alams, print, GUI, security).I am using share variable to get data from OPC server to labview. Now i want to deploy that application to third party computer. (where there is no NI software is installed)
i am using labview 8.6 and 2009.
Many ? like....
1) what is the procedure to install that application in third party computer.
2) Do i need to use my dsc run time licence..?
waiting for your valuable feed back.
Thank you.
CLAD
Labiew programmer

Hi, When you connect to NI OPC Server by creating New I/O Server > OPC Client. You will see all registered OPC Servers running on local machine or remote machine. I used KepServerEx from Kepware and LSIS OPC Server from LG with no problems. Just make sure that the OPC server is running.
Hope it helps
Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
Assistant Lecturer
Mechatronics Department
Faculty of Engineering
Misr University for Science & Technology
Attachments:
LG.png ‏57 KB

Error 77009 labview 2014 with solidworks 2015

hello please am a student i want to ask you some quastion that i have probs with it
i want to creat an application with labview 2014 and solidworks 2015 with softmotion simulation so i got a probs that i cant deploy my project with error 77009 (0x00012CD1)
message error :
NI SoftMotion Error Codes
A function in NI SoftMotion was called without creating or starting the controller service. Verify that the NI Scan Engine switched to Active mode and that there are no faults on the axes.
please your help was a great things
thank you

Hi,
Here are a few helpful resources further explaining Scan Engine and developing with cRIO.
http://www.ni.com/pdf/products/us/fullcriodevguide.pdf
http://www.ni.com/white-paper/7693/en/
I hope this helps. Have a great day!
- Kale

Dsc module modbus server handling uint8 variables

Hello!
I have a problem with handling Modbus uint8 variables in the dsc module . Unit8 Shared variables
are available in labview but Modbus i/o server Unit8 variables are not:
http://zone.ni.com/reference/en-XX/help/371618J-01/lvmve/dsc_modbus_using/
In our controller we split some 16 bit modbus registers into two 8 bit variables to pack some more usefull data in there.
All of my shared variables are running nicely in the shared variable engine but I've no way of
easily binding them to my Modbus i/o server uint8 variables easily.
Any ideas?
I like the auto-scaling logging and binding of the DSC module shared variables
so I want to avoid some manual labview processes.
I want to view all shared variables in my front ponel at run time. I have 300+ variables so I'm trying to avoiding manual one-off hacks.
James

jamesy777,
The reason Unit8 variables are not available in the Modbus I/O sever is the nature of the I/O server data types compatible with the registers. If you’re writing to two registers, you can just read those two separate registers as U16s in LabVIEW. Otherwise, if you’re writing to the upper and lower half of the register, you can split the register into its 8-bit halves using the Split Number function in LabVIEW.
Split Number Function - http://zone.ni.com/reference/en-XX/help/371361L-01/glang/split_number/
Regards,

NI Modbus Lib in LabVIEW 2014

Does Anyone see a Problem with Using NI Modbus Lib in Labview 2014 is meant for labVIEW version 7.1-8.6. NI Directed me this way instead of the DCS Module since I am only using Modbus communication and that is just a very small part of the Module. It installed and shows up on the user pallets just fine and wires up the way you would except it to:
However when I run the program I time out in the read register vi. the example in the library does as well so I am at a loss as to what might be causing this issue.
Solved!
Go to Solution.

Hi
Try this snippet, you must have 1 in qantity you cant read 0, and you must put in the MEAP header.
// Lars
WiFi Guru, proud holder of world record in WiFi, 421 Km @ 2 mbit/s
Attachments:
Modbus.png ‏28 KB

Modbus (DSC Module) - Illegal Data Address

Hi
I need to implement a Modbus Slave in an application on a cRIO system. I set up a "I/O server" (DSC Module) and created shared variables for all the registers I need. The Slave has been tested and works fine, I'm using about 20 holding registers and I'm able to both read from and write to them.
The issue is that when the Modbus Master reads a holding register that I have not implemented the slave replies with the value "0x00 0x00" (LabVIEW default for integer) and not with exception response code 02 (a holding register inquiry for a nonexistent address should reply with function 0x83 and code 0x02 - Illegal Data Address).
Is it possible to change a setting or something, in order to force the DSC Module to send an exception response code, in stead of simply a default value, for registers that are not specifically configured?
Hope someone can help me - I would really like not to write all the necessary code for a modbus slave myself.

Hi Lenvno
Thanks for your reply.
I think you misunderstood me.
I have an application running on a cRIO. On this cRIO I need to implement a Modbus Slave in which specific holding registers should be used. Through a serial connection a different device, acting as a Modbus Master, obtains information from this slave.
On the cRIO, in my LabVIEW application, I have created an I/O server - Modbus Slave. Using shared variables I write values to specific holding registers on the Modbus Slave.
The Modbus Master obtains the values from these registers using function code 0x03, read holding register - this works correctly. However, when the Modbus master query registers that I have not defined, the I/O server on the cRIO replies with a register value of 0, instead of Illegal Data Address. It seems like when using this I/O server, all possible Modbus registers is filled with the LabVIEW default value and the slave therefore always will reply with a value even if the register is not used.
My question is therefore, how can i change this? If the Master query a register that I am not writing to (and is therefore unused), I would like the slave to reply with "Exception Response" code 0x02 - "Illegal Data Address", and not just the value of 0.
/Simon

Using MB Ethernet master VI with multiple Modbus devices

Hi,
I am not sure if this is the right place to ask this question; hope I'll get some help anyways. So, I basically have couple of Watlow EZ-ZONE PM controllers with ethernet and ModBus/TCP support. I am trying to talk to each of them using the MB ethernet Master Query VIs. However, since I need to talk to them simultaneously, I have them hooked up to my router. However, in that case, I am not being able to use the open TCP connection VI anymore, as there is no port no. to specify for that VI. I tried creating new VISA-TCP/IP resources through MAX, but i'm not sure how to use the VISA VIs to interface with the ethernet master VIs, as the latter need TCP refnums. Can anyone suggest some alternative in this case? Sorry, I am pretty naive about the networking features in LabVIEW and so any help would be appreciated.
Thanks.

If you have multiple devices on the network that you are trying to communicate with, they all need to have unique ip addresses. You mentioned port number, but if your devices use the modbus, the port number have to be the same, which is 502.
Yik
Kudos and Accepted as Solution are welcome!

LabVIEW 8.6.1 DSC Module and SQL Server Agent

I had the following system constellation:
- LabVIEW Professional Dev System 8.6.1 installed (complete)
- SQL Server 2005 Express
Since Microsoft's SQL Server 2005 is no longer distributed, I had to install SQL Server 2008 Express on my system, too.
Everything is working fine, but after installing the 2008 Express version the SQL Server Agent appears in the '2008 instance!
This is quite good, but normaly the Express editions doesn't contain the Agent...?!
Since LV8.5 (?) the DSC module uses Microsoft SQL Server Express, right? (--> This is very good, but the documentation of the DSC module is more than bad.!!)
Is there any context between SQL 2008 Express <--> LV DSC??

Hi _avr_,
There's no documentation about LV DSC
supporting SQL Express 2008 because it's not supported. It may work if
you were to detach the database and reattach it, but it's something we
have not tested.
You are writing, that SQL Server 2005 Express is no longer distributed, however this is a Software which is a part of Installation Pack of a DSC Module. So if you have the DVD for LabVIEW with DSC Module you could install it without any problem. For DSC Module 8.6 we included the SQL Server 2005 Express SP1 on the DVD.
I do not really now why in your case the Agent is appering. You have right, the SQL Server 2008 Express does not contain any Agent.I do not have any explenation for it.
NI supports only DSC with SQL Server 2005 Express. The DSC Module 2009 is also working with SQL Server 2005 Express SP1. For Windows 7 SQL 2005 SP3 is recomended.
I would suggest you to deinstall the SQL Server 2008 Express.
Best regards,
ENIA
NI Germany

Unknown error when adding a DAQ assistant to a blank VI in LabView 2014

Hello,
I currently have an issue when I try to add a DAQ assistant to a blank VI in LabView 2014 Service Pack 1, version 14.0.1.
It was working previously and has now stopped working. I have reinstalled LabView 2014 but the problem still exists.
I have also reinstalled NI-DAQmx 14.5 but this did not cure the problem either.
I have made sure that the C:\Program files\National Instruments\MAX folder has Read & execute, List folder contents, Read function allowed for the user account in use on Windows 8.1
Thanks in advance for the help.
Scott.

As soon an the DAQ assistant is dropped onto the VI block diagram an error window pops up stating that "An unknow error has occurred" with an ok button. This does not force LV to close, the DAQ assistant icon stays on the block diagram, the block is non functional i/o signals available to wire to, I can not access any properties for the DAQ assistant. Other than that LV appears to be functioning.

LabView 2014 - DSC module with Ethernet Modbus: Error 56

Similar Messages

Maybe you are looking for