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

Similar Messages

Hi!!!I need your help!! Does anyone know if there is any Modbus lib or Modbus driver to use this en Labview BUT in LINUX?

I am using Labview to comunicate with ADAM modules, but I want to comunicate with them using Modbus protocol. I don´t want to use "ADAM protocol" ASCII comands that the modules can understand.
So I need a Modbus driver or Modbus libraries. The PROBLEM is that I am using LINUX!!!!!!!!!!!!!!!!
I am looking forward to your answer!!
Graci

Bichillo wrote:
> hi!!!I need your help!! Does anyone know if there is any Modbus lib or
> Modbus driver to use this en Labview BUT in LINUX?
>
> I am using Labview to comunicate with ADAM modules, but I want to
> comunicate with them using Modbus protocol. I don´t want to use "ADAM
> protocol" ASCII comands that the modules can understand.
> So I need a Modbus driver or Modbus libraries. The PROBLEM is that I
> am using LINUX!!!!!!!!!!!!!!!!
Please don't shout. It's deafening my ears!
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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.

Open vi reference conversion from Labview 6 to Labview 2014

Is there a way that someone can help me convert this VI written in Labview 6.1 so that I can work en EXE in Labview 2014.
I succed to open this vi from 6.1 to 2014 but it does not run. The open vi reference those not work in exe program. Someone know how I can replace that function...
Thanks!
Solved!
Go to Solution.
Attachments:
to convert 2104.zip ‏17 KB

Error 7 is File Not Found. So your dynamically called VI is not in your executable.
In the build spec for the executable in your project, there is a section for "Source Files". On of the options for the VIs is "Always Include".
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

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

Labview 2014 Excel Active X Property Nodes disabled - Why?

Hello,
I am using Labview 2014 and want to open, write to and close Excel by the use of Active X.
I am confronted with the problem, that, if connecting (Active X-) property nodes to the references (e.g. "Excel_Application"), right-clicking on the context menue doesn´t let me choose any properties, the item is disabled (one can read in German "Keine Eigenschaften" (no properties)).
How can I resolve this? What am I doing wrong?
Thank you!

I am having the same problem. When I left click to choose/change the property I do not get a list - instead I get the greyed No Properties popup - see screenshot.
If I drag and drop an existing property node from within an example subVI it connects to the reference and keeps showing the current property but I cannot change to a different one.
I am using LV 2012, Win7, Office 2013.
When I try with LV 2012, Win7, Office 2010, it works properly. So my guess is that is has to do with the version of office. But I would like to know the reason why as well.
Attachments:
NoProperties.png ‏67 KB

Making labview 2014 and Access 2013 db working correctly

Hi all,
i'm trying to gain access to a database created by Access 2013 from Labview 2014. Since we dont want to buy the NI toolkit i thought to use the old LabSQL library. Has anyone tried to do the same thing or give me some hints about it?
Actually i have tryed to run the example shipped with LabSQL but i received an error:
Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][Driver Manager ODBC] Nome origine dati non trovato e driver predefinito non specificato. in ADO Connection Open.vi->Example - Fetch a Table.vi
Reading the README file of the LabSQL i found this:
2. As with any database application on Windows, you'll need to create a DSN (Data Source Name) in the ODBC control panel. This DSN is used in your LabVIEW application to connect to the appropriate database. If you want to set up the example database, do the following:
   a.Go to your Windows Control Panels, and open "ODBC Data Sources"
   b.Click on the "System DSN" tab
   c.Click on the "Add..." button.
   d. From the list of drivers, choose "Microsoft Access Driver"
   e.At the dialog box, type in "myDB" for the Data Source Name. Then click on "Select..." button, and find the file "Sample Database.mdb" included with the LabSQL examples. Leave everything else as it is, and hit OK.
   f. Close the ODBC control panel
   g. Test the connection by running one of the examples provided.
My problem is that i can't find the driver named "Microsoft Access Driver" so i can't continue through the points of the instructions. I only found "SQL Server" and "SQL Server Native Client 11.0" but if i select one of this the dialog box that appear later is different from the one described in the README instructions...

You can certainly access the database without the toolkit. There are drivers that I posted on the forum and I have a small complete application on my blog -- you can even download the code from my SVN repository.
In terms of you specific problem, you don't need a DSN. What you need is something called a "connection string". Also, don't waste your time with ODBC. The built-in ADO drivers are easier to use. Again, check my posts for details -- I did a 3-part series on database connectivity.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How to map one modbus register to another modbus register in labview?

