|
|
 | | Re: Trains, DCC, and pbForth
|
| In lugnet.trains, Ralph Hempel wrote: <snip> (...) Now here's a thought--a truly automated layout, such as the following-- The RCX has sensors (either light or magnetic/light (as Jeff Elliot made up) to detect the trains as they pass) connected to (...) (21 years ago, 21-Nov-03, to lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | Trains, DCC, and pbForth
|
| All, As I've mentioned before, I have a version of pbForth firmware for the RCX that allows you to control trains modified with DCC controllers. The benefit of pbForth is that you can write, test, and debug your application interactively using (...) (21 years ago, 21-Nov-03, to lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | Re: Multiplexing 4 touch sensors on an RCX input port
|
| (...) (apologies for delay - my server decided to stop talking to lugnet for some reason, hopefully now fixed) (...) Errm, probably 2.1.0 (but I don't have it immediately to hand at the moment - that's the name of the directory on my computer with (...) (21 years ago, 18-Sep-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | Re: USB tower fast firmware download
|
| Trés bien! (...) (21 years ago, 14-Sep-03, to lugnet.robotics.rcx.pbforth)
| | | | | Re: USB tower fast firmware download
|
| (...) Here's a picture showing BricxCC parsing pbForth (with syntax highlighting, of course): (URL) I'm still working on the console and script downloading. John Hansen (URL) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.pbforth, FTX)
| | | | | Re: leJOS & BricxCC news
|
| (...) Yes, it would be nice, plus the two or three unused sensors... I'm happy enough with the LDCC firmware as a DCC encoder (pleased as punch, really). But it "would be nice" if it were implemented as a library or patch to an existing brick OS (...) (21 years ago, 11-Sep-03, to lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth, lugnet.org.us.indylug)
| | | | | RE: Multiplexing 4 touch sensors on an RCX input port
|
| (...) Ian, Great to see that you are having success with pbForth! I have a couple of questoins: 1. Which version are you using? 2. Are there any features you REALLY wish were available? 3. Do you have any stories or code to share? Ralph ---...--- (...) (21 years ago, 10-Sep-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | RE: leJOS & BricxCC news
|
| (...) OK, I've looked at your wish list and have the following comments with respect to how I see the pbForth implementation of DCC. 1. How important is it to have more than one port with DCC capabilities. The reason I'm asking is that it "would be (...) (21 years ago, 7-Sep-03, to lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | Re: leJOS & BricxCC news
|
| (...) Hmmm. I was seriously considering writing a leJOS package to support the LDCC IR Protocol. (Here's why: (URL) ) What capabilities were you going to add? Depending on your timeline, you might convince me to try FORTH. (21 years ago, 7-Sep-03, to lugnet.robotics.rcx.java, lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | RE: pbForth & ROLL
|
| (...) John, As always, it depends. ROLL can sometimes be recovered gracefully, but not always. If you ROLL more than the stack depth, you'll shift some RAM that you probably don't want to shift - like the pbForth image itself. In that case, there's (...) (21 years ago, 6-Sep-03, to lugnet.robotics.rcx.pbforth)
|
|
