Hello Alist
Has anyone had any experience using AB TCP on a palm pilot or similiar device to make a wireless connection to an AB plc network?
Thanks, Mark Ray

 

First of all the Ethernet protocol that AB uses is not TCP it is called Ethernet IP. Using the Mobile Industrial Communicator (MOBIC) from Siemens Energy & Automation we were successful in pulling this off; however you need a bridge between the standard TCP/IP of the MOBIC and the Ethernet IP of the AB PLC. ProSoft has such a device for the AB PLC that they call Generic Ethernet module. It communicates with ASCII strings. Using embedded Visual Tools C++ you can create an application for the MOBIC that will convert the ASCII string into raw data over Winsock.

You can then create an HMI for the MOBIC using either embedded C++ of embedded Visual Basic. Embedded Visual Tools is downloadable from the Microsoft website. This tool comes with SDKs for the palm pilot. The MOBIC when purchased from Siemens comes with an SDK that can be used with embedded Visual Tools. A company in Las Vegas called ProTech has been successful with this approach and are currently deploying this application using the MOBIC.

http://www.sea.siemens.com/automat/product/wt/mob/aumobov.html

Ron Powers

 

CimQuest INGEAR offers Allen-Bradley OPC DA Servers for WIN CE 3.0 and pocketPC platforms.
Also provided are free OPC ActiveX controls for the iPAQ pocketPC that allow you to create HMI screens using eVB or eVC with virtually no programming.

http://www.plcdriver.com/abopcpocketpc.htm

The AB OPC Server Cross Plaform install includes everything you need. Download it and give it a try.

 

One small correction. Rockwell/Allen-Bradley uses EtherNet/IP, a specification controlled by ODVA (Open DeviceNet Vendors Association). It uses an Application layer called CIP (Control and Information Protocol) that is the same as for DeviceNet and ControlNet. CIP is mapped to TCP/IP for connection establishment and UDP/IP for secure deterministic data transfers.

I believe that Rockwell Software sells the software for RSView32 HMI that will run on a Pocket PC using Windows CE. It will also run on a PC server using Windows CE on a Pocket PC as a terminal server. Check this out at:

http://www.software.rockwell.com/rsviewstudio/adddoc.cfm

Dick Caro
============================================
Richard H. Caro, CEO
CMC Associates
2 Beth Circle, Acton, MA 01720
Tel: +1.978.635.9449 Mobile: +1.978.764.4728
Fax: +1.978.246.1270
E-mail: [email protected]
Web: http://www.CMC.us

 

Not necessarily Dick, Ethernet/IP can "encapsulate" a wide variety of protocols. Besides CIP, a large majority of Ethernet/IP products are actually moving DF1 or DH+-style "messages" in a psuedo-CIP Rockwell-specific object, plus there are several products that will encapsulate ASCII in Ethernet/IP to allow remote access to weight-scales and other ASCII products.

Go to an "Ethernet/IP Programming Workshop" and they'll even mention how even Modbus could be encapsulated in Ethernet/IP - ;^) I'm not sure why anyone would want to do that, but I can be done.

Best Regards

Lynn August Linse, [email protected]
IA Firmware Specialist, Digi Int'l (www.digi.com)

 

You are indeed correct, but isn't that what I said. Ethernet IP is not TCP/IP. If you are talking about the Mobile View Tablet T750. That is only for thin client applications. You still need a server connected to the process. The Mobile View Machine Terminal will run RSView locally but it is tethered. With the Siemens MOBIC there is no need for a server and it is true full VGA unlike the Mobile View Tablet.

 

Right you are Lynn. CIP is THE User Layer protocol contained in the EtherNet/IP specification. It also contains an Application Layer encapsulation protocol that can pass any message from any source. Obviously, this capability allows EtherNet/IP to be used to replace their older proprietary DH and DH+ protocols.

I just respond reactively when anyone says that Ethernet can be used as a network protocol for any automation project. Ethernet alone is an insufficient specification. Even adding TCP/IP is not enough. Foundation Fieldbus HSE, EtherNet/IP, Modbus/TCP, iDA, and ProfiNET are all more proper ways to specify the use of Ethernet. Thanks for giving me the stimulation to correct some of these errors I see a lot on the A-List.

Dick Caro
============================================
Richard H. Caro, CEO
CMC Associates
2 Beth Circle, Acton, MA 01720
Tel: +1.978.635.9449 Mobile: +1.978.764.4728
Fax: +1.978.246.1270
E-mail: [email protected]
Web: http://www.CMC.us
============================================