OSPInSight OSPM-ViewLite 6.07 Release Notes

NEW FEATURES

1- ViewLite is a basic version of OSPInSight Outside Plant Manager, with the ability to view maps, label, perform find routes, see splice schematics, and create markup layers, among a few other features. It costs less than OSPM-Edit or OSPM-View

Tips

1- Adobe Acrobat reader (or something else that can read a .pdf file) must be installed in order to use the Training Manual, which can be accessed via the Help dropdown menu. Note that the Training Manual is specifically written for OSPM-View. Simply skip the parts pertaining to lists, reports and other features not included in OSPM-ViewLite.

KNOWN ISSUES

1- Alt+o does not pull down the 'Options' dropdown menu

2- When printing the map from View with MapPoint as the background, the printout is dark. Also, the print form takes a long time to close

OSPInSight OSPM-View 6.07 Release Notes

NEW FEATURES

1- Print Options have been added to the Taper report, so now instead of only having the option of printing through Crystal Reports, you can also print to a generic grid or export all the data to a TAB-delimited text file (which you can then open in MS Excel, or other applications).

2- A Plant Layers tab has been added to the display options, so that users can specify which layers they would like to have visible or invisible when loading a network, without adding them to a workspace.

3- The Display Options->More tab has had an additional column added to it, so that users can now see both the display captions and the database field names simultaneously.

4- Case sensitivity for user names has been dropped

ERRORS RESOLVED

1-Labeling database objects (buildings, access points etc.) with the getinfo tool where one the fields being labelled had a null value caused an error.

2- Mapping Rings (Terminations) from the Relationships window would give a 'no items selected' message, and not map the ring

3- Grouping the Ring (Terminations) by any field, then finding relations for a frame or span or termination in the treeview related to any Ring(Termination) gave an index out of bounds error.

4- Select getinfo tool, click an enclosure, when it asks if you would like to label splicing, select another application that is running...then switch back to OSPInSight: Run-Time Error was generated, and the application would crash.

5- Printing from the fiber panel would give incorrect Status values

6- An aggregate function error occurred if you selected EA1 as the 'Display field' for "Ring (Terminations)" In Options->Display Options, on the Treeview tab

7- In the Lit fiber length report, there was a math error when you switched units

8- Attempting to map a document from the treeview generated a "Object variable or With block variable not set" error. Now the associated database objects are mapped sequentially.

9- When opening the lists a “disconnected from client” error or "Automation error The object invoked has disconnected from its clients"would frequently appear. OSPInSight will re-establish the database connection now.

KNOWN ISSUES

1- When printing the map from View with MapPoint as the background, the printout is dark. Also, the print form takes a long time to close

2- Some forms when closed return focus to a different application, other than OSPInSight. It is necessary to re-select OSPInSight

3- When using Microsoft Mappoint as the background, the Back and Forward functions on the map don't always work the first time

Solution: Sometimes the Back & Forward entries on the right-click menu must be clicked twice to do anything

4- Any Equipment records that have an invalid TypeID value (such as 'none' when that is not in the TypeID list) will not show up in the "Customers/Equipment Report".

Solution: If you suspect that the report is not displaying all of your customers or equipment, open your Equipment List or Equipment/Customer Editor in OSPM-Edit and update the TypeID values such that they all correspond with an entry from the TypeID list (from the Hardware/Materials Editor)

6- Currently in the schematics, the Span/LocateID text dynamically resizes to fit the "span" field and not overrun the "fiber" field. However, it still isn't perfect, and depending on how big the form is, it will still run into the next column a little.

Solution: If there is some text overlap, simply resize the form until the text in the span column is not conflicting with the text in the fiber column.

7- When using MapPoint as a background (or when any Raster image is loaded in MapX), zooming in past 0.1 miles will typically invert the mapper. Labeling will also behave oddly at this zoom level with any raster images displayed.

Solution: There is currently no known resolution to this issue.

8- Sometimes you will see odd window/column behavior in the Ductbank Cross section form.

Solution: Reset the layout for that form.

OSPInSight OSPM-View 6.06 Release Notes

07/Feb/05

NEW FEATURES

