 | | Re: Ultimate ROBOLAB for PICs
|
|
(...) Philo sent me an email to attract my attention to registered trademarks of the Microchip Company among which PICLAB -all capitals. But, as ours is a non-commercial software, and we are using lower cases for the 2 final letters, this should not (...) (19 years ago, 31-May-07, to lugnet.robotics)
|
| |
| | documentation on bt / nxc
|
|
I have two bots set up some meaningful ack and nack conversation. However, when one bot/slave lost connection, e.g. terminated abruptly, the sender (master) does not notice that it indeed lost it. The ReceiveRemoteNumber(INBOX, true, ack) does not (...) (19 years ago, 31-May-07, to lugnet.robotics.nxt)
|
| |
| | Re: Ultimate ROBOLAB for PICs
|
|
(...) We actually worked a lot with the 16F88, which is a really great chip, something like a combination of the 16F628 and 16F819. But we didn't play with the I2C module on it yet. So that must obviously be our next challenge. (19 years ago, 31-May-07, to lugnet.robotics)
|
| |
| | name your nxt
|
|
Hi, SetBrickDataName(str) seems to be able to only change the name of the nxt temporarily. Once the nxt is started, it loses the name assigned thru the SetBrickDataName earlier. Idea? --Elizabeth (19 years ago, 31-May-07, to lugnet.robotics.nxt)
|
| |
| | Re: Ultimate ROBOLAB for PICs
|
|
Great timing. I just bought a PICkit2 to play with the other day. Any chance you already have the I2C slave interface for the NXT for the PIC? That way I can only concentrate on the specific code for a custom input/output device. (19 years ago, 30-May-07, to lugnet.robotics)
|
| |
| | Ultimate ROBOLAB for PICs
|
|
We added a special programming environment for a series of PICs to the Ultimate ROBOLAB site www.ultimaterobolab.com. To distinguish it from RCX-Ultimate Robolab, we called it PICLab. This is a powerful tool for PIC programming. The result is .asm (...) (19 years ago, 30-May-07, to lugnet.robotics)
|
| |
| | Re: robosoccer ball problem...
|
|
(...) It's not ideal for stock LEGO sensors I think, but it might be good to point out to them that the reason it blinks is to make things *easier*. With a source pulsing near a known frequency, ambient conditions are much easier to cancel out. (...) (19 years ago, 29-May-07, to lugnet.robotics.edu)
|
| |
| | Re: Moving NXT motors by hand
|
|
(...) Well, if by "more qualified" you mean "have abused their hardware harder than average, yes :-). Since day 1 I've back-driven the NXT motors by hand, including the magic motor demo (not as efficient with the NXT motors, but it does work), using (...) (19 years ago, 29-May-07, to lugnet.robotics.nxt)
|
| |
| | Re: Moving NXT motors by hand
|
|
(...) Well, I don't want to claim to be an expert, but I'll tell you what I've done. I have a couple remotes that I've been using for over a year, and I haven't had problems with them. One not only uses the rotation sensors, but also uses the motors (...) (19 years ago, 29-May-07, to lugnet.robotics.nxt)
|
| |
| | RE: Moving NXT motors by hand
|
|
Hand crank it alone should be find. As a matter of fact, that's how we demonstrate to kids a generator. However, just to be on the safe side, I would recommend you not to hand crank it when it is hooked onto to the power source, especially when it (...) (19 years ago, 28-May-07, to lugnet.robotics.nxt)
|
