12-06-2010 07:06 AM
Hi Adam,
I, too, am building a dyno using LabVIEW and a PowerFlex 700S. I have it working using the CIP read and write commands. Please email me directly and I will help you get started.
Regards,
Kevin
12-27-2010 03:58 PM
Hello experts,
I'm developing a driver to communicate with an Allen Bradley ControlLogix.
I read about the "bool array behaviour" in this thread.
I have a question: Does all arrays (of every possible datatype) in structures (user defined types) are aligned on 32-bit boundaries?
It is a new conclusion during developing my software. It does not fit into my exisitng results ...
Does anybody know?
Or is there a document in the www ... to read more about alignement/boundaries?
Thanks for help.
Labinger
12-28-2010 09:19 AM
labinger wrote:
Hello experts,
I'm developing a driver to communicate with an Allen Bradley ControlLogix.
I read about the "bool array behaviour" in this thread.I have a question: Does all arrays (of every possible datatype) in structures (user defined types) are aligned on 32-bit boundaries?
It is a new conclusion during developing my software. It does not fit into my exisitng results ...
Does anybody know?
Or is there a document in the www ... to read more about alignement/boundaries?Thanks for help.
Labinger
Hi Labinger,
Check out this document:
http://www.rockwellautomation.com/enabled/pdf/TypeEncode_CIPRW.pdf
Eric
12-28-2010 03:52 PM
Hi Eric,
thank you very much!!!
All information I was looking for ... !
Regards
Labinger
01-10-2011 09:29 AM
Hi Eric,
I am trying to connect to a servo drive from Rexroth with the get/set attributes. Recieving feedback from the servo drive is not a problem, but sending commands to the servo drive seems to be a problem. I don't have any errors in Labview, but no commands are recieved from Labview. I know that the Rexroth servo drive only recieves commands from the Scanner with point-to-point, but the servo drive sends with multicast back to the Scanner. It seems to me that the get/set attribute VIs only are developed for multicast transport type - is that correct?
Best regards,
Thomas
04-08-2011 11:37 AM
Eric,
One of my associates was trying to get the demo project working with a ControlLogix PLC and has been getting the "bad class" response from the PLC when trying to establish the connection. I looked at the setup she's using, which appears to be the demo project exactly and her PLC configuration matches the example provided in the driver help. I can't see an issue with it, but in an effort to try and figure it out I fired up my previously working Logix 5000 project and LabVIEW (albeit slightly modified) demo project. I am now getting the same error message, Bad Class. The assembly instances, sizes, etc. are correct in the PLC based on what is setup in LabVIEW.
The only thing that is different about my system now than the last time I played with this in January is that I've updated to Service Pack 1 of LabVIEW 2010 (32 bit). Has the driver been used with SP1 with no issues as far as you know? I'm at something of a loss about this. Thanks.
Jeff
05-03-2011 11:30 AM
Hi Eric,
This is my first post and I am very new in Labview. Please let me know if anything i am wrong.
My system: Allen-Bradley SLC5/05 1747-L553 Ethernet Processor
Individual PC: Rockwell software RSView32 HMI
Since i don't want to make any changes for that PC, I plan to write a labview program in another laptop computer and connect to the hub to collect running data. Here is the problem i encountered. I can get readings from file types like "Integer" and "Floating Point". But I don't understand why i could not get readings form "Output" file type. Following is the data table memroy map from 1747-L553 processor.
File #Elements File Type
O0 42 Output
I1 33 Input
S2 83 Status
B3 32 Binary
T4 155 Timer
C5 104 Counter
R6 1 Control
N7 221 Integer
F8 204 Floating Point
F9 240 Floating Point
F10 240 Floating Point
.........
.........
E/IP SLC500 read icon have 4 options: Integer(N), Float(F), Bit(B), and Raw. I can choose "Integer(N)" to read "integer" file type and "Float(F)" to read "Floating point" file type with no problem. I assume i should choose "Raw" to read "Output" and "Input" file type. But when i did that, i just got some readings that looked totally unlated or didn't match readings from data table memory map. Does anyone know what the settings should be? How can i read the rest of other file types? Thank you very much in advanced.
CK
08-11-2011 03:17 PM
I just upgraded my application to LabVIEW 2011, and noticed the Ethernet/IP VIs are broken. The session ID will no longer coerce into the session input on the call library function node. How should I fix this, or is there a 2011 version of the Ethernet/IP library available?
10-20-2011 12:43 PM
How can I read outputs and write to inputs of a an Ethernet/IP device using the NI Ethernet/IP drivers?
I recently get the NI Ethernet/IP driver from NI in order to communicate with a Fanuc LR Mate 200iC robot using this communication protocol. Actually, I configure the robot as an adapter setting up digital input 1 to 64 and digital output 1 to 64 through the Ethernet/IP configuration.
What I need to do is for example, in determined moment of my logic I have to know the status of an output of the Fanuc Robot to take some action, or give an input to the Fanuc Robot so this do some operations. Now, as I mention before, I get this drivers recently and apparently they are new in NI so the regular technical support do not give support to this product. Basically there is no documentation appart from the LabVIEW help about this drivers, and this help doesn't help too much really.
So, if anyone can help me to make this work I will really appreciate it a lot. I am in the middle of a project that we showd integrate using Ethernet/IP.
I am using LabVIEW 2011 with the Ethernet/IP v1.2 drivers in a Windows 7 Professional computer
Again, any help with this matter will be really appreciated. Thanks.
10-31-2011 12:45 PM
I am interested in an evaluation of the EtherNet/IP software for use on a windows target and a cRIO target. Is that available?
Thanks,
Casey