First Sign: Error Message: Could not start ParBERT system…
Result: Measurement Procedure will be ended
immediately with undefined result.
- Check with the ParBERT GUIs if
the clock systems have a valid clock (The PLL indicator on the right upper
side of the ParBERT GUI have to lit
constantly green). If the PLL is red, check the output signal of the SG.
- The RF output should be
- The amplitude is too small
- The Data SG should get a
trigger signal from the Clock SG (Event 1 of Clock SG has to be connected
to Patt Trig In of the Data SG on the back side of the SGs).
- The SGs are wired vice versa:
the one which should provide the clock for the data channels is connected to the pixel
clock group (DSRA) of the ParBERT and vice versa. Please check the
configuration once more.
- The trigger output of the data
group (DSRB) is not connected to the Start In of the pixel clock group
(DSRA). This cause a timeout if ValiFrame starts the pixel clock group,
because it needs a trigger impulse to be started.
- A setting pattern/sequence
setting is not compatible to the other settings. This would be a software
bug and should not happen. Please contact the BitifEye Support (email@example.com)
immediately. We need the actual video mode and the procedure which fails,
and the ParBERT error message (visible if you try to start the ParBERT
manually with the ParBERT GUI).
Question: Test 8-25 Deep Colour fails without showing any test image, why?
Answer: If you have selected support for deep-colour
colour-depth but not for 36 bit colour depth, the test will fail according the
description in the CTS.
First Sign: Intra pair skew test starts with pixel errors.
Result: Measurement will fail
Resolution: Perform the
Skew Calibration for Clock and Data in the calibration section.
First Sign: The test automation hangs (more than 15 minutes)
Result: no progress in the test procedures
- Missing connection between the
Event 1 output of the Clock SG to the Pattern Trigger input of the Data SG.
No clock on the Data SG, and Data Group of ParBERT could not start.
- Missing connection between the
trigger output of the ParBERT data clock module to the start input of the
pixel clock clock module -> pixel clock module will not start.
- DSO hangs->check if the HDMI
application and the DSO firmware is still running properly. If not reboot
DSO and restart ValiFrame.
- ParBERT Firmware has
crashed->very rare the ParBERT firmware does crash very silently. You
only find a small dialog behind the ParBERT user interfaces which allows
you to ignore this crash and proceed. Proceeding is not recommended
because the Firmware is then in an undetermined state. Maybe you can
select proceed to get ValiFrame back to react but you should abort every
remaining tests and store the test results. You have to close ValiFrame,
the ParBERT GUIs, the ParBERT Firmware and switch off the ParBERT VXI
Frame. After restarting you can go on with testing.
Question: Test XY from the CTS is missing, why don't you implement this test?
Answer: This can have multiple reasons. One reason is that there is a problem implementing this test. An other reason could be that this test uses instruments which can't be controlled by ValiFrame.
Question: I have the prototype DPTC with the USB connector and want to use it with the actual version of ValiFrame but the connection doesn't seem to work! How can I use it?
- Go to the ValiFrame Program directory
and locate the DisplayPortDll.dll it should have a size of about 540KB
- rename it to DisplayPortDll_Eth.dll
- Locate the file DisplayPortDll_USB.dll
with a file size of about 215KB and rename it to DisplayPortDll.dll
- Start the station configurator and
change the address to 0, click apply
- Test the connection and it should work, if it doesn't work contact us!
Question: I can not find test xy I've seen in the manual, where can I find it?
Answer: This can have various reasons, some tests are only available in the Expert Mode. To enable it please select it in the configure dialog. In addition depending on the hardware configuration it is possible that some tests are not offered, to verify this please look into the Procedure Description Guide of DisplayPort.
Question: My virus scanner detects a heuristic virus detection in your executables. Is there a virus in your software?
Answer: No. This detection is caused by our protection utility to make sure, that our software is only used, when it is licensed.
Question: Is there a difference in the test procedures available both in compliance and expert mode?
Answer: It depends on the test procedure! Where it
makes sense to have a different implementation or additional parameters
it is implemented. However for some procedures there is no need to have
a special expert mode or we don't see it. If you sink we have missed
something write us a mail.
First Sign: Could not connect to Instrument XY.
Result: Instruments won’t be setup by
Resolution: Check the connections to the
instruments using the Agilent Connection Expert (CE), configure the CE to be
able to communicate with all instruments (green sign) and for each instrument
copy the VISA Address from the right to the instrument field in the ValiFrame
Resolution2: If the upper description won’t
solve the problem, try to do a reinstallation/repair of the Agilent I/O
Libraries. ValiFrame uses the VisaCom from the I/O Libraries to communicate
with the instruments.
Questions not answered? Click here to get in contact with us and get help!