1- The Route highlight has been moved from the animosp layer to a new layer called 'mapping', allowing users to click objects, open editors, map items, etc. without losing route or cable highlights. By default the route/line highlight is yellow, however this can be changed. Open your layer control, select the "Mapping" layer, click "Display", and change the Style Override to be the color, thickness and line-style you want for your route highlight. To save this change for other sessions, exit your layer control, click the Options->Display Options dropdown, and on the Treeview tab, click the "Save Highlight Style" button.

2- The Setup form has been updated to make its use more intuitive

TIPS

1- Sometimes lists can have problematic display characteristics. For example, if your "Types of Enclosures" list is opening with colors that make it difficult or impossible to read (such as black text on black background), simply reset the layout for that list. To do so, open the Display options by clicking Options->Display Options, then click the Layout tab. Find the checkbox for the "Enclosure Types" list, check it, then click the "Reset Layouts" button. Use this form to reset the layout of lists, reports or editors that have similar problems.

2- After installing OSPInSight, if you are unable to drag the map to the right or down with a polyline (cable or duct object) but are able to do so to the left or up, simply resize, then maximize the application. Finally, press ctrl+q to save that setting.

3- If you are required to enter a password to get into your setup but would like to remove it, the setup password can be disabled by clicking the "Choose Setup.mdb or Admin.mdb" button in the setup, then clicking the "Change Password" button, and selecting "OK" while the form is still blank.

ERRORS RESOLVED

1- The End Point schematic was displaying incorrect SpanID's.

2- Selecting map objects on the DOC layer with the GetInfo tool would highlight incorrect documents in the treeview, or generate an error stating 'could not find item'

3- The 'Change View' form wasn't opening when selected from the Map dropdown menu

4- The Legend and Port colors for the Fiber Panel Graphic tab are working.

5- Displaying the LocateID in the Endpoint Schematic was not very legible. It has been improved but you still might see some overlay. See Known Issue #6 below

6- The 'ea6' field was not included in the default query for the Building List

7- Using the Enclosure tool to replace a slack with an enclosure when there was another slack object nearby would cause both slacks to be deleted, rather than only the one that was clicked

8- Hardware Materials Editor, Reelid was not updating in Oracle networks

9- Open a fiber panel with terminations, click the "Edit On" button, then click the 'Reserve' button in the notes section. In the "Reserve Current Jack" form, click the Initiator dropdown, then select 'Edit Items'. A "Run-time error '383'" used to appear, and then the application crashed

10- Updating values in the lists that had more than ~32,768 records would generate overflow errors

11- The Display Options->Autozoom option was affecting the Fiber Panel->Find Route function, whereas they are now completely independent. The Find Route options now determine the find route mapping

12- When running an SQL Query on a MapInfo table and viewing the results as a table called SELECTION, sometimes SELECTION was not an option in the Browse Table window. Also, if SELECTION was available, using the scroll bar in it would cause the list to go blank

13- Deleting a Frame with related terminations is now a more straightforward. Also, orphan termination records will not be left in the list

14- Midsheathing (splitting) a cable that loops over itself with an enclosure or slack loop would cause graphical distortion

15- Copper cables with a placement of 'underground' were not being created with the correct style, based on the Default style entered

16- Patch editing in Fiber Panel updated only one side of the patch. It will now update both sides of the patch

17- In the Schematics, the Print Setup button was not working. The VBPrnDlg.dll had to be placed in the system32 directory and registered

18- LocateID value was displaying incorrectly in the Splice Key editor

19- Colons ( : ) have been restricted as input in the Group field for terminations as well as the Equipment ID field for equipment. Colons are used as delimiters and can cause errors in some circumstances if they are present. Colon values have been handled in the Treeview...if you select a group with a colon in it you will no longer receive a syntax error.

20- While a network is opening if the File menu was clicked an error message appeared: Index out of bounds

21- Mapping from the Treeview would unnecessarily refresh the layers, as would using the GetInfo tool

22- Labeling MapInfo Document objects from the Treeview was displaying incorrect fields. Using the GetInfo tool wasn't labeling at all

