485 modbus communication with Watlow PM trouble

I have a Watlow PM that I can see over MAX now and using the EZ zone code can get manufacture info from. I also am using (for the first time) the add-on Modbus over serial tool from Saphire to try to write or read anything from it and I always get a "time out" error from the slave. I tried to do a simple VISA read as I found on some posts and I get the same time out error. It seems if I try anything from Labview I get this error. I even tried writing Hex to the thing with the same results. Can someone throw me a bone?
Solved!
Go to Solution.

There are a couple of free libraries.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/201711
https://decibel.ni.com/content/docs/DOC-30140

Similar Messages

Modbus Communication with Cube400

Hi
I have problem to communicate with Cube400. It is using modbus protocol and communication is going through rs485. I must connect it to cRIO 9022 serial port so I used converter IC-485SI (converter manual on page: http://www.esis.com.au/Converters/ic485si.pdf ) to change communication from rs485 to rs232.
I tried to used Modbus I/O Server. When I have one variable binded to modbus register I have proper reading. When I add second variable then I lose readings from first one. This solution is in VI called ModbusIO_rs485.
After this I tried to communicate with Cube400 by using VISA blocks. I tried to send specific modbus message. On the begging I get proper response several times but right now I am getting timeout error. This program is in VI called VISA_MBP_ForcePush.
I am attaching project with this VIs
What is wrong here ?
Best Regards
Pawel Dudzik
Attachments:
LABVIEW.zip ‏28 KB

In your program you read 16 bytes immediately after the write.
You should add some time after the write and you should see how many bytes there are available and read that number of bytes.
Look at the COM example shipped with LabVIEW.
And you use the WRONG CRC it should be 0x5679.
Try communication with the loopback command. Sending 0408 0000 8844 866D (Hex data) should return the same data
Kees

Modbus communication with Modicon premium PLC

Is it possible to communicate modicon premium plc(P574634M) and Lab view through modbus.
If possible how?

First, do a search for Modbus. There are several options available for communicating with Modbus devices from LV.
Then, if you have a more specific question, you can post it to the LabVIEW board (you posted to the feedback board by accident).
Try to take over the world!

Modbus communication with a load cell

Hello..!
I'm a new user of LV and I try to communicate with a load cell by RS232 modbus.
After installed NI Modbus Library I created a master VI with labview 8.6 using these library, and I can obtain a communication with load cell , these value are added into 1 register U32Bit, and it's okay, if I press a load cell I can see the values go on.( from 0 to 65535) . Now I want to show on front panel the value in KG , as decimal point,, for a right interpretation of value for my customer, so I added a block array to unbundle than I convert a value with I32Bit ( -32768 to 32768 ) with an indicator, but I can't see any values..
I suppose I doing something of wrong ( conversion ), I read some KB, but I can't see a suitable solution..
Can someone give me a link or information to show me an example to convert this value..?
Thanks in advance for any helps..
Configuration of MAster VI:
Read holding register
Starting address 2012 ( query for obtain net value from the load cell)
quantity 1
Slave address: 1
RTU
9600
Com 3
parity none
Solved!
Go to Solution.

Hello Ravens,
I tried to use your good advices and finally I can communicate correctly with my trasducers showing on front panel the right value ( Kg). Has been a problem of conversion from output of register ( U16Bit as 0-65535 ) to I16bit ( -32765 to 32765).
Thanks very much for your help, and I hope to chat again for new challenge...
Have a nice WE
Julio
Attachments:
Comunicazione Modbus load cell.jpg ‏46 KB

Modbus communication with an automation direct GS2 AC Drive

Has anyone written any VI's to communicate with an automation direct GS2-41P0 AC Drive using modbus? I need to ask the unit a few questions while it is running and possibly start and stop it. I have started searching around and found the NIModbus VI's. I just have not figured out how to modify them to suit my needs yet (I just started playing with this today). So far it looks like Modbus might make my head explode, but I am hoping it is easier than it looks at first.
Bryan

Hi Bryan,
I've never tried using modbus to communicate with that particular device, but if you have any specific questions I'll do my best to answer them.
Also, you may be interested to know that the AutomationDirect GS2 Drive is supported by our NI-OPC Server, which may be a more attractive alternative to modbus. I highly recommend you take a look at the LabVIEW Datalogging and Supervisory Control (DSC) module (wihch includes NI-OPC Server) to see if it is something your application would benefit from.
Supported Device & Driver Plug-in List for NI-OPC Server
Connect to Any PLC
LabVIEW Datalogging and Supervisory Control
Eric V
National Instruments
Applications Engineer
Certified LabVIEW Associate Developer
"I'm a Ramblin' Wreck from Georgia Tech and a helluva (NI Applications) Engineer!"

TS1717 Having trouble running iTunes version 11.0.2 on a Dell Laptop running Windows 7 Professional Service Pack 1. Keep getting an error message "the software required for communicating with iPods and mobile phones was not installed correctly..." reinst

Having trouble when I launch iTunes (version 11.0.2) on my Dell Laptop running Windows 7 Professional (service pack 1). I get an error message indicating software required to communicate with iPod and mobile phones was not installed correctly. Do you want iTunes to try to repair this for you? I normally respond with OK and it immediately tells me "could not be repaired. Please reinstall iTunes..." I have done this a number of times to no avail.

I also notice Quicktime is not getting installed at all.
That one is normal nowadays (ever since the iTunes versions 10.5.x).
The software required for communicating with iPods and mobile phones was not installed correctly. Do you want iTunes to try to repair this for you?
Let's try a standalone Apple Mobile Device Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of why it's not installing under normal conditions.
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/
Right-click the iTunesSetup.exe (or iTunes64setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleMobileDeviceSupport.msi (or AppleMobileDeviceSupport64.msi) to do a standalone AMDS install.
(If it offers you the choice to remove or repair, choose "Remove", and if the uninstall goes through successfully, see if you can reinstall by doubleclicking the AppleMobileDeviceSupport.msi again.)
Does it install (or uninstall and then reinstall) properly for you?
If instead you get an error message during the install (or uninstall), let us know what it says. (Precise text, please.)

My Notes will not display and I get the message "Trouble communicating with icloud". The notes are available directly at icloud

When I try to open "Notes" I get the message "Trouble communicating with icloud" The Notes are avaiable direc tly on icloud. just not on my laptop.

gkmorton wrote:
My IPad is loked with a message "ICloud Backup- This Ipad has not been updated in 2 weeks.
Perform a Reset...
Reset ( No Data will be Lost )
Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
http://support.apple.com/kb/ht1430
gkmorton wrote:
I have connectd to my computer and it says there is a new software version available.
Before Updating... Decide if you want to... If you Update... there is No going Back...
NOTE:
It is both Prudent and Recommended to Backup Before any Major Update or Upgrade.
How to BackUp
http://support.apple.com/kb/ht1766
What gets Backed Up
iTunes http://support.apple.com/kb/ht4946
iCloud http://support.apple.com/kb/PH2584

Communication with modbus devices

Hello All,
My name Peter, I am currently exploring what LabVIEW has for instrument communication. I have explored a little on NI-Visa and used it for instrument communication through USB and Ethernet. My next task just now is to see how I can communicate with Modbus devices. I have done some background reading on modbus communication protocol and now have some level of understanding of what it is about. I hope to understand more as I continue to read more materials.
I came across an NI-Tutorial titled Connect LabVIEW to any PLC with Modbus. It is about communicating with a networked PLC using modbus. I followed all the steps described for creating Modbus master I/O Server, Binding shared variables to Modbus Address through the I/O Server and writing to Modbus Addresses in LabVIEW. On running my VI to deploy the shared variable, the following error occured.
Can anyone please guide me on what to do because I do not know exactly what is going ON. I engaged in this excercise with the hope of getting to understand more about Modbus communication and then see how I can apply thesame idea to communicate with the Modbus device available in my Laboratory. Please note that I do not yet know much about modbus communication and I am just learning about it now. I do not have any PLC connected to the network. Could that be the reason for the error? If anyone has got any other relevant document to help me get started with modbus communication I will be happy to have them posted here.
Thanks very much for taking time to read through my post message. Hope to hear a quick response from you.
Regards
Peter

Hi SmithD,
I would like to say thank you very much for making out time to respond to my queries. I have done as directed but still not getting result. Following the wire mode port setting configuration, I stopped the process and then selected the RS485/wire4 as the wire mode. On running the VI, an error pops up with the information that the Visa resource is Valid but the port cannot be accessed. I noticed that If I undeploy the shared bound variable the error does not pop up anymore. I concluded that maybe I was not supposed to have added the VISA configure Serial port in the first place.
Kindly tell me what to do.
My task is to read the holding register from a Modbus device. I have the register map with me, and know the TCP and RTU settings for this device. After the attempts I have made so far I was forced to believe that perhaps the device was not responding. I then resolved to using the QModbusMaster which was previously used to read the holding register. For reasons I don’t not know, It worked well with the TCP communication and returned an error that read " slave threw exception > unknown error". With that, I am now sure that the device is functioning properly, at least with the TCP.
Having obtained result from the TCP using QModbusMaster application, I want to simply do the same using LabVIEW.
Some few questions for which I would want to ask for clarification are:
1.) When using the Modbus Library, do I need to create both master and slave instance to be able to read the holding register? My attempt was to create a Master instance with the RTU parameters. The starting address and number of registers were specified at the input terminals of the Read Holding Register VI. This VI immediately followed the Create Master Instance VI. I was expecting that that would read the information contained in the specified registers and output it at the register value terminal. One challenge with this attempt was that with RTU it didn't work. I tried selecting TCP as the VISA resource. But the device was not showing on the list. I went to MAX to create a new VISA TCP/IP resource under the network devices but MAX could not detect the presence of the device. I am now thinking maybe the device is not supported by NI-VISA and so it will not be possible to use the Modbus Library with it.
2.) If the device is actually not compatible with NI-VISA, can DSC I/O server be used to read the information on the holding register?
3.) Do I need an intermediate device between a Modbus device and the PC to be able to read its holding register?
Please if anybody has got a good suggestion as to what to do to get my task achieved, kindly leave me a post.
Thanks
PETER

