Timeout on isoch descriptor

OSR_Community_User-271 · August 22, 2001, 3:18am

I’m developping a measurement system based on a firewire system. To calibrate the ADC Channel we need a 96 kHz sampled 50 Hz sine wave. For the sensors with DAC’s and ADC’s we use Philips AV/C LLY and PHY Chips . The protocoll is based on IEC 61883 AV/C with CIP1 CIP2 Header and 12 TimeStamp and Data Samples per Frame.

To produce this isochrounous data stream for the sensors we use now the Microsoft 1394 Device Drivers from MS DDK. The microsoft drivers are based on OHCI.sys and 1394bus.sys.
We use the DESCRIPTOR_SYNCH_ON_TIME flag for the isoch descriptors.
The problem we have with the Microsoft Device Drivers is that, that the isochronous stream is not continous. It works for 1 sec than we have a timeout. So I get always error on the philips LLY.

Does somebody have any expirence with this kind of problems?

Thank you for your answer

Thomas Grun

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Mark_Roddy · August 22, 2001, 7:27am

winddk\2505\inc\ddk\wxp\storport.h

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Thomas Grun
Sent: Wednesday, August 22, 2001 3:16 AM
To: NT Developers Interest List
Subject: [ntdev] Timeout on isoch descriptor

I’m developping a measurement system based on a firewire system. To
calibrate the ADC Channel we need a 96 kHz sampled 50 Hz sine wave. For
the sensors with DAC’s and ADC’s we use Philips AV/C LLY and PHY Chips .
The protocoll is based on IEC 61883 AV/C with CIP1 CIP2 Header and 12
TimeStamp and Data Samples per Frame.

To produce this isochrounous data stream for the sensors we use now
the Microsoft 1394 Device Drivers from MS DDK. The microsoft drivers
are based on OHCI.sys and 1394bus.sys.
We use the DESCRIPTOR_SYNCH_ON_TIME flag for the isoch descriptors.
The problem we have with the Microsoft Device Drivers is that, that the
isochronous stream is not continous. It works for 1 sec than we have a
timeout. So I get always error on the philips LLY.

Does somebody have any expirence with this kind of problems?

Thank you for your answer

Thomas Grun

You are currently subscribed to ntdev as: xxxxx@hollistech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

OSR_Community_User · August 22, 2001, 1:28pm

Maybe you have a pipeline drain condition.
Are you sure you call REQUEST_ISOCH_ATTACH_BUFFERS often enough to avoid the drain?

Max

----- Original Message -----
From: Thomas Grun
To: NT Developers Interest List
Sent: Wednesday, August 22, 2001 11:16 AM
Subject: [ntdev] Timeout on isoch descriptor

I’m developping a measurement system based on a firewire system. To calibrate the ADC Channel we need a 96 kHz sampled 50 Hz sine wave. For the sensors with DAC’s and ADC’s we use Philips AV/C LLY and PHY Chips . The protocoll is based on IEC 61883 AV/C with CIP1 CIP2 Header and 12 TimeStamp and Data Samples per Frame.

To produce this isochrounous data stream for the sensors we use now the Microsoft 1394 Device Drivers from MS DDK. The microsoft drivers are based on OHCI.sys and 1394bus.sys.
We use the DESCRIPTOR_SYNCH_ON_TIME flag for the isoch descriptors.
The problem we have with the Microsoft Device Drivers is that, that the isochronous stream is not continous. It works for 1 sec than we have a timeout. So I get always error on the philips LLY.

Does somebody have any expirence with this kind of problems?

Thank you for your answer

Thomas Grun

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

OSR_Community_User-271 · August 23, 2001, 4:14am

I don’t think, that i have a pipeline drain condition,
I always get this behaviour, independent of sampling frequency.

The following printout is created by the driver 1394diag.sys,
where i use the original REQUEST_ISOCH_ATTACH_BUFFERS of the NTDDK
The Cycle Time is in the format seconds, cyclecount, cycleoffset

I have inititialized the descriptor with following timestamps.

The Completition Time is printed out in the callback, which is called
after transmit the buffer.

1394DIAG: pR3TempDescriptor->CycleTime = 6:174:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:184:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:194:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:204:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:214:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:224:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:234:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:244:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:254:1266
1394DIAG: pR3TempDescriptor->CycleTime = 6:264:1266
1394DIAG: Completition Time = 6:268:0

Between a cycletime from 0:0:0 to 2:0:0 and from
4;0:0 to 6:0:0 the transmission is always interrupted, even
when i increase the duration.

I have tested different versions of OHCI1394.sys and 1394bus.sys, and I
get always the same results.

1394DIAG: Completition Time = 7:7854:0
1394DIAG: Completition Time = 7:7954:0

Stream is interupted

1394DIAG: Completition Time = 2:292:0
1394DIAG: Completition Time = 2:392:0
1394DIAG: Completition Time = 2:492:0
…
Stream works fine
…
1394DIAG: Completition Time = 3:7892:0
1394DIAG: Completition Time = 3:7992:0

Stream is interupted

1394DIAG: Completition Time = 6:331:0
1394DIAG: Completition Time = 6:431:0
…
1394DIAG: Completition Time = 7:7831:0
1394DIAG: Completition Time = 7:7931:0

Stream is interupted

1394DIAG: Completition Time = 2:292:0
1394DIAG: Completition Time = 2:392:0

The only solution i see now, is that i try to access the OHCI hardware
directly. Maybe you have an other idea.

Thanks for you support

Thomas

----- Original Message -----
From: Maxim S. Shatskih
To: NT Developers Interest List
Sent: Wednesday, August 22, 2001 7:25 PM
Subject: [ntdev] Re: Timeout on isoch descriptor

Maybe you have a pipeline drain condition.
Are you sure you call REQUEST_ISOCH_ATTACH_BUFFERS often enough to avoid the drain?

Max

----- Original Message -----
From: Thomas Grun
To: NT Developers Interest List
Sent: Wednesday, August 22, 2001 11:16 AM
Subject: [ntdev] Timeout on isoch descriptor

I’m developping a measurement system based on a firewire system. To calibrate the ADC Channel we need a 96 kHz sampled 50 Hz sine wave. For the sensors with DAC’s and ADC’s we use Philips AV/C LLY and PHY Chips . The protocoll is based on IEC 61883 AV/C with CIP1 CIP2 Header and 12 TimeStamp and Data Samples per Frame.

To produce this isochrounous data stream for the sensors we use now the Microsoft 1394 Device Drivers from MS DDK. The microsoft drivers are based on OHCI.sys and 1394bus.sys.
We use the DESCRIPTOR_SYNCH_ON_TIME flag for the isoch descriptors.
The problem we have with the Microsoft Device Drivers is that, that the isochronous stream is not continous. It works for 1 sec than we have a timeout. So I get always error on the philips LLY.

Does somebody have any expirence with this kind of problems?

Thank you for your answer

Thomas Grun

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@freesurf.ch
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

OSR_Community_User · August 23, 2001, 6:41pm

Maybe DESCRIPTOR_SYNCH_ON_TIME is wrong?

----- Original Message -----
From: Thomas Grun
To: NT Developers Interest List
Sent: Thursday, August 23, 2001 12:10 PM
Subject: [ntdev] Re: Timeout on isoch descriptor