 | | Re: Using NXT Port 4 EIA-485 —John Barnes
|
| | | (...) 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 (...) (18 years ago, 8-Apr-07, to lugnet.robotics.nxt)
|
| | | |
| | | | | 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 (...) (18 years ago, 8-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| | | | | |
| | | | | | | Re: Using NXT Port 4 EIA-485 —Christian Mock
|
| | | | | | (...) Hi, halfduplex is not the problem when connecting the NXT to an external MCU. My problem is the bitrate of 921,6 kbits/s. Simple cheap MCU like ATMega didn't support this bitrate (as far as I know). To add an external devices (e.g MCU+SD-Card (...) (18 years ago, 9-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| | | | | | |
| | | | | | | | Re: Using NXT Port 4 EIA-485 —Juergen Stuber
|
| | | | | | Hi Christian, (...) the RS-485 interface is directly connected to the AT91SAM7S USART, so you can choose the bit rate quite freely. (...) No, it is not necessary, P-Net is just a field bus which seems to be popular in Denmark, there are others which (...) (18 years ago, 10-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| | | | | | |
| | | | | | | | Re: Using NXT Port 4 EIA-485 —Christian Mock
|
| | | | | | (...) Hi Juergen, Yes, I found this night the entries at Lego-Source-Code... and no line about P-NET-Protocol... My first thought was to implement a simple p-net-node at own MCU, but now I can try my own communication from NXT (master) to external (...) (18 years ago, 10-Apr-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| | | | | | |
| | | | | | | | Re: Using NXT Port 4 EIA-485 —Sivan Toledo
|
| | | | | | (...) Does anybody have an NXC program that demonstrates the use of RS485 communications? (18 years ago, 25-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| | | | | | |
| | | | | Re: Using NXT Port 4 EIA-485 —John Hansen
|
| | | | (...) 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 —Christian Mock
|
| | | | | (...) 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 —John Barnes
|
| | | | (...) 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 —John Hansen
|
| | | | (...) 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)
|
| | | | |
