06-09-2010 03:40 PM
Currently I have a PXI-1000B, and I have opnly ever used the same card in the same slot. I have a much faster sampling card and I'd like to try it out but I receive this error message when trying to use it. The interesting problem is that there is a exact duplicate of the card that I am using right now in another slot and it also does not work, giving the same error message. I did not setup the lab so I don't know if there was a procedure to make the one slot operational that the other haven't recieved. Do I need to set up the clock somehow?
DAQmx Error -200550 occurred:
Hardware clocking error occurred.
If you are using an external reference or sample clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that its rate matches the specified clock rate. If you are generating your clock internally, please contact National Instruments Technical Support.
Status Code: -200550
Thanks
06-09-2010 03:44 PM
You need to provide more information.
A PXI-1000B is a chassis.
What DAQ cards are you using, (old vs. the "much faster sampling")?
06-09-2010 03:50 PM
06-10-2010 06:13 PM
Hello,
What exactly are you doing when you receive this error? Are you able to use the NI-Scope Soft Front Panel without any problems?
Regards,
06-11-2010 04:09 PM
Hopefully this covers everything:
We have a NI PXI-1000B crate & several digitizer modules (2 PXI-5122 and 1 PXI-5152) in our lab. We have been heavily using one of the PXI-5122 with no problems, but need to move on to using the faster PXI-5152.
We find that we cannot read out either the 2nd 5122 or the 5152. They both consistently fail with "hardware clocking - error 200550". This occurs both while attempting to test the cards in MAX as well as while trying to sample with them. There is one difference between the errors, when rebooting the system, when the drivers access the cards the 5122 cards behave in the same way with green lights, however the 5152 flashes a red light before resuming a green light for access.
We have swapped modules and slots. Both the bad 5122 and the 5152 produce the same error in different slots, including the one the good 5122 normally operates in. We have also moved the good 5122 and it works fine in different slots, including the ones the bad modules fail in.
The bad 5122 was once repaired (replaced fuse) at NI for the same problem, but we have no history of repairs to the 5152. We "inherited" this setup from a technician who is now in another lab but reachable, so we don't know the exact history of the set-up.
It seems strange that both bad modules exhibit the same error. We're happy to try any other suggested tests here before sending them for repair. Any suggestions would be much appreciated.
06-14-2010 10:15 AM
Hello,
This error usually indicates that the card cannot communicate with the onboard FPGA. There are a few steps you should try before having the card sent in for repair.
You mentioned that you had already tried some of these, but I want to make sure that you run through the list and try them all. If the problem still persists after this then your next move is to have the cards sent in.
Regards,
06-14-2010 02:22 PM
Thank you for the reply, the problem has persisted throughout the tests, so it looks like we'll be sending it in for repair.
Thanks again,
Ben
08-11-2013 10:40 PM
Dear Ben,
I had a similar problem as above.
I bought PXI-5122, PXIe-1073 and PXI-6221 for my experiment.
I try performing data acquisition by using external sample clock as reference.
I use the example from Labview 2012 "niScope EX External Clocking.vi", sending in an irregular sine wave as sample clock into CLKIN, then getting data from channel 0.
The moment I run this VI, the error prompt :
"Hardware Clocking Error occurred."
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the speicified clock rate."
Then, I change External Clock Rate to 3 MHz, error prompt that the clock rate is not valid.
The generated signal I had used is as shown below, a sine wave period of 220ns to 300ns (Around 4 to 7 MHz), less than 2V .
08-12-2013 05:09 PM
winsoncws,
You might try ensuring that you are operating within the specs of the equipment with the external clock by checking out the user manual. Also, you can try the example located here.
You may want to try posting this on a new thread. Generally more of the members of the forums respond to new questions instead of older questions. The last time ben posted here was in 2010.