Subject:
|
Re: Using NXT Port 4 EIA-485
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Mon, 9 Apr 2007 21:25:58 GMT
|
Viewed:
|
16420 times
|
| |
|
|
In lugnet.robotics.nxt, John Hansen wrote:
> 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 work properly where if you write to the HSOutBuf and
> properly set the HsState and HsFlags values that it will send data and receive
> data into the HSInBuf. What sort of additional support is needed to make this
> interface (more) useable?
>
> John Hansen
Hi John.
I must have misunderstood something I was told a while back which went along the
lines of "there isn't enough time to implement support for this feature".
Perhaps there was some time after all ;)
Do you know how large the OutBuf and InBuf are?
JB
|
|
Message has 1 Reply:
 | | Re: Using NXT Port 4 EIA-485
|
| (...) They are tiny. #define SIZE_OF_HSBUF 128 typedef struct { UBYTE Buf[SIZE_OF_HSBUF]; UBYTE InPtr; UBYTE OutPtr; UBYTE Spare1; UBYTE Spare2; }HSBUF; // HI Speed related entries HSBUF HsInBuf; HSBUF HsOutBuf; The IOMap hi speed buffer is copied (...) (18 years ago, 10-Apr-07, to lugnet.robotics.nxt)
|
Message is in Reply To:
| | 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 (...) (18 years ago, 9-Apr-07, to lugnet.robotics.nxt)
|
15 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
