 | | 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)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
(...) Do you think it is possible to read/write binary and ascii data to this device or is there a special protocol neccessary ? What about bitrate of EIA-485 device ? Is it possible to adjust bitrate to anything more usable (9600, 38400, 115200) ? (...) (18 years ago, 9-Apr-07, to lugnet.robotics.nxt)
|
| |
| | Re: Using NXT Port 4 EIA-485
|
|
(...) 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 (...) (18 years ago, 9-Apr-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