23- Reordering lists by a column would reset the horizontal scroll bar back to the left, forcing the user to relocate the column

24- Labeling slack loops with the getinfo tool would change the zoom level and view area, and would not label correctly

25- If a user opened a fiber panel, made the form wider and closed it without saving the layout, then the next time it opened the columns would be incorrectly sized

26- The Taper Report's layout was not resetting correctly when Options->Display Options->Layout->Taper Report was selected and the 'Reset Layout' button was clicked

27- The option to map innerducts from the relations window was removed, as selecting it generated an error

28- Clicking in the Relationships section of Treeview caused a Run-Time Error if no Relationships were displayed yet in that session

29- The "Lit Fiber Report", which calculates the length of fiber attached to equipment, was giving an incorrect, and sometimes inconsistent result.

30- A Red-Line or markup layer created in View was editable during the session in which it was created, but if it was opened in a later session, OSPInSight would no longer allow it to be edited.

KNOWN ISSUES

1- The new version of MapX, which is included in View 6.06, causes the Thematic Mapping "Report" to not function with Oracle databases.

Solution: If a copy of the OSPInSight network database is exported from Oracle to a Microsoft Access format, the Thematic Mapping report will function correctly. Advance Fiber Optics will provide instructions and tools to facilitate this process, if you so choose. This problem will be resolved in the next release.

2- When printing the map from View with MapPoint as the background, the printout is dark. Also, the print form takes a long time to close

3- Some forms when closed return focus to a different application, other than OSPInSight. It is necessary to re-select OSPInSight

4- When using Microsoft Mappoint as the background, the Back and Forward functions on the map don't always work the first time

Solution: Sometimes the Back & Forward entries on the right-click menu must be clicked twice to do anything

5- Click 'Print' in the Fiber Panel, and export the data from Crystal to Excel. Note that the data in the last few columns is offset from the headers.

Solution: Select the offset data, and move it so it matches the headers, or vice versa.

6- Any Equipment records that have an invalid TypeID value (such as 'none' when that is not in the TypeID list) will not show up in the "Customers/Equipment Report".

Solution: If you suspect that the report is not displaying all of your customers or equipment, open your Equipment List or Equipment/Customer Editor in OSPM-Edit and update the TypeID values such that they all correspond with an entry from the TypeID list (from the Hardware/Materials Editor)

7- If you create a new table in View, make it editable and add objects such as Polygons, Polylines, Points, Ellipses, Rectangles or Text, the 'Delete' key does not work to remove them.

Solution: It is necessary to delete them by using the Backspace key

8- Currently the Span/LocateID text dynamically resizes to fit the "span" field and not overrun the "fiber" field. However, it still isn't perfect, and depending on how big the form is, it will still run into the next column a little.

Solution: If there is some text overlap, simply resize the form until the text in the span column is not conflicting with the text in the fiber column.

9- When using MapPoint as a background (or when any Raster image is loaded in MapX), zooming in past 0.1 miles will typically invert the mapper. Labeling will also behave oddly at this zoom level with any raster images displayed.

Solution: There is currently no known resolution to this issue.

10- Sometimes on Windows XP machines, creating a red-line or markup layer in the 'My Documents' folder will make that layer behave oddly. Specifically, it will be editable during the session in which it was created, however you will be unable to edit it in any future sessions.

Solution: Create red-line or markup layers in a path that does not include your 'My Documents' folder

-------------------OSPInSight OSPM View 6.04.3 Release Notes--------------------------

Not externally released

ERRORS RESOLVED

1- If all database passwords were the same, then OSPM-View would not allow access to the passwords form or users form through the Setup

2- Relate a MapInfo object (on the DOC layer) to a Document in the Document Relationships editor, then use the OSPInSight GetInfo tool to click on the MapInfo object. In 6.04.1 doing this would fail to highlight the related document in the Treeview

3- Installed Material/Hardware Report, when run in an Oracle network, would not allow the user to re-order by any column

4- MapPoint background layer didn't stay hidden when disabled in layer control

-------------------OSPInSight OSPM View 6.04.2 Release Notes--------------------------

25/May/2004

******** NEW FEATURES ********

