Chassis TimeSync Custom Device Feedback

[UsmanKhan]

Stephen,

I check the versions and for NI-Sync it says 3.4.0 and for TimeSync 1.3.0? Do I need to look for NI-Sync 3.4.1 then?

[StephenB]

I'm not sure that you need NI-Sync 3.4.1 .... I think NI-Sync 3.4.0 should work fine.

I mistyped when I typed NI-TimeSync 1.2 or later. In fact you need exactly 1.2. Version 1.3 will not work. Uninstall NI-TimeSync 1.3 from your real time target, your host computer, and then follow the instructions on the download page exactly to install NI-TimeSync 1.2: https://decibel.ni.com/content/docs/DOC-29546

That should do it!

[UsmanKhan]

Below is what I get. I did install that version locally and on the real time target but still gives me the same error.

[nitsup] [[NI-Sync]]  Warning: .\source\nitsu\service\tDriverInitializer.cpp:427 - A NI-Sync Device was unable to start the 1588 protocol on boot, Please check your network adapter configurations, Error code -302016Preparing to run system definition...
Loading c:\ni-rt\NIVeriStand\SystemDefinitionData.nivscfg

System Definition Details
-----------------------------
Name: TimeSyncWith6683H
Version: 1.0.0.45
Description:
-----------------------------
Loaded 0 calibrations.
Initializing DAQ devices...
Initializing DAQ waveform tasks...
Initializing engine timing sources...
Initializing FPGA devices...
Initializing inline custom devices...
Initializing data sharing devices...
Initializing models...
Synchronizing Timed Structures:
Controller_HP

Controller_LP

ControllerWatchdogLoop

Synchronization Timeout: 120000 ms
Starting asynchronous custom device loops...

****************************
System error encountered.
:::Details:::
Error code: 1003
Error Message: LabVIEW:  The VI is not executable. Most likely the VI is broken o
r one of its subVIs cannot be located. Select <b>File>>Open</b> to open the VI an
d then verify that you are able to run it.
****************************

System awaiting new configuration from client.
Stopping system definition...
Stop time: 08:40:21
11/04/2013

Finalizing engine timing sources...
Finalizing inline custom devices...
Waiting for asynchronous custom devices to shut down...
Asynchronous custom device shut down complete.
Finalizing DAQ devices...
Finalizing FPGA devices...
Finalizing data sharing devices...
Finalizing models...
Unloading system definition...
VeriStand Engine idle. Awaiting command...
VeriStand Engine idle. Awaiting command...

[StephenB]

Can you create a MAX technical report of your real time target please? http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4?OpenDocument

I have a utility we can use to figure out why the VI is broken, but I need to see the max report first.

Also, different issue, but verify your 6683H's Ethernet port is enabled. That might clear up the first error.

[UsmanKhan]

I have replied to the email notification and attached the report with it.

Thank you

[StephenB]

Those dont go to me... thats an automated system.

Instead can you attach it here? Click Use advanced editor in the top right of the quick reply window to get attachment options

[UsmanKhan]

Attached is the file. Thanks.

[StephenB]

Usman,

This report does not contain all the information I need. Are you sure you followed the instructions to create a report for technical support?

Thanks!

[StephenB]

This might be easier:

can you just get a screenshot of the software installed on the target?

Thanks!

[UsmanKhan]

Here are the screenshots