Dangerous Prototypes

Other projects => Open Bench Logic Sniffer => Topic started by: sdixon on May 01, 2010, 01:14:09 am

Title: OLS communications problems
Post by: sdixon on May 01, 2010, 01:14:09 am
I'm getting communications errors when trying to capture data with my OLS.  It seems mostly to happen with the larger recording sizes (64K and above) but sometimes with smaller sizes.  It also seems more common with higher sampling rates (100KHz and higher).  The symptom is a dialog box popping up (usually when the progress bar is fully to the right but sometimes part way through) which says
Communications Error
Error while trying to communicate with the device:
...
Make sure the device is:
-connected to the specific port

etc etc
At this point, even if I try more times and the scan succeeds, no data is displayed. (the traces are displayed but they are all ground).
I've tried using lower port speed, reseting the OLS, only capturing one channel, changing the pins I'm using on the OLS (buffered and non-buffered etc) and trying a different computer.  But I'm still getting this behavior pretty often.  I've mainly been using a Windows XP SP3 machine although I've tried a Windows 2000 machine as well. 
Any ideas what is going on?
Title: Re: OLS communications problems
Post by: alanbur on May 14, 2010, 03:59:11 pm
The sample sizes are limited - by default you can capture 32 traces at 4k depth - see http://dangerousprototypes.com/forum/in ... 47#msg4447 (http://dangerousprototypes.com/forum/index.php?topic=505.msg4447#msg4447)
Title: Re: OLS communications problems
Post by: sdixon on May 14, 2010, 05:11:39 pm
[quote author="alanbur"]
The sample sizes are limited - by default you can capture 32 traces at 4k depth - see http://dangerousprototypes.com/forum/in ... 47#msg4447 (http://dangerousprototypes.com/forum/index.php?topic=505.msg4447#msg4447)
[/quote]
That is true as is made clear in the topic you quote.  However, it does not appear that the communications problems are related to incorrect sample sizes.  Even with the appropriate bitstream and correct sample size, the communications problems still occur sporadically.  I've not sorted out any exact pattern although they do seem to be more frequent with higher sample frequency.

And for whatever reason, the communications problems seem much less frequent on a Mac so it isn't much of an issue for me now that I've got SUMP working on my Mac.
Title: Re: OLS communications problems
Post by: alanbur on May 14, 2010, 07:46:56 pm
See http://dangerousprototypes.com/forum/in ... 80#msg4780 (http://dangerousprototypes.com/forum/index.php?topic=545.msg4780#msg4780)
Title: Re: OLS communications problems
Post by: ian on May 16, 2010, 10:00:12 am
I thought of a possible issue with USB->serial latency for boards that have intermittent response problems. If possible, could you please test this solution and see if it helps at all:
http://dangerousprototypes.com/forum/in ... opic=549.0 (http://dangerousprototypes.com/forum/index.php?topic=549.0)

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01462053272session_write_close ( )...(null):0
20.01492184848ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01492185624Database_MySQL->query( ).../DatabaseHandler.php:119
40.05912324336Database_MySQL->error( ).../Db-mysql.class.php:273