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!"

Similar Messages

Modbus (RS485) and Automation Direct GS2 Example

I am looking to see if anyone has used the Automation Direct GS2 Drive and LabView and has a workign VI? I have been looking over Modbus over RS485 that the GS2 uses and I have looked at the Modbus .vi library. Correlating all that into one cohesive thought seems to be escaping me. I am new to LabView and never seen Modbus before and I have a very short schedule to get something going. Even if all the .vi did was start and stop the motor I would be happy. Then I could work the rest out.
GS2 Manuals
Solved!
Go to Solution.

That was a better explanation then the other info I was looking at as far as address and commands. I at least have the drive displaying an error. Yesterday it just sat there and showed 00 on the drive display. Sometimes it is the little victories. I am also getting error codes back from the drive which is some sign of life, the drive displays error 03 and my vi displays a 03 when it errors out.
From the manual:
error 03: Communications Warning: Illegal data value - The data value received in the command message is not available for AC drive.
But now for the continuing headaches.
I have tried to read the firmware version using the command/address you talked about with no success. I guess I would be even happy with that to work. The vi does not accept an address of 091B (run) it will not accept the "B" of the hex number.
So for run:
Description Hexadecimal Modbus Decimal Octal
Serial Com Run 091B 42332 4433
This implies a Read Input Register command 4 to Hex address 091B? Looking at the Modbus intro I see the code 4 in table 2 aka the read Input register. I would say that is just to read the status of the run register. 00-Stop, 01-Run. So what does that corespond to writing to the register 62332?
Attachments:
GS2 Control.vi ‏13 KB

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

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

Modbus TCP with Beckhoff (Wago)

Hi,
I'm looking for examples/how to/lib/dll to build a communication to a Beckhoff BK9000(similar to Wago 750) which have a Ethernet - Modbus TCP Option.
I'm able to write via LabVIEW-TCP-Functions but only once after powering on and the result/answer is more confusing.
For the lookout OPC variant i heared there is still some additional software needed - true? or is it possible to set up the communication with lookout OPC without third party driver?
Thanks for any help
Hans

Hi JAMR,
There are plenty of examples that setup up the tcp server communications. If you open up the NI Example Finder and double click on the Networking Folder (under the Browse tab). You can then select the TCP & UDP folder and find several examples that use TCP. Also, there is a great knowledge-base article that provides information about network communication with TCP/IP messaging protocol. Essentially, what you are going to want to do is establish basic connectivity between the computer and the device and then assign the device an IP address. Before you do anything with the driver for the device, you might try to ping the device first. Once you can get this working, then you can set up the TCP/IP communication. I hope this helps!
Carla
National Instruments
Applications Engineer

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

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.

Direct communication with SIEMENS PLC

I am trying to establish a direct connection with a SIEMENS S7 PLC. I donot want to use any card or profibus etc. I want to do it through the Serial Port.
I have used the IA server kit when communicating with SIEMENS S5 for which I used AS511 protocol. I would like to know if there is any such protocol for S7.
Please Help!!