1- The limit on the number of layers that can be opened in a .gst file with OSPInSight has been raised from 250 to about 32,000

+++++++++ ERRORS RESOLVED +++++++++

1- An "Object variable or With block variable not set" Error appeared when switching from one network to another with a MapPoint background

2- In the Installed Material/Hardware Report the slack loop placement query would return incorrect values

!!!!!!!!!! KNOWN ISSUES !!!!!!!!!!

1- If you receive the following error while running the taper report: "No object was found using the index you specified", then browse to your \OSPInSight\OSPM\View\Settings\Reports\ directory and delete the 'tapassignments.ini' and the 'taprouting.ini' files. This should resolve the error

2- When using MapPoint as the background and the view is zoomed out to a continent-level view, the network objects are often offset from their correct locations. When the view is zoomed in to a tighter view the objects come into correct alignment

3- If the Administrator password for an OSPInSight network is the same as the Read-only or Edit password, OSPInSight View will state that the Administrator password you entered is incorrect and not let you access the Passwords or Users forms from the setup. The easiest workaround for this situation is to change the passwords through the database manually, or through OSPInSight Edit, such that the Administrator password is not the same as either the Read-only or Edit passwords

-------------------OSPInSight OSPM View 6.04 Release Notes--------------------------

31/March/2004

******** NEW FEATURES ********

1- When performing a Restore, before OSPInSight network files are overwritten a zipped copy of those files will be created, thus allowing for an easier recovery in the event of the wrong files being replaced

2- Prompt for golden directory download when loading a network. Select the option in the Setup

3- The Treeview Search allows partial-string searches within the selected folder...type your string and click the binoculars

4- Support for operating system large fonts has been added

######## TIPS ########

1- The LocateID and colorcode can be displayed with all spans and fibers in reports and forms. To see them in reports click Options->Display Options->Treeview, and check the options for appending the colorcode and locateid

2- The fields displayed in More windows and lists can be customized. Go to Options->Display Options->More, then choose your editor. You can uncheck the fields you don't wish to see, reorder the fields and rename them

3- When you select an item in the Treeview, pressing a letter on the keyboard will find and highlight the next item displayed that starts with that letter, including folders and subfolders. This method will not search through items in a folder that is not expanded. To use the search field above the Treeview, click the folder that contains the item you wish to find, type any part of that item's name in the search field, then click the binoculars button. For example, if you wish to find a pole that has "Benson" in it's name (such as "PL-123 Benson Ln") expand the 'Poles' category, select the first item in the list, type "benson" in the search field, then click the binoculars

+++++++++ ERRORS RESOLVED +++++++++

1- The More window, report, and other .ini files have been updated in the 6.04 release to resolve certain incompatibilities

2- Workspaces saved with OSPInSight sometimes would force the user to browse to the specified layers when being opened

3- Installed Materials/Hardware report showed all cables as underground when querying by Placement='underground'

4- Display Options settings were not displayed in the 'Relations...' window

5- Mapping Rings (Cable Span) would get an "expression too complex" error when mapping very large rings. Now the objects are copied to the animosp layer

6-In Windows XP some forms had the bottom slightly cut off

7-The Route Schematic would not run correctly when opened from within the Taper Report

8-Sometimes when performing a find route through splitters the route distance (based on the last path) would calculate incorrectly

9-When Performing a Find Route in the Fiber Panel, the Span column would show the first span in every row

10-Not all user-defined column widths were saved when ctrl+s was pressed in the taper report

11-The splice spreadsheet was not displaying dead fibers correctly in all situations

12-Installed Material Hardware report terminated when the letter 'e' was pressed in other applications

13-An error would occur when attempting to create a thematic map

!!!!!!!!!! KNOWN ISSUES !!!!!!!!!!

1- The Treeview window loads very slowly, depending on the amount of data in a given list. For example, a network with more than 10,000 poles will typically take about a minute to expand the poles category in the Treeview. This problem is important to us and the performance will be improved in a later release

