NI 5105 returns error 50550

[Alex T]

Hi,

I’m using a NI 5105 in  TestStand sequences (4.1) on a testbench. It was fine (Timing tests ran ok meaning the scope was working fine at that time) until I got back to work 2 weeks ago and nobody turned the testbench computer on while I was away. It is now returning the following error on every step involving the scope:

An exception occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'

An error occurred while executing the step.

Component Works IVI Control Error: The IVI Read operation failed on channel 'CHANNEL0' for logical name 'PXI_SCOPE_1'.

Details: (CHANNEL0) NI Platform Services:  A synchronization object was not acquired within the time limit. The operation could not be completed as specified. Status Code: -50550 [IVI Error Code:  BFFA65D9]

Source: TSIviStepTypes

After some research on NI Forum, here are the solutions I found:

• A fix for PCI-5122 that recommends upgrading the firmwire but the tool is not provided on NI 5105. I updated NI Scope 3.4 to 3.7 though.

• The topic also suggests that it could be related to computer processes running that doesn’t allow the CPU to allocate enough time to the scope process : nothing but the needed is running background.
• Selftest runs successfully but self calibration does not complete, it still runs after 3 hours which I assume is abnormal.
• Using NI Examples (Labview 8.5) to run the scope results with the same error. So does running the SFP tool with a function generator connected. The computer freezes when it occurs and a reboot is inevitable to regain control over the computer.

What does this error mean ?

How can I fix it ?

PS : My apology if it doesn't belong to this board, can an admin please move it to the correct one. Thanks.

Regards,

[Alex T]

Hi,

I’m using a NI 5105 in  TestStand sequences (4.1) on a testbench. It was fine (Timing tests ran ok meaning the scope was working fine at that time) until I got back to work 2 weeks ago and nobody turned the testbench computer on while I was away. It is now returning the following error on every step involving the scope:

An exception occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'

An error occurred while executing the step.

Component Works IVI Control Error: The IVI Read operation failed on channel 'CHANNEL0' for logical name 'PXI_SCOPE_1'.

Details: (CHANNEL0) NI Platform Services:  A synchronization object was not acquired within the time limit. The operation could not be completed as specified. Status Code: -50550 [IVI Error Code:  BFFA65D9]

Source: TSIviStepTypes

After some research on NI Forum, here are the solutions I found:

• A fix for PCI-5122 that recommends upgrading the firmwire but the tool is not provided on NI 5105. I updated NI Scope 3.4 to 3.7 though.

• The topic also suggests that it could be related to computer processes running that doesn’t allow the CPU to allocate enough time to the scope process : nothing but the needed is running background.
• Selftest runs successfully but self calibration does not complete, it still runs after 3 hours which I assume is abnormal.
• Using NI Examples (Labview 8.5) to run the scope results with the same error. So does running the SFP tool with a function generator connected. The computer freezes when it occurs and a reboot is inevitable to regain control over the computer.

What does this error mean ?

How can I fix it ?

PS : My apology if it doesn't belong to this board, can an admin please move it to the correct one. Thanks.

Regards,

[Romain_Duval]

Hi Alex T,

Did you try to use  the tool even though it is precognized for the 5122?

tool

regards,

[Alex T]

I didn't but before i do that, is there anyway to backup the current firmware if it doesn't work ?

[Alex T]

The tool seems to be specific to NI 5122 as it detects no device. Reinitializing the device fails as well : no response after a while just like self calibration. Thanks for replying by the way.

[TimmTheEnchanter]

Hi Alex,

You can find your firmware updater for the 5105 at this location.  Can you open this up, select the 5105, and tell us what version of the firmware is currently on that device?  Also, let us know if the firmware updater suggests there is a higher version of the firmware available, and what that version is.

C:\Program Files\National Instruments\NI-DAQ\fpgaFiles\ni5105

(for the above two questions, it may just be easier if you attach a screenshot of the window.)

What version of NI-SCOPE do you have installed?

-Andrew

[TimmTheEnchanter]

Hi Alex,

I'm sorry, I misread your previous message--you're correct, the firmware updater tool is not relevant for the 5105.

Could you test this on another 5105 just to confirm it is an issue specific to the 5105 you are using?  (In other words, make sure it is not the test sytem).

If you can confirm this issue is something specific to the 5105, I would recommend:

1. Setting up an RMA

2. Post the RMA Number and Serial Number here.

-Andrew

[Alex T]

Hi Andrew,

I will ask if there is a spare 5105 available on wednesday but i doubt it. How can we proceed otherwise ?

Regards,

Alex

[TimmTheEnchanter]

Hi Alex,

I would like to make sure we can confrim another 5105 works and this one does not.  If you cannot do this, you may want to choose to RMA the unit.  If the unit does not pass self-calibration on its own (as you mentioned) that is most certainly a reason to RMA the unit.

You may want to talk with your sales representative about borrowing a 5105 from a loaner pool if you do not have one on-hand.  The timelines for this may or may not work out for your schedule, so I that is a suggestion, not necessarily a requirement, for proceeding.

If it is critical that you have the hardware to test with while your original unit is being repaired, you may want to talk with your RMA coordinator about an advance replacement option.

Hope that helps.

-Andrew

[Alex T]

As I feared, we don't have a 2nd NI 5105 so we will return the scope to NI and try to get a replacement board during repair.

I will ask the sales for details on procedures and I will get back to you.

Thanks for replying.

Regards,

Alex

[TimmTheEnchanter]

Hi Alex,

If you can, please post the SN and RMA numbers here.

-Andrew