Error 107 having troubles communicating with adobe. How I fix!?

error 107 having troubles communicating with adobe. How I fix!?

Where are you choosing to download the install files too?

I'm having trouble communicating with a transducer (Keyence LS-3100 laser scan micrometer) via the serial port. It works in Hyperterminal. Any suggestions?

Its not a simple baud-rate or parity error. If I issue the command to send data (X1) in hyperterminal I start to get data. If I then switch to Labview I still get data. However if I try to issue the send-data command via Labview I get nothing (i.e. I can read from the device, but not write to it).
I am on a Windows 98 (version 2) PC, running Labview 5.1.1

Try adding a carraige return to the end of your command.
"djb" wrote in message news:[email protected]..
> I'm having trouble communicating with a transducer (Keyence LS-3100
> laser scan micrometer) via the serial port. It works in
> Hyperterminal. Any suggestions?
>
> Its not a simple baud-rate or parity error. If I issue the command to
> send data (X1) in hyperterminal I start to get data. If I then switch
> to Labview I still get data. However if I try to issue the send-data
> command via Labview I get nothing (i.e. I can read from the device,
> but not write to it).
> I am on a Windows 98 (version 2) PC, running Labview 5.1.1

How can I configure labview for communication with Modbus I/O?

i read a article about configureing Labview for communication with modbus I/O in NI developer zone, but it was written for Labview 6, how can I configure it with labview 7. it seems there are some difference. Thanks!