-WORKAROUND: For improved Treeview performance, group large categories. For example, if you have many poles in your network, click Options->Display Options, select the Treeview tab, then click the Poles category. In the 'Group By' dropdown, select an appropriate category by which to group your poles, such as city, type, class, owner, etc. What you want is to have smaller groups of poles. That way when you expand the poles category you will be presented with various groups that load MUCH quicker, and each group will load much quicker as well

2- The zip utility used in the Backup/Restore utility will crash the application if used repeatedly during the same session

3- The Treeview search utility will only search within the folder that has the focus

4- At times an 'Automation Error' is displayed when the user attempts to export list data to a Tab-delimited text file, or a message is displayed stating "Object invoked has disconnected from it's clients"

-WORKAROUND: This error seems to be very inconsistent...sometimes it will occur for an hour or a day, but will work fine when attempted the next day, or after waiting for an hour. In short...just keep trying.

-------------------OSPInSight OSPM View 6.03.8 Release Notes--------------------------

Errors Resolved:

1- After clicking Hide/Show in the treeview, a gray bar covered part of the map until the network was reloaded

2- Lists use only programmed colors now, instead of inconsitently using system colors

3- When clicking on MapInfo objects on the DOC layer with the GetInfo tool that have documents attached, the appropriate record was not highlighted in the Treeview

4- Redundant route/endpoint schematic print form has been eliminated

5- The calc.mdb database that is used for report-data formatting has been updated to eliminate "Field is to small to accept the amount of data you have attempted to add" errors

6- If you right clicked on a splice-line in the splice schematic and clicked 'Taper Report', the correct spanid was not sent to the Taper form.

7- After performing a Find route and then a Find fault, the row with the fault was not highlighting in the details tab

Known Issues:

1- At times an 'Automation Error' is displayed when the user attempts to export list data to a Tab-delimited text file

3- When opening a network, if an error appears saying "Error Message: The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.", then open the Options->Display Options->Main window, and select a field in the 'Fields to Display' section for each category, and update all of the changes.

-------------------OSPInSight OSPM View 6.03.5 Release Notes--------------------------

New Features:

1- The Taper report Route Details tab now allows the user to open the Route, Splice and Endpoint schematics from a right-click menu

2- LocateID and Color Code have been added to the Taper Report

Errors Resolved:

1- Splice spreadsheet column format corrected

2- Printing a duct-bank report, the install year would always display '2000'

3- Highlighting when mapping and performing find routes has been corrected

4- Relations and More Info sections have been updated

5- Taper report Assignment tab not showing Assignment data

6- Incorrect default paths were placed in the Data Linker form

7- Trying to display relations on objects with document relations gave an error

Known Issues:

1- After performing a Find route and then a Find fault, the row with the fault is not highlighting in the details tab

-------------------OSPInSight OSPM View 6.03 Release Notes--------------------------

Tips:

1- Never save changes to your animosp or animate layer

2- If you are an editor, do not specify a Golden Directory

3- Press Ctrl + Q to save the layout of the toolbars and treeview, press Ctrl + S to save the size and layout of 'More' windows, reports and lists

Errors Resolved:

1- Splice Spreadsheet - Export from Crystal to Excel wasn't working

Known Issues:

1- After completely installing OSPM 6.03, at times the OSPM 6.03 installer will begin to run, and request that you browse to the install files. In order to make it stop running, simply select the .msi file from the CD or the installation files from which you originally installed and let it run through it's process.

2- Taper Report - Route schematic doesn't display correctly when run in the taper report, the objects are all on top of each other. Workaround: Open the Route Schematic from the 'Reports' drop-down menu instead of from the Taper report

3- There are still some rendering bugs to be worked out in the End Point schematic

-------------------OSPInSight OSPM View 6.02 Release Notes--------------------------

New Features:

1- An Error Log has been added under the Help dropdown menu

2- All schematic printing functionality has been improved

Errors Resolved:

1- The End Point Schematic does not pull up in the Fiber panel after shooting several fibers. If you pull up the Schematic before shooting any fibers, the schematic will pull up.

2- Some longer routes render incorrectly in the route schematic

Known Issues:

1- Issue 801 Routes passing through about 100 spans fail to display the labels on splice points and fiber panels

