08-08-2007 06:58 AM
08-10-2007 07:57 AM
Spec for 6009 says following about DIO:
The default configuration of the NI USB-6008/6009 DIO ports is open collector, allowing 5 V operation, with an onboard 4.7 k
Ω pull-up resistor.I don''t think a pulldown resistor will fix your problem. I'm guessing that you currently have one side of your relay coils connected to common and are switching +DC to the other side of the coils. ( sourcing ) You should consider modifying your external circuit so one side of relay coils is connected to +DC and use the DO to switch a low level to other side of coil. ( sinking )
What you want is to use DO as a sinking output, not a sourcing. That way when the DIO pins are unconfigured and pulled high, it will not cause your relays to be energized.
08-10-2007 09:04 AM
Centerbolt,
Thanks for that input. Pls note that we keep switching the relays on and off at various points in the application. Which means we send both +5VDC and 0VDC to the relays, depending on whether we want them to go off or on.
In light of this, does your suggestion still hold good?
We also observe that the DC signal on PFI pin is spread out into all the 12 DIOs. Is this expected or should we send the device back to NI for repair/repalcement?
Thanks.
08-10-2007 09:30 AM
If one side of relay coil is permanently connected to +5VDC and the DO is high (+5VDC ), there will be 0V potential across coil and relay will not actuate. When DO is low, then there will be potential across coil and relay will actuate. Make sure you are using flyback diodes across your relay coils to protect the DO's from damage.
To make this work you would need to change your wiring to relay coils and invert the sense of your outputs. In sinking configuration, all outputs are active low.
If your DO pins are still in the default open collector configuration, I would expect to read +5VDC on all your DO when device is unconfigured. Remember each output has an internal 4.7K pullup to +5VDC. I don't believe your device is damaged because it is operating correctly when your program is up and running.
08-10-2007 10:36 AM
08-10-2007 11:44 AM
02-05-2008 09:32 AM - edited 02-05-2008 09:33 AM
02-07-2008 08:30 AM
02-07-2008 08:37 AM