Where do I find the MentorXL IP address and network configuration information? | What frequencies are used in the HD Multiburst Test Pattern? | Why is my MentorXL not saving its settings? | Can I have a GPS and genlock input at the same time? | NTP not synced? | Setting the MentorXL as an NTP Server? | How do I save the Config file from the MentorXL? | How do I set the MentorXL to account for daylight savings automatically?
This can be found either by browsing to the MentorXL and opening the Status > Info page.
Or from the unit’s front panel by navigating to Status > MentorXL Information screen.
The HD Multiburst test pattern is made up of a series of sine wave bursts that appear as a series of vertical lines when viewed on a monitor. The frequencies of the tone bursts are:
5, 10, 15, 20, 25, 30Mhz.
This problem could be associated with either a backup battery failure or not allowing a selected parameter to ‘time-out’ in the menu structure.
The fault can be determined easily; if it is a backup battery problem, all user settings will be lost. If related to the menu time-out, only the setting(s) that have been applied within a menu tree may be lost.
To overcome the loss of parameter settings once the required sub-function is selected, (the OK button is used to choose it), and the currently selected option is indicated by asterisks (e.g. *ON*), do not use the ‘Cancel’ function to return to a higher menu. Although the chosen setting will be applied immediately, it has not been stored, and will be lost when power is removed.
It is essential that the currently selected parameter is allowed to ‘time-out’, and then revert to a higher menu tree automatically. Using this method ensures the parameter is saved to memory.
An alternative workaround: in the Setup > More > Display menu set the <Menu Timeout> to *Disable* and the <Set Period> to 3 secs. Using this method, there is no Menu timeout, and the display will be left at the last selection.
Once the parameter has been set the unit can be returned to its normal operating mode, or another function chosen.
If the MentorXL is losing all of its settings this may be due to the battery back-up circuit fault.
A quick test can confirm this. Isolate the mains power and remove the top cover of the MentorXL, next re-apply power to the unit. Remove the battery jumper link J48, this link is labelled 'BAT' and is on the right-hand end of the motherboard, half way down.
Using a digital volt meter, measure the voltage between the chassis and TP68 (labelled BAT), the TP is near J48 and should measure approximately 3V. Using the DVM measure the voltage between the chassis and the Battery BT1 at the front right-hand side of the motherboard. The voltage should be approximately 2.4V. Minimum battery voltage is 1.5V before memory loss is likely, if the battery measurement is below 2.0V with the power removed it is recommended the battery should be replaced.
No. If the Mentor has been configured to use GPS as its locking method, then any genlock inputs must be removed as they can cause errors in the locking process.
As stated in the manual, the genlock lock mode should be set to "Internal Freerun". If set to “Force Strict Sch” or “Sync Lock Only” it will never lock to 1PPS and the Mentor ends up in some indeterminate lock state.
Please check that the PC time is within an hour of the NTP time. If time difference is a long way out the time will not sync, set the PC time to within an hour of the Server time before the sync.
The NTP Server uses port UTP 123. Please confirm this port is not being blocked?
Depending on the operating system, when the PC is synced to the NTP server it will either jump the PC time to the NTP Server time or slew the time over a number of minutes to the NTP time. For example, if the time difference is say 10 minutes out, it will jump the time to NTP time. If it is say 30 seconds out, it will slowly slew the time to NTP time. Another point to note is that after the sync has occurred the PC will now free run and drift from the NTP Server time until the next sync occurs.
The NTP server is easily setup from either the front panel of the Mentor XL or from the Vector web browser pages. We recommend using the web browser if possible as more options are visible at the same time when making changes and it is generally easier to navigate.
From the web pages, go to the Setup > Misc page and find the NTP settings section in the middle of the page. To use the Mentor as a server, please select ‘Server’ in the mode drop down list.
In the server address please enter the IP address you wish the server to be placed. This will be the address you need to enter on clients looking to get their timing from the server.
Click submit to enact these changes.
These same settings can be accessed from the front panel by navigating to the Setup > More > NTP menu.
Once this has been done, you should then be able to set your NTP client devices to look for the server at the IP address you just set and when they poll that address, the NTP time from the Mentor XL will be obtained.
Please ensure all devices are on the same network and that any firewall / network port issues have been opened to allow communication between devices. The NTP Server uses port UTP 123.
To save the file from the MentorXL go to the Admin > Config screen. If you wish to save the configuration file currently running on the unit, ensure the ‘Current’ configuration is selected in the Configurations drop down menu.
Please note. If, for example, ‘Slot 3’ is selected in the drop down menu, then the configuration saved to this slot will be saved to file.
Next select ‘Save Selected Configuration to file’ option.
Selecting the ‘Save Selected Configuration to File’ option will now download the current cfg file to the PC.
When a location setting has been chosen, the MentorXL will automatically adjust its real-time clock to account for daylight savings. This does not automatically update the timecode outputs however.
The timecodes are only updated when the JAM operation is performed. To ensure this occurs automatically around the daylight savings adjustments, we suggest using the following setup:
Configure the all frequencies tab of the timecode menus to update using RTC as the source at an AUTO time of 01:00:01.
Configure the individual frequency that your outputs use (most commonly 25Hz in a PAL environment) to update using RTC as the source at an AUTO time of 02:00:01.
This setup should ensure that whether the clocks for forward or backward, the timecodes will AUTO-JAM a second after the change takes place.
Please note, an auto jam will cause a temporary disturbance in the MentorXL signal outputs, set the AUTO time such that the jam will occur at a time when the disturbance will not cause a disruption to the studio outputs.