Difference between revisions of "CablingService"
From RifidiWiki
| Line 1: | Line 1: | ||
| − | + | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.rcp/org/rifidi/designer/services/core/cabling/CablingService.html javadoc]<br/> | |
| − | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.rcp/org/rifidi/designer/services/core/cabling/CablingService.html javadoc] | + | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPI.html GPI]<br/> |
| − | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPI.html GPI] | + | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPO.html GPO]<br/> |
| − | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPO.html GPO] | + | The cabling service is used for GPIO events.<br/> |
| − | The cabling service is used for GPIO events. | + | It provides facilities to add and remove cables.<br/> |
| − | It provides facilities to add and remove cables. | + | The reason why we don't allow a direct connection between a GPO and a GPI is that we want to be able to monitor and record events between these.<br/> |
| − | The reason why we don't allow a direct connection between a GPO and a GPI is that we want to be able to monitor and record events between these. | + | |
Latest revision as of 19:42, 26 November 2010
javadoc
GPI
GPO
The cabling service is used for GPIO events.
It provides facilities to add and remove cables.
The reason why we don't allow a direct connection between a GPO and a GPI is that we want to be able to monitor and record events between these.
