Chassis TimeSync Custom Device Feedback

[JeKo]

Thanks a lot!

I would build it by myself, but I don't have access to the hidden property for 6682 (Set Timekeeper CLK10 Input.vi).

But having a built version on the community page is even easier.

Regards,

[puffin1486]

Hello Joel, I tried to use this with 2015 SP1 and had some issues at runtime. I couldn't build due to the hidden properties.

Could you upload a built version for 2015 SP1?

[johnporter]

Hi All,

I am trying to use the device in Veristand 2015 SP1 and am unable to get past a deployment error:

Details:
Error -1074118630 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi
<append>=========================
NI VeriStand: niSync Initialize (String).vi

Possible reason(s):

Driver Status: (Hex 0xBFFA401A) The specified device is a remote device. Remote devices are not allowed.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

It would appear the custom device is not able to reference the VISA alias for the PXI card.

Have tried multiple names, have tried deploying from multiple PC's.

No matter what I set the Name value to in the system def I get the same deployment error.

Have tried deploying an RT VI directly from LabVIEW with the Sync init function set to the MAX reference and it runs without error.

Card is a 6683H set to IRIG-B AM, test panels prove source is fine.

Any input greatly appreciated, this issue holding up system deployment.

[Chris_Jones_NIUK]

Hi John,

I've had some experience with this recently and actually saw the same error as you during my use. Looking at the screenshots, it seems there's some confusion regarding naming. The entry under 'Time-Based Synchronization Module' (rather than 'Name' which is just the name of the TimeSync CD) should match the name within MAX. I've got a setup here with the card and tested this: If I have a mismatch between these, I can get the exact same error as you. Let me know if this resolves the issue.

[johnporter]

Thanks for the response Chris. Brilliant news you have seen the same issue and have a resolution.

The hardware is on a customer site, I will visit tomorrow afternoon to run a test.

It would appear the documentation for the custom device is fairly misleading if this is the error. The system def input for the device even has context sensitive information pop up when you enter card model numbers into that input, and in the source code for the device it appears to use that information to determine the model of the pxi card. I guess this information must be pulled automatically once the actual reference is correct.

Will let you know how I get on.

Cheers

[johnporter]

Hi Chris,

Just to let you know your suggestion worked,

Thanks, John

[Chris_Jones_NIUK]

Good to hear - thanks for the update!

[T.Hamberger]

Hello,

as we currently use Veristand2017 with LabVIEW2017, I want to ask whether it is possible for NI, to build the TimeSync Custom Device also for LabVIEW 2017,

and offer it for download?
[as it contains vis with removed BlockDiagrams, I cannot convert it myself]

Thank you in advance...

[Andy-C]

A 2017 build as well as the original source code is available on the community page for this add-on. The source code is also available on GitHub here.

[T.Hamberger]

thank you!