Invalid Fiber Couplers

Fiber Couplers are used to connect Fiber Inner Ducts in a Fiber Branch Enclosure. You can connect Fiber Inner Ducts using the Fiber Feature Editor by selecting the two Fiber Inner Ducts and choosing the ‘Couple’-icon :

Connecting Fiber Inner Ducts
Connecting Fiber Inner Ducts

This will connect the 2 selected Fiber Inner ducts using a Fiber Coupler. After coupling the Fiber Inner Ducts the picture looks like this :

Connected Inner Ducts
Connected Inner Ducts

The two selected Fiber Inner Ducts are now connected via a Fiber Coupler which you can see in Feature Explorer if you go to the connected features of one of the Fiber Inner Ducts :

Explorer feature in Fiber Feature Editor
Explore feature in Fiber Feature Editor
Explored feature in Feature Editor
Explored feature in Feature Editor

Fiber Couplers are only allowed to be connected to Fiber Inner Ducts and they can only exist in the system when they have a connection. The following Fiber Couplers are invalid :

  • Fiber Couplers with more then 2 connections
  • Fiber Couplers with a single connection
  • Fiber Couplers without a connection
  • Fiber Couplers connected to other features then Fiber Inner Ducts

The following AdHoc-query will display all Fiber Couplers with invalid connections :

with T as
(      
select 	4300 		g3e_fno
	,	a.g3e_fid
	,	4301 		g3e_cno
	,	1 			g3e_cid	
	,	count(*) 	cnt	 
	from gc_ne_connect a
		inner join gc_ne_connect b on ( (b.node1_id = a.node1_id) or ( b.node2_id = a.node1_id) )
			and b.g3e_fno != 4300
	where a.g3e_fno = 4300 
		and a.node1_id != 0 
		and a.node2_id != 0
		group by a.g3e_fid
UNION
select 4300	g3e_fno
	,	g3e_fid
    ,	4301 g3e_cno
    ,	1	g3e_cid
    , 0 cnd
    from gc_ne_connect
    where g3e_fno = 4300 
    and node1_id = 0 and node2_id = 0
)select g3e_fno
	,	g3e_fid
    ,	g3e_cno
    ,	g3e_cid
    ,	cnt from t 
    where cnt != 2
    order by cnt desc

The result looks like this :

invalid Fiber Couplers
invalid Fiber Couplers

Hope this helps, Stephan

Related Posts

Shortening CustomCommand development time by using a proxy

One of the most time-consuming processes when developing with Hexagon G/Technology is creating custom commands. The usual development approach consists of the following iterative process: During testing,…

Invoking Oracle Spatial from a Custom Command

Consider a requirement where the centroid of a set of points needs to be retrieved within a custom command. This can be achieved using the ‘GTDataProvider.DataContext.Execute‘-method:

Rubberbanding in G/Technology

Whenever a user is digitizing a polygon, he expects feedback when moving the cursor before actually adding a point, the system should ‘rubberband’ the position under the…

sample_set7

Sorting and merging geometries in Oracle Spatial

Consider a requirement where an unsorted set of geometries needs to be merged into a single geometry. Take for instance the following set of geometries where: a…

Fiber Cables

AdHoc Queries

Introduction G/Technology provides functionality to run dynamic queries, the so called ‘Ad-Hoc queries’. A Large telecom provider in the Netherlands is moving Fiber Cables from CRAMER to…

Leave a Reply

Your email address will not be published. Required fields are marked *