Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

1588 device not showing in ethernet

Solved!
Go to solution

Yes, we downgraded to NI-Sync 3.0

 

But now, when the device is plugged and sending it's PTP paquets, it causes the card to enter in the FAULTY state (red light on the 1588)

 

We called NI and got our own representant investigating on the topic, we'll see if something comes out of this.

 

If anyone got any idea? (Well it could be the new NI-Visa interfering with the old NI-Sync, but that's just a random guess)

 

So thank you for any lead,

Seb

0 Kudos
Message 11 of 16
(2,890 Views)

Hi,

 

Did your PXI 6682 go into a faulty state when you were using NI Sync 3.1? What happens when you only connect the PXI 6682 to the network? Can you post a screen shot of this faulty clock for everyone to see? Are you using a cross over ethernet cable or a path cable? Are you connected to a HUB? Or can you try a direct connect as I suggested earlier?
Matt
Applications Engineer
National Instruments
Message 12 of 16
(2,877 Views)

1) Did your PXI 6682 go into a faulty state when you were using NI Sync 3.1?

1.1) No...but it wasn't reading the device's packages so it's inconclusive to know if it was faulty before

 

2)What happens when you only connect the PXI 6682 to the network?

2.1) Works just fine

 

3)Can you post a screen shot of this faulty clock for everyone to see?

3.1) The 1588 LED is red...no need for a picture 😛

 

4)Are you using a cross over ethernet cable or a path cable?

4.1)...not sure? ^^; I'm using normal cables that you buy at 7$ to connect computers to routers

 

5)Are you connected to a HUB?

5,1) Yes

 

6) Or can you try a direct connect as I suggested earlier?

6.1) Same thing happens (Red light)

 

Hope this helps :S

0 Kudos
Message 13 of 16
(2,874 Views)
Solution
Accepted by Sebastien Dupere

If it is going into the faulty state then that means the Sync Interval is probably off.  I think the NI default is 1 second, but several devices use 2 seconds.  Try changing the Sync Interval in MAX on the properties dialog to see if that fixes the issue.

 

-Josh

Message 14 of 16
(2,871 Views)

Bingo on that one Joshua 🙂

 

Well now, any practical way to change that? (not needed for us but hey good info)

 

Thanks ya all, lots of help for the novice that I am,

Seb

0 Kudos
Message 15 of 16
(2,866 Views)

If you make the change in MAX from the Properties page it should persist after reboots.  If you just change it in the Test Panel it will revert to what is in the Properties page if you reboot the system.  You can also programatically set it in your application, but I wouldn't recommend it since it takes a minute or two for the clock to settle after making a change like that.

 

-Josh

0 Kudos
Message 16 of 16
(2,860 Views)