Member Login
Search
Past & Future Posts
Sponsored Communities
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Cool stuff
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
The sooner our happiness together begins, the longer it will last.
-- Miramanee, "The Paradise Syndrome", stardate 4842.6
-- Miramanee, "The Paradise Syndrome", stardate 4842.6
RSS Feed
www.control.com/rss
from the Allen Bradley/Label guru required! department...
Ethernet messaging to labellerHi Everyone, First post so go easy!
I have been given a nice little project that includes creating full pallet labels via three automatic 'Logopak' pallet labellers.
I have an existing PLC5/80 ethernet processor, that I was hoping to use to send several flat strings including the required fields of data for the label.
However,I have now found out that although the labeller has an ethernet 'CommServer' (that basically converts from ethernet to RS232), this device uses Winsock port 8000.
I have contacted some resources who think that direct comms (i.e not using VB) would not be possible, although others have had contrasting views (although no actual solutions. :-) )
The manufacturer told us that ethernet communication was possible from the PLC, but seem a little less sure of late!
I have noticed that in the Logix5 MSG instruction, there is provision for an IP address, but nothing for a port number, so I am not too sure how to set this part up.
Any help would be greatly appreciated.
I have been given a nice little project that includes creating full pallet labels via three automatic 'Logopak' pallet labellers.
I have an existing PLC5/80 ethernet processor, that I was hoping to use to send several flat strings including the required fields of data for the label.
However,I have now found out that although the labeller has an ethernet 'CommServer' (that basically converts from ethernet to RS232), this device uses Winsock port 8000.
I have contacted some resources who think that direct comms (i.e not using VB) would not be possible, although others have had contrasting views (although no actual solutions. :-) )
The manufacturer told us that ethernet communication was possible from the PLC, but seem a little less sure of late!
I have noticed that in the Logix5 MSG instruction, there is provision for an IP address, but nothing for a port number, so I am not too sure how to set this part up.
Any help would be greatly appreciated.
Not really understanding your project details but have the following suggestion: Look at the MARC Omnii-Comm module that supports Ethernet
communication as well as ASCII communication http://www.miille.com/266-P00-Ethernet.pdf .
This module can convert ASCII strings to data that can be accessed using standard PLC messaging.
You may contact me directly at jmiille at miille.com.
communication as well as ASCII communication http://www.miille.com/266-P00-Ethernet.pdf .
This module can convert ASCII strings to data that can be accessed using standard PLC messaging.
You may contact me directly at jmiille at miille.com.
Hi Jerry,
Thanks for the advice, the 4 port version of this looks as though it will do the job. If I understand this, the PLC Message instruction would target the IP of the Omnii Com module. How would I then discriminate between each of the 3 serial devices connected?
Thanks,
Ian
Thanks for the advice, the 4 port version of this looks as though it will do the job. If I understand this, the PLC Message instruction would target the IP of the Omnii Com module. How would I then discriminate between each of the 3 serial devices connected?
Thanks,
Ian
Hi there,
I agree with Jerry that what you need is a converter.
Here is another one:
http://www.anybus.com/support/support.asp?PID=110&ProductType= Anybus%20Communicator
If you have any questions regarding this product, let me know.
Pat
support@hms.se
I agree with Jerry that what you need is a converter.
Here is another one:
http://www.anybus.com/support/support.asp?PID=110&ProductType= Anybus%20Communicator
If you have any questions regarding this product, let me know.
Pat
support@hms.se
From Control Engineering magazine...
Related articles from Control Engineering magazine- OPC: Painless migration, classic OPC DA to OPC UA, partership
- Easier: panel designs, short-circuit current rating compliance
- MechatronicsZone road show kicks off
- Partnership: Advanced, interoperable motion control, machine tools
- Protect intellectual property: Encrypt firmware, control code
- Portable computing: Operators can be mobile with rugged HMI
- Whitepaper: Small form factor HMIs evolve
- Remote control: Get behind firewalls—securely
- Report asks: Will DIN-rail PCs with I/O revolutionize industrial PCs?
Above articles copyright 2008 Reed Business Information. Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Users of this site are benefiting from open source technologies, including PHP, PostgreSQL and Apache. Be happy.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!