In both LabVIEW 6 and 7, you connect to modbus using Lookout Protocol Drivers (LPD) and then communicate to LPD using the tag engine of LabVIEW DSC or through DataSocket.

Having trouble communicating with ipod says software was not installed correctly and then asks if i want it repaired but couldnt need help

Having trouble communicating with i pod says software was not installed correctly and asks if i want it repaired but then says could not be repaired.Installed uninstalled numerous times but nothing dont know what else to do.

See the second box of Troubleshooting issues with iTunes for Windows updates.
tt2

Friend Recommendations: we're having trouble communicating with the game center server and are unable to turn on friend recommendations. Does anyone know how to fix this?

Friend Recommendations: we’re having trouble communicating with the game center server and are unable to turn on friend recommendations on our iPad. Does anyone know how to fix this?
we also get this error message when we try to connect the iPad to Facebook from the Candy Crush Saga game..... Failed: Sorry, you don’t have access to the Kingdom, right now. Please try connecting again later. anyone know how to fix this?

Welcome to AD!
I have a regular post for the top 3 or 4 fixes for that 9808 error. Obviously you are going to skip #1, since you've already tried it. Let me know how you get on with the next 2.
The top 3 fixes to itunes error 9808 seem to be
1) Go to Start > Control Panel > Internet Options > Advanced, make sure that SSL 3.0 is checked and TLS 1.0 is checked. Also under Security make sure that the “Check for server certificate revocation (requires restart)” is unchecked. Then click ok and fire up iTunes.
2) The culprit was Norton. The users are set up as Admin and Standard. I have Parental Controls turned on in both Vista as well as Norton. Admin users had no problems connecting to iTunes. Standard users would get the error. I had to go to Norton’s Personal Firewall and add the program “iTunes Helper.exe” and set the option to “Allowed” (”iTunes.exe should already be in the Allowed category.) in order for the standard users to be able to connect.
3) close iTunes if you have it open right now. Then go to C:/Documents and Settings/username/Local Settings/Application Data/Apple Computer/iTunes. Delete or cut the preferences.xml file which contains your iTunes preferences. Then go to C:/Documents and Settings/username/Application Data/Apple Computer/iTunes and delete or move the preferences.xml file. For Mac users, there is only one file you must delete or move a to a new location and is located at User > Library > Preferences > com.apple.itunes.plist. Restart iTunes and it will recreate those two (or one) files with the default settings. Feel free to set your preferences back to what they were and then connect to the iTunes store and enjoy!
And #4, see if you can get into the iTS from a different windows admin account on the same PC.

Modbus Communication, Adding shared variables, Licenses

