 | | Re: Enhanced standard NXT firmware
|
|
(...) It actually was not a very big deal. I was familiar with the firmware source code since I had looked at it quite a bit since it was released, trying to figure out how to get it to compile with GCC. All the RIC bug fixes were things I figured (...) (19 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) <snipped description> Holy crap John! You've been really busy! For anyone poking around in this forum, I can say that what John has done is pretty significant. I have written my own firmware for the brick so I know how much work must have gone (...) (19 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Enhanced standard NXT firmware
|
|
Over the past couple days I have used the IAR Embedded Workbench to implement some enhancements and bug fixes for the standard NXT firmware. The bug fixes are as follows: 1. RIC drawing code incorrectly checked the size of the OP_LINE structure for (...) (19 years ago, 16-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Connection to Bluetooth
|
|
Dear All, I have spend a lot of time to get connection with Bluetooth using Bricx. I using the latest nxt software! I have connection with the NXT with Bluetooth, I see on the display of the NXT "<>" After starting Bricx Command Centre I get the (...) (19 years ago, 16-Mar-07, to lugnet.robotics, FTX)
|
| |
| | Re: Bricx Command Centre and the NXT
|
|
(...) BricxCC uses the NXT Fantom API layer to communicate with the NXT via both bluetooth and USB. If you have the NXT Fantom drivers installed properly (which, if you can communicate with the NXT via the standard NXT software, you must) then when (...) (19 years ago, 15-Mar-07, to lugnet.robotics)
|
