unstrobed IO during a burst mode transfer

[notta finger]

I gotta DIO6533 board.

I'm trying to burst 18 bits into the interface and use PCLK2 and ACK2 as low speed select lines to my target hardware. 

The DIO_CONFIG used to set up the 32 bit, burst mode transfer to handle the 18 bit input blows away the state of PCLK2 and ACK2 setup with a port write to port 4..(I've seen the User's Manual chapter 2-6)

Attempts to perform the port write after the DIO_CONFIG lead to device not available to the port write...

Should I wait for ni to improve the DIO configuration software to leave unstrobed general purpose IO lines alone while configuring burst mode transfers?

Should I buy more ni hardware for two bits of low speed control? 

[lrallen]

These lines should work properly according to the handshaking protocol.  Please see the link below.  Are you trying to do some type of custom control using these lines?  If that is the case, you may need to look at getting some more hardware to do this.  Take a look at the link below and let me know if this is how you are trying to use these lines.

http://digital.ni.com/public.nsf/websearch/CDFED34BD265F95F86256E220072B01A?OpenDocument

Regards,

LA

[notta finger]

The burst mode operates on REQ1, ACK1 and PCLK1 as advertised... My problem is I need two bits of low speed output and had hoped to use REQ2 and ACK2 as unstrobed I/O on port 4. My VI asserts a state on REQ2 and ACK2 via a port write to port 4. A DIO_CONFIG follows for the burst mode but I loose the state of REQ2 and ACK2. Attempts to perform the port write after the DIO_CONFIG result in device not available error messages..... I'll consider other hardware..

[Michael.Phillips]

Hi,

I think this KnowledgeBase article addresses your question. One general piece of advice I can offer is that you configure everything before doing any I/O.