Hi.
I'll try explain it.
All Simatic S5 PLc's processors (CPU90 ,CPU100) have got serial (current loop converted to RS232) physical inteface as standard.
You can program PLC's or communicate with its by AS511 protocol.
S7 Simatics processors (CPU 3xx, CPU4xx) haven't got RS232 interface as standard. RS 232 interface occurs in forms of interface module connected to the rail (slot) and doesn't serve any protocol (simple chracters exchange).
You can program PLC, observe/modify I/O, variables, etc. only by standard RS485 interface using protocols MPI or PROFIBUS (PPI/MPI for Simatic S7-2xx CPU's).
You can try exchange data between Labview and S7 PLC by serial in characters form, but it is very difficult and inconvenient (you have to w
rite own driver for Labview and program for S7).
Another solutions:
1.PROFIBUS card for PC with drivers for Labview (I don't know if they exist)
2.connection thru OPC server (PLC->PC by PROFIBUS card->OPC server->Labview by Datasocket)
I think second solution is more comfortable.
See also:
Connecting LabVIEW to an OPC Server through a DataSocket Connection
Regards.
Romek.

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

Using modbus/TCP with USB ethernet adapters

I have a test stand where I have a handful of USB instruments and a single modbus/TCP slave. I'm considering adding a USB ethernet adapter to the stand so that there is a single USB cable connecting the computer to the hardware rather than both a USB and an ethernet connection. Does anybody out there have experience (good or bad) using USB ethernet adapters with modbus/TCP slaves?
The existing USB instruments all use ASCII/SCPI-style command sets. The Modbus/TCP slave is an Automation Direct EBC-100. Nothing high-bandwidth or low-latency. Basically, the computer issues no more than a handful or command or request (ether SCPI or Modbus/TCP) per minute.
Mark Moss
Electrical Validation Engineer
GHSP

Adam G wrote:
Hello Mark,
I was wondering what NI hardware you are going to be using in your application? Also are you going to be using LabVIEW for the programming? Have a great day!
Best Regards,
Adam G
The test software is written in LabVIEW, and the test stand uses M-Series cards for data acquisition.
Mark Moss

"The software required for communicating with the iPod is not installed..."

I realize my explanation of my problem is long-winded, so if you want a shortened version, here it is:
I've followed all the instructions trying nearly everything, and no matter what I do, iTunes gives me the error saying: "The software required for communicating with the iPod is not installed correctly. Please reinstall iTunes to install the iPod's software." My G5 iPod (60GB) works on two other computers (both without any music on them), so I assume there something wrong with my computer and not the iPod itself.
Now for the long-winded story of the last eight hours of my life...
I just got the Generation-5 iPod Video (60GB) a today and I'm having problems already. I followed the instructions and installed the iPod software and then plugged in my iPod (iTunes has been on my computer for a while now). I was expecting iTunes to open after plugging in the iPod, but my device manager only detected and installed "a new device". I manually opened iTunes and got an error saying: "The software required for communicating with the iPod is not installed correctly. Please reinstall iTunes to install the iPod's software."
After re-installing the iPod software and iTunes, and restarting my computer countless times, I came looking for help here. I found this page, which seemed to outline my problem exactly. My computer recognizes the iPod as a drive, but iTunes won't have anything to do with it. I have all the symptoms outlined in the heading, so I hoped to solve my problem there. I followed the instructions step-by-step, and after the final restart, I open iTunes to get the same exact error message.
I decided to determine whether there was a problem with my iPod or if it was my computer. I plugged my iPod into my uncles's powerbook, and got to the point where I can name and configure my iPod. I expected it to work flawlessly on a Mac (which it did) but there is no way for me to continue using a Mac (after tomorrow) for my iPod. This formatted the iPod for a Mac, so I went to another (different from the original) Windows computer, clean of any iTunes and iPod software, and followed the instructions exactly as they're supposed to be followed. After the installations, I plugged in my iPod, and although iTunes didn't open, I was able to format back to Windows and name my iPod (a step in the right direction). I should note that my (anti-iPod) computer is a Windows XP Pro, and the working one is Windows XP Home Edition. This was all well and good, until I remembered there was no music on this computer. So my iPod is completely working there, but there isn't anything I can do with it.
Next, I came back here and browsed around the discussion boards, hoping to find somebody with a similar problem to mine. There seems to be alot of errors concerning iTunes not recognizing the iPod, but none of the solutions I tried worked for me, including changing the drive letter. I get the "iPod Service Error" while trying to restore to factory settings through iPod updater.
Of course, I could transfer all 32GB of music from one computer to another, but the second (working) computer isn't mine and I won't have access to it in a couple months. It would be most convenient if I could get my iPod working on my own computer. Any help would be appreciated, especially from somebody who has solved this problem or know how to solve this problem.
P.S.
Here are some other minor details that my be important, but I didn't feel they were worth including.
- My brother has his iPod mini set up on my computer, under a different user login. He gets the same error once in a while, but re-installing iTunes always solves the problem for him. I had him try solving my problem his way, but nothing worked for him either.
- My computer is an AMD Athlon 64 Processor 3200+, 512MB RAM with Windows XP Pro SP2 installed. My internal hard drive is partitioned, using the letters C, D and H (C being my system files, D used for recovery files and H for my applications and games). My E drive is used as a DVD/CD-ROM Drive, and drives F and G are reserved for virtual drives (none have been running during this entire ordeal). My external hard drive uses the letter I, and I manually set my iPod to use the letter J (I've never used 'J' for anything else before).
- Yes, I have downloaded and installed the latest versions of iTunes and the iPod software.
- I'm assuming there is a problem with my computer and not my iPod, since it worked on both other computers I tried. I'm hoping it's as simple as changing a registry file or cleaning out (yet another) temp directory.

Solution to "Software required for communicating with the iPod is not installed"!
I battled this same problem for about 5 hours. Going through re-installations, the "5 R's", all these discussion boards. Nothing worked.
The problem is that iPodService was repeatedly crashing after minute or so. You can verify this by hitting Ctrl-Alt-Delete and noting that iPodService is missing from the process list (sort by image name), or by right-clicking on My Computer and selecting "Manage", then going to Services and checking out the IPodService service - if it gives you the option to "Start", then it's not running.
Here is what worked.
1. De-install iTunes and iPod (if you have the updater installed) completely by going to Start --> Control Panel --> Add/Remove Programs. Also delete the C:\Program Files\iTunes and c:\Progam Files\iPod\bin directories. (Don't worry, this doesn't affect your saved music files.)
2. Log in as an Administrator
3. Go into the registry (note this is dangerous - you should be careful) and remove the iPod entries that the uninstaller misses.
3.1 Go to Start menu --> Run.
3.2 Type in "regedit".
3.3 Go to HKEYCLASSESROOT --> IPodService.iPodManager.
There are two keys here, iPodManager and iPodManager.1. In my case, I did not have permission to view either of these. I think this is the root cause of the problem. I think the installer can't properly update these because it doesn't have permission. So you need to change the permissions:
3.4 Right-click on IPodService.IPodManager
3.4.1 Select "Permissions..." A warning will appear saying you don't have permission, but that you can change permissions.
3.4.2 On the window that launches, click on "Advanced..."
3.4.3 Click on the "Owner" tab.
3.4.4 Select a valid account (the one you're logged in under) under "Change Owner To".
3.4.5 Hit "OK".
3.4.6 Back on the main Permissions window, hit Add and add the same account as a valid user.
3.4.6.1 Where it says "Enter the object names to select", type in the account name, e.g. "Smith".
3.4.7 Click on the "Allow" checkboxes for "Full Control" and "Read".
3.4.8 Hit "OK".
3.5 Repeat procedure for the "iPodManager.1" key.
3.6 Now right-click and delete both of these keys.
I think that's all that's required, but I also searched through the registry and deleted the following keys.
4. Other keys I deleted:
4.1 HKEYCLASSESROOT --> IPodManager.IPodManagerUI.1
4.2 HKEYLOCALMACHINE --> SOFTWARE --> Apple Computer Inc. --> iPod
I think that's all I deleted, but I'm not positive. I seached for instances of "ipod" using the Find... and Find Next functions under the Edit menu.
5. Exit out of the registry editor.
6. Re-install iTunes. I re-installed iTunes and reconnected the iPod, and everything worked.
I want to repeat that editing the registry can completely mess up your computer if you modify the wrong things, so only do this if you're comfortable, and be extremely careful.
Hopefully this helps!
Apple support people: assuming this works, please add it to your solutions page, and feel free to reimburse me for spending half of Christmas figuring this out.
Mark

There is a problem communicating with the printer.

I have a Lexmark Interpret S405. I am using a MBP laptop with WiFi, running 10.5.8. I have a cabled (non-wifi) Linsys router. I am using an Airport Express.
I was finally able to get the WiFi light on the Lexmark to be static green after reinstalling the Lexmark WiFi setup and reconfiguring my Airport settings so that both the computer and printer see each other.
In fact, I even updated the driver from Lexmark's Web site last night and I watched the WiFi light on the printer blink green indicating that the installation of the driver update was being communicated to the printer.
However, when I print, it opens the print window and says first "Looking for S300-S400", then it says "Printer is now online". Then after about 10 seconds, I get this error: "There is a problem communicating with the printer. Make sure the printer is powered on and connected to the computer. Delete or hold the job and try again."
I've exhausted Lexmark's technical databases and couldn't find the answer here.
I've read that one possible solution was to delete all the printers from the "Print & Fax" system preferences window and re-add. That didn't work.
Lexmark says for: The printer communicating on a network; however, the printer is not responsive. Possible causes could be:
1. Your printer is associated with a network, router, or access point, but it is not your network.
2. A software process is blocked by a system security firewall preventing network communication.
3. You are logged into Virtual Private Network (VPN).
4. You are connected to a network but have decided to switch to a USB connection.
I don't have a VPN and have removed the USB cable, then restarted both printer and computer, and deleted printers in Sys Prefs, restarted, and still no solution.
I can print directly via USB cable, but want to print wirelessly.
Lexmark also says to enter my PIN (which I have pulled out from the print menu screen on the printer) in the System. That tells me a lot...
Network settings on the print window on the printer also tell me Signal strength is 5 (excellent) and that I am on the network my airport is on.
Message was edited by: Macman17

I bet this is too late but...
Are you trying to print through the airport express wirelessly or the built in wireless of the lexmark? If you want to use the airport express, there is no need to mess with the wireless printing on the lexmark at all. The airport express will be easy to set up, all the wireless setups through the printers are a pain.

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

Modbus communication with an automation direct GS2 AC Drive

Similar Messages

Maybe you are looking for