Issue when streaming more than 8 channels
Posted 09 July 2012 - 08:14 AM
Posted 09 July 2012 - 10:26 AM
1. Update to UD driver V3.25 if you have not already, and then update to the latest beta driver:
2. Update to the latest U6 firmware:
3. See if you can cause the same problem with LJStreamUD, or just in your program.
Posted 09 July 2012 - 10:45 AM
Posted 10 July 2012 - 10:55 AM
Posted 10 July 2012 - 11:27 AM
Posted 10 July 2012 - 08:00 PM
Posted 11 July 2012 - 04:36 PM
Posted 11 July 2012 - 05:24 PM
Posted 13 July 2012 - 04:25 PM
Posted 22 July 2012 - 04:12 PM
Posted 25 July 2012 - 04:02 PM
Posted 06 August 2012 - 11:05 AM
Was the root cause for this issue ever found?
I am facing issue which sound quite similar to this...
However, I am using C# instead of java. But have faced similar issue... if I add more than 9 channels to stream it will start to get messy.
I have situation where I need to stream different amount of timers ( 1..4 ) and rest of the streamed channels are analog inputs. I am using 32 bit falling edges or rising edges timer( tried both just to see if that makes any difference ), this seems to be against the instruction mentioned here http://labjack.com/s...ers-guide/3.2.1, but in my tests it seems to work without any issues as long as you have less than 9 or 10 channels ). If I remember correctly I had more issues with earlier firmwares, but with 1.35 this seems to be working ok ( with less than 9 or 10 channels ).
Tried with 1.26 and 1.37 beta firmware as well. For me 1.26 caused other issues with timers and 1.37 performed similar to 1.35 that I am using normally.
Specifically this situation appears when I input square wave for timer with higher frequency ( above 1kHZ ). Could this have something to do with edge detection interruption taking extra time? Scan rate I have used has typically been 2000/sec
However, what I've found is that when I change timer clock to 12MHZ ( from 48MHZ ) this issue does not seem to happen. Could that bring some light why this is happening?
I would like to get extra resolution for timers and use 48M instead of 12M.
I tried to create some test app for reproducing this but cannot get that to fail... so this issue most likely has something to do with my primary app ( Unfortunately, I cannot share that app).
Anyway I am performing streaming in separate thread from UI thread... Streaming thread is defined to be running with high priority, and as said it works ok if timer clock is 12MHZ
I am running in Windows 7 64 bit
UD driver is 3.25 ( tried beta as well but that was not helping )
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users