2- Issue 749 Taper Report - Route schematic doesn't run in the taper report

3- Issue 784 Splice Spreadsheet - Export from Crystal to Excel not working

4- Issue 802 Printing Endpoint schematic renders an additional vertical line

5- Issue 803 Endpoint Schematic is inaccurate through splitters

6- Attempting to print from schematics with no printer installed causes a Run-time error, and shuts down the application

-------------------OSPInSight OSPM View 6.01 Release Notes--------------------------

New Features:

1- 'Refresh' added to category right-click menu in treeview

Errors Resolved:

1- An ungraceful error was given if the path was incorrect in the Data Linker

2- Added flexibility in Network Setup

3- Tree View search functioning

4- Reorder termination list by position no longer giving error

5- Selecting an empty Node or category in the treeview gave a 'With block' error

Known Issues:

1- The End Point Schematic does not pull up in the Fiber panel after shooting several fibers. If you pull up the Schematic before shooting any fibers, the schematic will pull up.

2- Some longer routes render incorrectly in the route schematic

3- The Endpoint schematic fails to show span linetimes

-------------------OSPInSight OSPM View 6.0 Release Notes---------------------------

New Features:

1- Press Shift+~ to disable and re-enable MapInfo Callbacks. Disabling MapInfo Callbacks will disable some labeling functionality, however certain map-intensive operations will run much more quickly

2- More and Report forms can be customized and the layout saved by pressing Ctrl+S

3- Field names, displays and placement can be customized and saved

4- All network layers can be saved as part of the workspace, allowing customized display of tables such as pole, conduit, etc.

5- True treeview structure for navigation

6- Improved customizable Treeview display options

7- Interactive Route Schematic, Endpoint Schematic, and Splice Schematic

8- Ability to save a history of Splice Schematics

9- Data Linker tool which facilitates thematic mapping and MapInfo labeling

10- Customizable toolbar layout press Ctrl+Q

11- MapInfo Hotlink tool accessible in OSPInSight

12- MapInfo Layout window

13- MapPoint data available as background map

14- More complete Installed Material/Hardware report

15- Splice tray field allows multiple trays

16- Improved Termination status integrity

17- Bi-directional Find Route function

18- Extended attributes fields added for network items, allowing users to add customized data

19- Ability to perform a find route independent of the map

20- Red line capability now available View only version

21- Title and page number have been added to Work Order Report printout

22- Equipment added to Work Order Report

23- Ability to relate folders, as well as individual files, to network objects

24- Enhanced ring/circuit data storage

Errors Resolved:

1-If a cable span is using a cable with a COLORCODEID of 6 or more digits, an Overflow error from CRoute:RouteFindColor was generated upon running the Find Fault function.

2-When performing a Find Route, the span field in the Assignments tab did not show the correct spanids

Known Issues:

1-Rendering some very large panel graphics can be a little slow, in panel designer, and the fiber panel

2-Color Code Legend in the splice schematic covers the splice data

3-In windows XP some forms have the bottom slightly clipped

4-At the completion of the MapX install an innocuous error is generated, "Incorrect command line parameters"

5-In the fiber panel, after unchecking the 'Highlight route' option, it is necessary to reload the form to re-enable them

6-Infrequently when a right-click menu is displayed (from map or treeview) and a toolbar or dropdown menu is left-clicked, the application will ungracefully exit

8-Geosets created in OSPM View are incompatible with MapInfo's Geoset utility

Known Oracle Issues:

1-After adding an existing OSPM Oracle database to the setup list, an error is displayed 'check that the database is not read only' and the database cannot be loaded if Oracle client isn't installed

-------------------OSP InSight View 3.07 Release Notes-------------------

Find Fault updates..more accurate

CRoute error trapping

Updated rptConduit.rpt handles 0 in install date fields 1/15/03

-------------------OSP InSight View 3.06 Release Notes-------------------

New Features:

-the GIS software has been upgraded from MapInfo MapX 4.5 to MapX 5.0, which brings superior database connectivity and speed as well as other features that can be seen at http://www.mapinfo.com/mapx

Errors Resolved:

1-Ruler would not function after a certain distance