How to map one modbus register to another modbus register in labview? For example, let 40001 equal to 30001. Thank you.
Steven

Hello Steven,
Sorry, I was under the impression that you were using the complete Lookout development software (as opposed to just the Lookout Protocol Drivers). You cannot do any development (connections, mapping, etc.) with the Lookout Protocol Drivers (LPD). So, you were right. We have to do this in LabVIEW.
I ain't sure how exactly the Modicon floats work, but assuming what you're saying is correct, in your LabVIEW VI(s) you would read the DataSocket item corresponding to 40yyy+1 first, and then write this value back to the DataSocket item corresponding to 40xxx. Similarly, you would read the DataSocket item corresponding to 40yyy and then write the value read back to the DataSocket item corresponding to 40xxx+1.
A tip: I wou
ld at first make sure I have the OPC communication between LabVIEW and LPD working. Make sure you can read and write to the LPD registers via their DataSocket/OPC equivalents in LabVIEW. You can then implement the mapping as described above.
Hope this helps,
Khalid

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.

Bug LABVIEW 2014 - Calcul Quotient et Reste

Bonjour à tous,
Avez-vous remarqué ce bug dans labview 2014 sur la fonction quotient et reste?
J'ai lu sur le forum anglais que le bug a déjà été vu en 2009. Il est à nouveau présent!
C'est la seconde fois que je tombe dessus et qui m'oblige à utiliser un "patch maison", mais cette fois j'en informe la communauté:
Par exemple dans mon cas 8.6 / 0.1 = 85 et reste 0.1... (voir PJ).
Merci aux personnes concernées de prendre en compte ce bug dans vos prochaines mises à jour car c'est une fonction assez basique...
Bonne journée.
Julien P.
Certified LabVIEW Developer
Résolu !
Accéder à la solution.
Pièces jointes :
quotient.vi ‏7 KB

Bonjour à tous les deux,
En effet, comportement particulier mais qui n'est pas un bug.
Le "souci" vient des règles qui régissent la façon dont sont arrondis les nombres à virgule:
IEEE Rounding rules
C'est pour celà que dans l'aide détaillée de la fonction une remarque est présente (cf Quotient et reste (fonction)):
"Remarque Certains nombres réels ne peuvent pas être représentés par les nombres à virgule flottante de la norme ANSI/IEEE. Il est donc possible que des erreurs d'arrondi surviennent et que LabVIEW produise des résultats inattendus si vous utilisez les nombres à virgule flottante avec cette fonction. Pour obtenir des comparaisons et des calculs exacts, convertissez les nombres à virgule flottante en entiers."
Bonne journée,
Valentin
Certified TestStand Architect
Certified LabVIEW Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Problems con opcenum after installing LabView 2014

After installing LabView 2014, all other OPC compliant software (Matlab with the OPC Toolbox, Wonderware SCADA, OPC Demo Client from Softing, ...) previously installed on my PC (Windows 7) started to have problems in browsing OPC Servers. They were unable to connect with opcenum service for listing installed OPC servers. After manually unregistering opcenum and registering again as a service (and cleaning the windows register), everything was solved.
So I guess there is a bug with the labview installer that mess things up with the opcenum service. I haven't found anything on the web but in case anyone has the same problem, this is the "manual" solution. Anyway, I would like to ask NI to revise the problem.
Regards,
Jesús

Hello,
I haven´t heard of this issue with a standard LabView install, however there is a known issue with the standard DSC install. Have you installed DSC 7.1? If so you need to go in and modify the DSC install to uninstall the "Keyboard Filter". The filter causes the computer to hang when it attempts to suspend.
Regards
Thomas D.
NI Germany
(SRQ 202575)

LabVIEW 2014 x64 AppCrash StackHash crash

Our application is crashing somewhat inconsistently in the x64 compile, but not the x32 compile. We are using LabVIEW 2014. When it crashes, LabVIEW stops responding and has to be closed from windows. The View Details feature says it's AppCrash and further says StackHash_someHEXnumber. Another member of the team analyzed dump files and seemed to think it's crashing in the LabVIEW run time.
Any known issues out there that would explain this?
It happens on the original release of LV2014x64 and SP1. It happens in LabVIEW and in a compiled executable. If is not consistent, if we open the software and start running tests, sometimes it will never crash, other times it will crash before 1500 test runs. Our way of testing this has been to run 1500 runs, then close it then reopen it, run again. If it doesn't crash within 3 times of doing 1500 runs, we say that the crash probably isn't going to happen in that version of the software. So we've been selectively disabling parts of the software trying to figure out which code is triggering the crash.

