08-06-2024 03:24 AM
According to this link below it is not possible to turn of excitation voltage for NI9237 programmatically.
Wonder of there is a workaround or a solution for this issue?
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P69oSAC&l=sv-SE
08-06-2024 03:32 AM
Hi tokar,
@tokar wrote:
Wonder of there is a workaround or a solution for this issue?
There are 3 other "workarounds" mentioned in your linked article…
What is the problem that you want to solve?
08-06-2024 07:09 AM
Thanks for your reply.
It feels unnessessay to have excitation voltage applied when the application are not used.
Number 1-3 are not an option for me.
Under "additonal information" it says:
The NI-9237 does not provide a programmatic method for disabling excitation voltage.
I have tried the code in the articel but i get error messages:
Error -200077 occurred at an unidentified location
Possible reason(s):
Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P69oSAC&l=sv-SE
You can turn off the excitation voltage in a few ways:
Note: The NI-9237 does not provide a programmatic method for disabling excitation voltage. Some level of excitation will always be present when the card is plugged into a chassis.
08-06-2024 09:02 AM
Hi tokar,
@tokar wrote:
It feels unnessessay to have excitation voltage applied when the application are not used.
It may "feel unnessessary", but what is the problem you want to solve exactly?
@tokar wrote:
Under "additonal information" it says:
The NI-9237 does not provide a programmatic method for disabling excitation voltage.
I have tried the code in the articel but i get error messages:
Error -200077 occurred at an unidentified location
Possible reason(s):
Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property.
Because the NI9237 does not support to set the excitation voltage to zero…
08-06-2024 09:18 AM
I want to prevent power consumption when the software program are not used.
Of course its possible to remove the power supply to the cDAQ but its unlikely that the operaters will do that.
Its also a safety issue if i remove my bridge sensor and have 5V applyed in an open connector.
If unucky it can be short circuit by misstake.
Its not a big issue but why leave 5V power on when you dont need it.
I tested the code and understand now that only 2,5 - 3,3 - 5 and 10V are valid values
as stated for the hardware.
08-06-2024 09:32 AM
@tokar wrote:
I want to prevent power consumption when the software program are not used.
Of course its possible to remove the power supply to the cDAQ but its unlikely that the operaters will do that.
Its also a safety issue if i remove my bridge sensor and have 5V applyed in an open connector.
If unucky it can be short circuit by misstake.
Its not a big issue but why leave 5V power on when you dont need it.
I tested the code and understand now that only 2,5 - 3,3 - 5 and 10V are valid values
as stated for the hardware.
So, your goal is to conserve the mW of wasted power?