Has anyone heard of / used the CompoNet protocol?

[AustralIan]

Whilst browsing the ODVA website, I came across CompoNet.

Has anyone heard of or even used this protocol before?

https://www.odva.org/Technology-Standards/CompoNet/Overview

In Australia, Compo is slang for "worker's compensation" which is money you receive from your employer's insurance company when you are injured at work.

 

[dmargineau]

I believe it is a high speed industrial communications CIP protocol similar to DeviceNet's Master/Slave hierarchy with Allocate/Release tokens for each transferred I/O packet; it also has a 'pre-allocated' data transfer methodology similar to the ControlNet 'scheduling', however, it has the capability to 'Release' connections which are no longer needed and has only a 'polled' type data exchange mechanism.

CompoNet is running on a proprietary physical layer.

9.3.4 of
https://books.google.com/books?id=p...HRSSB1wQ6AEIVTAJ#v=onepage&q=CompoNet&f=false

Omron is implementing it quite extensively; I have never personally been around any implementations though; most likely Ken did...

https://www.ia.omron.com/products/category/automation-systems/networks/componet/

 

[BryanG]

In the UK Compo is a character in the comedy 'Last of the Summer Wine'. Definitely not relevant.... but you started it.

 

[BobB]

It is basically an update to Omron's old CompoBus 2 wire remote system and has been made open and is administered by ODVA. It is fast, reliable and runs on a twisted pair. There is a heap of error checking built in and it is capable of explicit messaging although I do not know of a manufacturer that has implemented that at all. I have used it extensively for remote I/O control on Omron PLCs. It is also fast - 1000 digital I/O over 30 metres on a twisted pair update time is I believe 1 millisecond - faster that the PLC scan time usually. By the way the physical set up is far less demanding than DeviceNet and the system is no where near as fussy and cranky either.