Some more information:
In addition to not happening in LV2014x86, it does not happen in LV 2014 MacOS x64. So this is specific to LV 2014 Windows x64. Furthermore, if we save our code to previous and open it in LV2013x64 there's no crash (there's some hickups with the downgrade so it's not 100% apples-apples though) .
We have narrowed the crash down to a specific changelist in source code control. In that changelist we changed the architecture of how we pass messages around in our program. We used to use User Events to pass messages and the vi listening would subscribe to the user event. However, we found this created a memory leak in LV2012. So we switched to a queued based messaging architecture in this changelist. We created a variant which held the queues as a variant attribute associated with the message enum. This was so that when a message is sent we could do a fast lookup by taking the message and getting a varriant attribute associated with it (thus giving us the queues subscribing to that message). When we introduced this in LV2012 we stressed tested it all and it worked great. Later we upgraded to LV2014 and that's when the crashing started, we have gone back to this specific changelist and tried it with LV2014 it crashes.
We have found other parts of our code which if we disable the crashing goes away. Our suspicion is that this occurs due to a perfect storm of calling vi's asyncronously (which call other vi's ascncronously), passing messages to them via queues, and maybe the variant's containing queues in attributes. Based on what various programmers have seen via a variety of observations, our suspicions are that some combination of those circumstances is triggering some sort of LV2014 windows x64 bug.

Convert from LabVIEW 5 to LabVIEW 2014

hi,
I could not open VI. Could you convert this vi to LabVIEW 2014
Attachments:
mslumsrs.vi ‏432 KB
mslumsrs.vi ‏432 KB

That's okay. You can't.
The message about the duplicate post is some forum housekeeping to save people's time responding to this message in the event the other message is already answered. It just directs everyone to the first thread in case they stumble across this one first.

File dialog crashes LabVIEW 2014 on Mac OSX Yosemite

I know that Mac OS 10.10 (Yosemite) is not technically supported by LabVIEW 2014. If that's the only answer to this question, then so be it.
The following causes LabVIEW 2014 to crash on Mac OSX 10.10 (Yosemite):
1. Run the native File Dialog in LabVIEW 2014 (Express VI) , using "New or Existing File" as the selection mode
2. Select "New File..." when the file dialog appears
3. Enter anything as the file name and click OK
4. LabVIEW either crashes immediately, or hangs indefinitely and must be force quit.
Is there an update for LV 2014 (and the RTE) that does support Yosemite?
This bug makes deploying apps to the Mac basically impossible, Yosemite is the latest OS. Does anyone have a workaround for the issue?
Thanks.

LabVIEW 2014 SP1 seems to solve that problem here on my Mac OSX 10.10 system.
Now Apple may be nice for end users, but all those Apple fan boys sure would think a little different about it, if they had to write programs on the Mac. Apple keeps changing its APIs and their behaviour continously, inventing new APIs (which is fine) in a rapid pace, only to depreciate and remove older APIs at almost the same speeed!
Microsoft sometimes goes to the other extreme with maintaining backwards compatibility but working with Apple systems surely isn't easy as a programmer (unless maybe when one uses their high level click and point together web design applications, but I don't know that).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Cloud Dashboard not installing in Labview 2014

Hi guys,
I'm trying to use Cloud Dashboard with LabVIEW 2014.
I'm following https://decibel.ni.com/content/docs/DOC-38359 but the attachement at the bottom of the instructions does not open in VIPM Labview Tools Network. Instead I get the general page with 244 different tools but without the Cloud Dashboard tool.
Does anyone know if there is a incompatibility with the 2014 LabVIEW with the Cloud Dashborad tools/pallete/examples?
Cheers
Solved!
Go to Solution.

Hi Axero,
I have tested it just now on my machine running LabVIEW 2014 version 14.0f1 (32bit) and it worked for me.
Can you please tell me what is the exact version of LabVIEW that you are using, by going to
Help->About LabVIEW ?
Regards
Art
Applications Engineer
National Instruments

NI Modbus Lib in LabVIEW 2014

Similar Messages

Maybe you are looking for