 | | Re: lnp communication question
|
|
Hello Tobias, (...) Why do you think there's only 1 byte that can be sent? If your data buffer is longer, bytes are sent one-by-one serially in a packet... (...) look into lnp.c and you will see that both lnp_integrity_xxx and lnp_addressing_xxx are (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: serial port interrupts
|
|
(...) Actually that's what I was intending but I couldn't remember the words at my keyboard. To make debugging easier I will use parallel words that can be merged in later. I was going to use the following debugging strategy: Put the isr init in a (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | due to popular demand
|
|
The HOWTO and other legOS archives will be available (until I get it to sourceforge) at (URL) for the people who wrote and volunteered to serve it- the archives now total something like ~100 meg (several different copies of compilers are in there) (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | lnp communication question
|
|
Hi! When using lnp_integrity_write(&data, length), what is the length argument used for? The data can only be one byte long if I understand it correctly. Can I use the length argument to send an additional byte of information? Is there anyway I can (...) (24 years ago, 14-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: serial port interrupts
|
|
(...) Sounds good Steve, see notes below for some pointers... (...) Absolutely. All we have to do is enable the interrupts on the receiver throw the chars into a buffer. I'd keep the standard FORTH words that already exist so less system source (...) (24 years ago, 14-May-00, to lugnet.robotics.rcx.pbforth)
|
