To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.pbforthOpen lugnet.robotics.rcx.pbforth in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / pbFORTH / 490
489  |  491
Subject: 
RE: Apparent 'time-out'
Newsgroups: 
lugnet.robotics.rcx.pbforth
Date: 
Thu, 9 May 2002 21:45:27 GMT
Reply-To: 
<rhempel@bmts.comNOSPAM>
Viewed: 
2415 times
  
I saw the above post in a thread on lugnet and to me it sounds exactly like the
problem I reported to you recently. All I have managed to determine is that my
hardware/drivers are sound - NQC works fine, Legos also works fine, both of
these are to an RCX 1.0 brick and using the USB tower. I have also seen the same
effect using the Serial tower, but it happens much less often for some reason.

As I mentioned in my previous mail, although the IR comms stops working, the
brick forth software is still functional and powering off and then on again
using the forth power function (via a key press) will start it working again,
and I suspect that the comms initialisation code that is run when the unit
powers back up is the reason for this.

I can't explain why it stops working - I've had a good look through your comms
assembler code, and as far as I can tell it looks sound. To me it looks like an
interrupt or the serial receiver is being disabled, perhaps because of some sort
of buffer overrun maybe.

Anyway I hope this helps in some way, if there is anything I can do to help -
more information etc, please let me know.

Rob,

Thanks for this. I think I'll be able to get to this tonight. I'll have a good
look at what is going on.

Cheers, Ralph



1 Message in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR