 | | RE: Custom Firmware, IR Problems, and Dead RCXs
|
| (...) Ummm, that doesn't make sense. You know where the midpoint is by knowing the baud rate, and hence the bit width. The only time you need to sample at the beginning of the bit time is to look for a start bit. This is all very basic asynchronous (...) (25 years ago, 29-May-01, to lugnet.robotics)
| | |  | | Re: download .s19 problem
|
| the target of your code is probably the zero page of RAM, where the downloader bootstrap routine lives. so as your code is being downloaded, you're over-writing the hc11-ram-based dl comms code and the host side ultimately fails. fred (...) (25 years ago, 29-May-01, to lugnet.robotics.handyboard)
| | |  | | Re: Custom Firmware, IR Problems, and Dead RCXs
|
| (...) Actually, it's the computer itself that determines the duty cycle. This does mean that you could change the duty cycle, but you should be aware that it would be at the expense of noise immunity and would require a higher sampling rate from the (...) (25 years ago, 29-May-01, to lugnet.robotics)
| | |  | | Re: Custom Firmware, IR Problems, and Dead RCXs (long)
|
| (...) For what it's worth, it's not actually that bad. I don't know the specs on the NPN transistor, but I suspect 1.14A would kill it almost instantaneously. One important factor you've left out of this equation is the 9V battery itself. We often (...) (25 years ago, 29-May-01, to lugnet.robotics)
| | |  | | Re: Custom Firmware, IR Problems, and Dead RCXs (long)
|
| I'm hard pressed to understand why one would need to continually transmit from either the RCX or the tower? Data logging comes to mind, but there aren't many cases where there is a need for this. Listening can, of course, be done continously. The (...) (25 years ago, 29-May-01, to lugnet.robotics)
| |