2-When you added a user to the Oracle USER table as read-only, and then attempted to open the database in View, an error was displayed

3-In Hometown, an incorrect path to the .wor file was displayed

4-When running an Installed Material/Hardware report on a region containing over 1000 objects, and error was generated

Known Issues:

1- When you run the Customer/Equipment report, you can double-click a row to open the More Info window, the the fields are empty

-Resolution: Open the More Info window from the Equipment list in the TreeView

-------------------OSP InSight View 3.05 Release Notes-------------------

(Internal Release)

Errors Resolved:

-Registration software updated

-Splice Schematic display updated

+++++

Splice Schematic Setup

The Splice Key Schematic Setup allows users to customize the layout of the Splice Key Schematic, granting them the ability to customize for unusual color-codes, long comment fields, or other special circumstances.

Text Offset – determines the placement relative to the top of the window. It is recommended that you not change this value.

Cable Offset – determines the vertical space between the cable information blocks.

Splice Offset – determines the horizontal distance between the vertical lines in the schematic.

Group Offset – determines the vertical distance between each line of text

Fiber Text – determines the horizontal distance between the cable and the fiber information

Font Size – determines the font size

Fiber Offset – determines the horizontal distance between the fiber information and the splice info

X - start – determines the horizontal distance between the splice type and the schematic lines

X - end – determines the length of the horizontal line of the schematic

Y - start – determines vertical offset of text

Y - end – determines vertical offset of schematic lines. Y - start & Y - end should have the same value.

Line Style – determines the schematic line style, i.e. dashed, dotted, solid, etc.

Line Width – determines width of some of the schematic lines

Lines/Page – determines the number of lines of text per page

+++++

-------------------OSP InSight View 3.04 Release Notes-------------------

Errors Resolved:

-When closing a network, sporadically some of the database menus were left on the toolbar, causing the application to crash when used

-Find Route function would report a zero distance for spans after a patch

-When connected to an Oracle database and running the Duct Taper Report, performing a 'Find Endpoints' function would produce a run-time error

-When connected to an Oracle database, the plant drawings would be layered in a random order, and interspersed among the background layers

-when selecting and mapping items in a list in certain orders, an EOF BOF error was received

-the ability to convert the database has been removed

-Splice schematic displayed incorrectly for enclosures with more than 7 cables

-The spreadsheet would not complete for enclosures related to poles

-InSight can now resolve the Oracle service name with multiple versions of Oracle on a system

Known Issues:

1- The 'OPTICALLENGTH' column in the 'Installed Cable Span List' actually contains the Physical Length of the cable span, rather than the optical length

2- STILL A KNOWN ISSUE: Often, when you right click on the map or treeview displaying a drop down menu, then a left click on any toolbar, the application will shut down instantly

-Resolution: We know that this error is irritating and are working towards it's resolution. It is caused by third party software, over which we do not have complete control, so we appreciate your patience until it is resolved. Thank you

3- Export the results of the 'Installed Material/Hardware...' report, some fields are repeated in the report, others are left out.

-Resolution: Format report after exporting

-------------------OSP InSight View 3.03 Release Notes-------------------

New Features:

-When labeling a cable with the OSP InSight GetInfo tool, the 'Cable Segment' section can now be set to not display

Errors Resolved:

-The GetInfo tool was not working consistently on the *DOC.tab layer

Known Issues:

1- Often, when you right click on the map or treeview displaying a drop down menu, then a left click on any toolbar, the application will shut down instantly

-Resolution: Avoid selecting any toolbars or menus if you have a right-click menu displayed

-------------------OSP InSight View 3.02 Release Notes-------------------

Errors Resolved:

The following errors have been resolved in this release

-Windows NT Dr. Watson Install error

-MapX40.OCX not registering

-Distorted tool bar on 'no database open' screen on Windows 2000 OS

-Thematic mapping problems

-Get info tool map shift

-list run-time errors when mapping

-Mapping from map region locking error

Possible Installation errors and resolution:

-if OSP InSight Pro is installed on the computer before you install view, you might receive a machnm1.exe error when trying to run Pro, after installing view.

Resolution: reboot your computer.