9 Replies Latest reply on Feb 17, 2017 4:35 PM by Tim Szekely

    Fiber Trace oddness

    David Meek

      A new issue has come up that we could use some assistance on.

       

      We were using a Transition Point feature to show the DMarc location on the side of a residence.  We have a few instances where the drop is multi-strand and branches at the DMarc with one strand going into the residence and another strand being spliced at that point and running to a second residence further on.  To map this I created a DMarc as a Splice Point feature.  When running a fiber trace with the new Splice Point DMarc in place I'm getting the following pop-up which terminates the trace without completing.

      SplicePoint NID error.jpg

       

      The screen-grab below shows the specific circumstance with the splice at the DMarc.  Also, I have four DMarcs in the trace, but I'm getting three repititions of the error in the message, not four.  Note that in each case the drop continues into the residence and terminates at a Device Point.

      Splicable NID layout .jpg

       

      This also keeps a fiber schematic from running properly.

       

      Thanks for your help on this.

       

      David

        • Re: Fiber Trace oddness
          Matt Lutgen

          This error message is from your newly placed splice point correct?   This is where the trace stops?

           

           

          Any additional messages in the Miner event log which occur after the fiber trace is run?

           

           

          Greg McHugh, Tim Szekely

            • Re: Fiber Trace oddness
              Tim Szekely

              Hi David,

               

              When you say you "created a DMarc as a Splice Point feature", is this just an additional subtype for the splice feature class or was there a configuration change to go with it?

               

              What was the workflow used to place the new subtype of splice, same as usual or was the cable feature already split at that location?

               

              I've seen this error when a feature with connections was moved/removed in some way that didn't clean-up the entries in the connection table that were originally associated with it, like when a riser was placed in one location, then disconnected and moved before being deleted, or when the "Fiber Object Deleted" AU accidentally became un-assigned to a feature class.

                • Re: Fiber Trace oddness
                  Elwyn Pratt

                  Thanks for your help on this. Just to add to David's comments below, Miner produces the following two attached messages whenever the error occurs.

                   

                  Some additional info:

                  - The "Fiber Object Deleted" AU is assigned as normal.

                  - As David mentioned, the trouble items in the FIBERCONNECTIONOBJECT table reference the wrong object as a container. This is true even when the original transition point is deleted and the neighboring fiber cables are disconnected / reconnected to the geometric network. Is there some way to "refresh" the container object?

                   

                  Miner1.PNGMiner2.PNG

              • Re: Fiber Trace oddness
                David Meek

                Elwyn's been testing and found that in replacing the old TransitionPoint DMarc with a SplicePoint DMarc if the new goes into the exact same location we are getting this error.  If the location for the replacement DMarc is not in the exact same spot things are working normally.  We're still working on permutations of this.

                 

                The new DMarc (Splice Point) is simply an additional subtype.  No configuration changes were made.

                 

                Using the disconnect tool on the old DMarc and then deleting it didn't help.

                • Re: Fiber Trace oddness
                  David Meek

                  A few questions.  Can we overwrite the old DMarc's Global ID in the CONTAINERGLOBALID field in the FIBERCONNECTIONOBJECT table with the new DMarc's Global ID?  Or are there other fields in other tables that need to be modified, also?  If that's not advisable, we have a workaround:

                   

                       delete old DMarc

                       delete fiber segment from old DMarc to Device

                       connect drop from building edge to Device

                       place new DMarc away from building edge

                       move new DMarc (and fiber endpoints) into place

                       build fiber connection in new DMarc

                   

                  but, is there a more elegant way (read faster) to do this?

                  • Re: Fiber Trace oddness
                    Tim Szekely

                    Hi David,

                     

                    Fixing the particular situation isn't going to be quite as simple as editing the fiber connection table unfortunately.  In certain situations this could work but there are a few cases where it will mess things up further instead, for example when the new connection container is a different type than the old one, i.e. your example here.  In general editing the fiber data tables directly isn't recommended.

                     

                    In theory, if all AU's were in place you should have been able to delete the old demarc (type of transition point) and drop in a new demarc (type of splice point) and then reconnect the cable segments (using Connection Manager) as all strands should have been disconnected (note that you couldn't put in another type of transition point e.g. old demarc and do this).  However it sounds like for whatever reason the old connections associated with the original feature didn't get removed, so they are still in the connection table messing up the traces. 

                     

                    The work-around you listed is probably about as good an option as any.  Somehow the old connections need to get cleaned-up, this can be done by either deleting the cable on one side of the old demarc (recommended method) or by deleting these entries directly from the fiber connection table (expert level tactic, beware this approach).  You can then place the demarc type derived from a splice at the spot of the old one and draw a new cable coming from it, then connect things up in the demarc using Connection Manager.

                     

                    Note that for the old-type of demarc (a subtype of transition point) you can't put a new one at the end of a cable; when placed it needs to split a cable.  If you need to move or remove an existing one, there is a page here that describes the process (rules are same as for risers):

                     

                    How To - Fiber Manager - Move a Riser That Has Been Placed at the Wrong Location

                     

                    If you can't get rid of those trace errors it may be best to submit a support ticket, we can go over how to clean up the obsolete connections to get the traces working again in a screen sharing session.

                     

                    Kind of a wordy description, hope I'm not confusing things more here...