Hello, I am having trouble communicating with a third party DAQ. I am receiving data from a thermocouple input module through a modbus library address but I recently purchased a digital I/O module which is giving me trouble. As soon as I add the shared variables which correspond to the modbus addresses of the digital I/O module channels I am using I get a few different errors. If I turn off aliasing for one of the thermocouple channels I get Error 1550 "the license for the I/O server type is invalid"....If I turn it back on I get errors for every modbus location saying "invalid value for enable aliasing option" I am using the student edition and on the opening screen it says the data logging license is expired. Is that the problem? I don't think so because I am successfully communicating with the thermocouple module of the same DAQ device. Is there a simple way to write a new VI that I can try to communicate with just a switch on the digital I/O module and see if it is reading on or off (0 or 1). Thank you very much for your time

Hi brade,
To clarify where we are at. the behavior you are seeing isn't expected. It is a minor bug that we have seen in R&D but haven't been able to reproduce and fix yet.
People have gotten around it by
1) re-making their projects
2) Enabling descriptions, as the engineer in other post. The problem went away for him on this post: "Aliasing is no longer an error. (As long as NI Variables (task description) is enabled)."
We were talking about the aliasing tab you can see on the modbus variables in hte labview project by right-clicking and going to properties;
I assume he checked the box on this tab:
Can you also post your project?
Jesse Dennis
Design Engineer
Erdos Miller

Could VBAI be use as Slave in ModBus communication ?

hello,
I'm working with VBAI 2010, in ModBus comunication I need to use VBAI as Slave.
I saw on help file that it is not possible but in menu "Tools\Communication device\" I can see "Vision Builder AI ModBus Adress :"
What does it mean ?
Is there any solution to use VBAI as slave in ModBus communication ?
Fabrice

Yes, Vision Builder AI can actually only be used as a Modbus slave for now (users can implement the master functionality using a Run LabVIEW step).
To configure Vision Builder AI as a Modbus Slave device, select Tools>>Communication Device Manager.
Click New Device, to create the Modbus Master Device you want Vision Builder AI to communicate with.
Give it a name, then select either the Modbus Serial or Modbus TCP as the communication protocol depending on the physical layer used to connect to your device. For serial, you will need to specify the port and Modbus Mode (the most widely implemented is RTU).
Click OK.
Click the Start Server button, next to the Modbus Server, to start the background task that will listen for incoming Modbus messages. Note that the Modbus registers will be updated asynchronously from your inspection, whenever a Modbus frame is received.
The Vision Builder AI Modbus Slave Address is only used to identify the device, when the protocol is Serial, and you use the RS-485 protocol to connect together more than 2 Modbus devices in a multi-device configuration. Ignore this control if you are using Modbus TCP.
We know this dialog is a little confusing and are working towards improving it in future releases.
Once the server is running, use the Modbus Slave step to read and write the Modbus registers (that are located on the machine running VBAI, since you configured VBAI as a slave device).
Make sure that you specify the correct address in your Modbus Master device configuration software for the register you want to access in Vision Builder AI. In most Modbus device configuration software, you must enter a name for the register you want to use. Per Modbus convention, the register address of the slave device is calculated by subtracting 1 from the register name that you specify in the master device configuration software. Vision Builder AI expects register addresses, not register names, so you may have to subtract 1 from the address you defined in the Modbus device configuration software. For example, a register name defined as 2 in your Modbus configuration device translates to register address 1 in the Vision Builder AI Holding Registers table.
Modbus Device
Holding Register Name = 2
Vision Builder AI
Holding Register Address = 1
The Modbus data model is based on a series of four tables: Discrete Inputs, Coils, Input Registers, and Holding Registers. These tables do not overlap in Vision Builder AI. Some Modbus devices use the following start addresses for these tables.
0x00000 for the Coils
0x10000 for the Discrete Inputs
0x30000 for the Input Registers
0x40000 for the Holding Registers
Because the tables do not overlap in Vision Builder AI, ignore the first digit of the start addresses when entering the addresses in Vision Builder AI. For example, a register name defined as 0x40000 in a Modbus configuration device translates to register address 0 in the Vision Builder AI Holding Registers table.
Modbus Device
Holding Register Name = 0x40000
Vision Builder AI
Holding Register Address = 0
Sometimes you need to subtract 1 from the register name that you specify in the master device configuration software and ignore the first digit of the start address to ensure proper register addressing. For example, a register name defined as 0x40008 in a Modbus configuration device translates to register address 7 in the Vision Builder AI Holding Registers table.
Modbus Device
Holding Register Name = 0x40008
Vision Builder AI
Holding Register Address = 7
The Modbus Local Registers Terminal accessible from the Tools menu is a useful tool to figure out where you're writing data.
Hope this will help you configure the communication between VBAI and your device easily.
Best regards,
-Christophe

485 modbus communication with Watlow PM trouble

Similar Messages

Maybe you are looking for