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] | + | =[http://azysijogen.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]= |
− | [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.rcp/org/rifidi/designer/services/core/cabling/CablingService.html javadoc]<br/> |
− | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPO.html GPO] | + | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPI.html GPI]<br/> |
− | The cabling service is used for GPIO events. | + | [http://www.rifidi.org/javadoc/designer/org.rifidi.designer.entities/org/rifidi/designer/entities/interfaces/GPO.html GPO]<br/> |
− | It provides facilities to add and remove cables. | + | The cabling service is used for GPIO events.<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. | + | It provides facilities to add and remove cables.<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.<br/> |
Revision as of 23:20, 23 November 2010
This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page
javadoc<br/> GPI<br/> GPO<br/> The cabling service is used for GPIO events.<br/> It provides facilities to add and remove cables.<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.<br/>