|
|
 | | Re: 1.0 brick not responding
|
| (...) Generally, that means the IR tower is working. It's possible the tower has become broken, while it sat in a closet, but that's not very likely. So, knowing things worked before, you may be forgetting something. Make sure the memory is cleared. (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: 1.0 brick not responding
|
| (...) Yes, it flashes. (...) Yes it did work, but it's been in storage for a couple of years. (...) At this point, just download firmware. Once I get the communication issues resolved, I'll do programming. (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) I agree with Steve that the code samples you posted are probably BrickOS. Now to acheive what you want, it might be a waste of power, but you could always blank off the light itself with a peice of black card or thin black packing plastic. If (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) Matt, There are a few ways you can program your RCX. The main choice is if you use the standard firmware, or not. The firmware is pretty much like Windows Operating System. If you use NQC & the standard firmware, you don't need to worry about (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) inside the RCX *directly*, not running programs layered on top of the standard firmware. And if you want to use NQC, you have to work within the limits of the standard firmware (OK, ignoring Dick Swan's firmware, which I've still not been able (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
|
