Geek Answers Handbook

Any successful profibus messages from .NET?

Has anyone successfully spoken profibus from a .NET application?

If you did this, which device / card did you use to achieve this, which application, and did you use any existing or available code?

+6
communication plc industrial
source share
3 answers

We did not use Profibus, but used DeviceNET (another CAN-based protocol), Ethernet / IP and ControlNet , which all have similar problems.

We have been doing this since the end of 1990 and therefore rely mainly on our own generated code using off-the-shelf equipment. The companies that have shown longevity in the period that I remember are: -

  • AnyBus (HMS, www.anybus.com ), we recently started using our gateway products, since we can place fieldbus interfaces next to the equipment and then exchange data over regular Ethernet (usually using Ethernet / IP www.odva.org ). This has the advantage of separating hardware and PC using only a network cable. The Ethernet / IP.NET classes were written by us ourselves, because at that time there was nothing special on the market. Iā€™m sure a quick google search will find suitable class libraries.
  • SST ( www.mysst.com ) has had fieldbus interfaces for over a decade. The last SST card we used for DeviceNET still had only the VB6 sample code. A good selection of fieldbus support and various form factors, for example. PC104, PCI, PMCIA
  • Beckhoff / Wago ( www.beckhoff.com , www.wago.com ), we usually use Beckhoff for I / O more than interface cards, but again a company that has existed for a long time. They also have products that support OPC browsing (another way to get I / O information without directly communicating with hardware / devicedrivers).

I suggest not using the OPC interfaces directly on the equipment (its OK for communication using PC (.NET) ā†’ PLC-> Profibus), since you need to make sure that the control system responds to loss of control from your .NET application, I assume that you need a Profibus master here (and not a slave), so if your control system is completely fail-safe, then a loss of communication should mean that the control system goes into an "idle" state and therefore most of the I / O will return to a safe state.

We also try to ensure that we do not put security code in .NET. Most of our .NET code is the user interface from the PLC, but in some places we directly control the field bus, but we guarantee that hardware locks will prevent trouble-free operation, either using safety switches / relays or a small PLC with the task of only locking, And, before just make the system fault tolerant! Losing commits from .NET code should disable automation to a security state.

+7
source share

We used Steeplechase to connect our Profibus to our automated selection system.

http://www.phoenixcontact.com/automation/32131_31909.htm

+2
source share

Try the following: http://libnodave.sourceforge.net

+1
source share

More articles:


All Articles