Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

1588 device not showing in ethernet

Solved!
Go to solution

This is a very basic question (since I am new to everything)

 

So if you have a card that synchronize your chassis (PXI-6682) and you plug it via a cable on the local network.

You also call the necessary APIcalls (niSync_SetTimeReference1588OrdinaryClockniSync_Start1588).

 

And on the other end you have a device which also uses 1588 (PTP) and is also plugged on the same local network....

 

Should both the card AND the device notice each other automaticly?

For now what happens is:

  • The PXI-6682 is master (should be slave)
  • The other device is master

 

This means, for me, that they do not seem to communicate between one another.

 

Can someone explain to me a nice step by step of what I would need to do?

Message Edited by Sebastien Dupere on 10-26-2009 03:47 PM
0 Kudos
Message 1 of 16
(6,862 Views)
What other device do you have? Is it 1588-2008 compliant?
0 Kudos
Message 2 of 16
(6,850 Views)

The thing is that device is some kind of special device used to prove timing via 1588 is functional.

 

*Gets the big book and browse rapidly*

 

Let me see....in a few minutes I can tell you that from reading from the book:

 

  1.  The ___ will initially be configured to receive its time through PTP (Precision Time Protocol). (...)
  2. By default, the instrument will receive its time through PTP

I know this isn't much, but this device doesn't have much ONLINE documentation so unless I call the company, I might not be 100% sure.

 

My question was mostly to know if NORMALY a 1588 PTP device plugged on my company's network would REGISTER automaticaly as a 1588 device (and thus add itself to the list of clocks)... Because I really need to know if I need to register it or do anything special.

 

If I know more about HOW to setupt a 1588 ethernet network, maybe I can figure out what I'm missing.

 

And again, sorry for being very vague about the device itself ^^; (it's not NI stuff sadly)

0 Kudos
Message 3 of 16
(6,843 Views)

Hi,

There is an Introduction to Distributed Clock Synchronization and the IEEE 1588 Precision Time Protocol that you might find helpful. Also the NI PXI-6682 Series User Manual and Specifications has a lot of good information about that board. Have you had a chance to look at either of these?

Matt
Applications Engineer
National Instruments
0 Kudos
Message 4 of 16
(6,826 Views)

Darn erased my post...alright here is the basic reply:

 

1) Yes I checked both those documents, but I found no example on how a network in 1588 is suppose to be...the explanation is more about HOW 1588 works (in the protocol)

2) Checking the 6682 specs ...wqell I did and all it told me more than the iontro is that it's master (green light blinking every 2 seconds)

 

So am I to assume a normal 1588 PTP network connection works like so:

 

1) Plug router in Network plug

2) Plug ___ device in router

3) Plug PXI-6682 in router

4)Start chassis (with PXI-6682)

5) Start ____ Device

6) Start computer

7) Start task

😎 Auto synchronisation between the timing card and the ___ device with no parametrisation whatsoever

0 Kudos
Message 5 of 16
(6,822 Views)

Hi,

 

The necessary API calls are what you need to get the PXI-6682 to look to the network and begin PTP time negotiation. I’m not sure what you need to do in order to get your other device to communicate with the PXI-6682. Since both are showing up as master, can you try directly connecting the two devices to eliminate any network considerations?

Matt
Applications Engineer
National Instruments
0 Kudos
Message 6 of 16
(6,800 Views)

Sadly I can't because the only way to know if it's master or slavbe is to check a web application...and for that I need the device to be linked to my computer.

 

But yea, it's thiose necessary steps I'd like to know ^^;

 

Thanks

0 Kudos
Message 7 of 16
(6,798 Views)

Hi,

 

It looks like the devices are not seeing each other as they are both showing as Master. I just set up a PXI 6682 and with a second 1588 and set up PTP communication with just those few API calls (you didn’t mention an initialize step but that’s also needed). If you have a second 6682 to test with that would be good to eliminate a source of error, otherwise I led to believe it is your network and you should try a direct connection.

Matt
Applications Engineer
National Instruments
0 Kudos
Message 8 of 16
(6,776 Views)

Well someoene in my company came and help me out showing me stuff like ethernet paquet sniffing...didn't think sniffers were free ah well, I'm still a novice XD

 

Anyway the problem is that the device is using PTP 1588 v.1 while the PXI-6682 uses PTP 1588 v.2

 

 

Anyone knows if there's a qay to use v.1 on that card?

 

Like since it's the same protocol, there must be a way to be backward compatible?

 

Thanks for the support though,

Seb

0 Kudos
Message 9 of 16
(6,767 Views)
What version of NI-Sync are you using? The read-me for the NI-Sync driver version 3.1 states that the 1588 protocol was upgraded and it is not compatible with the older protocol. If your device needs to use the older protocol can you use an older version of NI-Sync?
Matt
Applications Engineer
National Instruments
0 Kudos
Message 10 of 16
(6,734 Views)