 | | Re: Using NXT Port 4 EIA-485
|
|
(...) What is not supported about this port in the standard NXT firmware? You can read from it and write to it using the IOMapRead and IOMapWrite syscall functions. Looking at the firmware source code it certainly looks like everything is setup to (...) (19 years ago, 9-Apr-07, to lugnet.robotics.nxt)
|
| |
| | EggArt - a 4-colour Easter egg painting robot
|
|
Just in the nick of time, the day before Easter, I completed building a 4-colour NXT Easter egg painting robot. I started building it several months ago, when I thought I'd have plenty of time before Easter. Of course, at about the 85% complete (...) (19 years ago, 9-Apr-07, to lugnet.robotics.nxt, lugnet.org.us.smart) !
|
| |
| | RE: Using NXT Port 4 EIA-485
|
|
I've looked at implementing an interface for RobotC, but I've always struggled with why bother since there are no applications that connect to it. I wish LEGO had implemented an option to provide a logic level "RS-232" UART on port four. Yes, I (...) (19 years ago, 8-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
(...) As far as I know, there isn't any support for this interface in either the standard firmware or any of the other third party firmware implementations. The interface runs at 921,600 bps so it will be fast enough to be really useful. I am hoping (...) (19 years ago, 8-Apr-07, to lugnet.robotics.nxt)
|
| |
| | Re: NXT external storage
|
|
(...) It may work, but it will be very slow. The NXT runs the i2c ports at only 9600kb/s, so the data will trickle to the NXT very slowly. (...) I think that the answer is yes. (...) (19 years ago, 8-Apr-07, to lugnet.robotics.nxt)
|
