Subject:
|
RE: Palm and pbForth
|
Newsgroups:
|
lugnet.robotics.rcx.pbforth
|
Date:
|
Tue, 5 Mar 2002 19:42:12 GMT
|
Reply-To:
|
<RHEMPEL@BMTS.COMsaynotospam>
|
Viewed:
|
2292 times
|
| |
|
|
> If you changed pbForth to use 2400,o,8,1 instead of 2400,n,8,1 wouldn't that
> make it work with the USB tower? It seems to me like that is what the
> standard Lego firmware expects from either tower. That appears to be how it
> works under Windows, anyway.
Yes, this is very easy to do. I'd have to change the GUI I supply
too, but that would not be too bad...
> > From the pbForth perspective, it seems like it shouldn't matter what
> platform the client software is using. pbForth (imho) should support the
> USB tower regardless of whether it is easy to use the USB tower under Linux
> or not.
It's not pbForth that's the problem, it's the host-side software that I
need to update to use the USB tower.
> Does the standard Lego firmware even know (or care) whether the client is
> using the USB tower vs the serial tower? I'm nearly certain it doesn't. If
> the either tower sends using the right baud rate, parity, data-bits, and
> stop-bits settings then it can understand the data and respond appropriately.
The RCX does not care. That's why I'm about ready to try the Palm IR and get
rid of the tower altogether..
Cheers, Ralph
|
|
Message is in Reply To:
 | | Re: Palm and pbForth
|
| (...) If you changed pbForth to use 2400,o,8,1 instead of 2400,n,8,1 wouldn't that make it work with the USB tower? It seems to me like that is what the standard Lego firmware expects from either tower. That appears to be how it works under Windows, (...) (23 years ago, 5-Mar-02, to lugnet.robotics.rcx.pbforth)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
