 | | Re: legOS Network Protocol
|
|
(...) given (...) lego (...) [ stuff about lego/native collisions ] (...) of a (...) on (...) I was wondering, since people are considering using tags in the LNP frame to signify local to local messages, could we not also use this to "label" non (...) (25 years ago, 23-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) In my brief experimentation with rom_reset(), it does not actually clear the rom- rather it only starts the program over again (in main()). Is this intentional? I get this behavior when calling it from main- when calling it from within another (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) This seems the best approach to me too. My problem is I don't know if I am able to do such a thing :-) (...) I know your site and know you've done a LOT of hard work to understand and explain both RCX hardware and original firmware code. Mario (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) That's what I am doing. Markus. (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Hmm.. with a little hacking you could certainly detect logic errors. The main problem I think would be writing alternative C-Functions for the H8 assembler, which makes up legOS itself. You'd also need to create a simulator engine for legOS to (...) (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) The first instruction (at 03ae) places the stack in on-chip memory, assuming RAME bit of SYSCR is at its initial value of 1. Why not make rom_reset() disable interrupts, then do its thing? That would be the safest thing to do. -Kekoa (25 years ago, 21-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) Well, if rom_reset() gets invoked near the end of your time slice, ROM has no time to reset the OCIA IRQ vector before the next timer tick. I'm not certain about the order in which ROM sets up data areas and IRQ vectors. legOS freely allocates (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Assuming packets without large internal gaps, we could employ a timeout to wait for a packet transmission of unknown protocol type to end. At 2400 bps with 8E1 (LEGO, isn't it?), one data byte has 11 bits, so a space of 1.5*11/2400 s should be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Excellent idea. This would yield the default settings dead-on. (...) Scaling isn't about the final output. The final output is already in the standard format. Scaling is about shifting the raw sensor values displayed by the firmware six digits (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Yes this will be a datagram only protocol for the time being. The LNP will allow us to do things like debugging and remote control. I have also invisioned something like a "shell" running on the legOS that you could either "telnet" in to or (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) Why doesn't somebody finish up the decoding of the ROM, specifically the routine at 14c0. This routine takes the raw sensor samples and converts them to usable values, including handling the temperature and rotation sensors. The standard (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) From what little I remember about the Lego protocol, here are some thoughts. *) On reception, some Lego packets may contain data which look like the beginning of a legOS native protocol frame. Most likely, the checksum would fail (once enough (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) What sort of safety are you referring to? Motors left running? My initial thought was of lost memory or data structures in an indeterminate state, but that would seem to be moot since you are restarting from the ROM, which will have forgotten (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) The interface is specifically datagram only. Dunno about packet reassembly; I doubt it as the philosophy is minimalism. The main advantage I see in it is the ability to change the degree of checking it does on your behalf to ensure packets (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) I suppose we could ask for help also to non-legos owners of RCX and rotation sensors. What if any of us posts a message in the robotics newsgroup asking for some reads of rotation sensors? Raw values can be read with the sandard firmware too (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found (maybe!)
|
|
(...) Exactly. I don't have rotation sensors, either. I think these values were originally gathered from Michael Nielsen's sensors. What's the current status? Is there a patch working for everybody, or do we need some calibration work? It would be (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) rom_reset() does the trick, you'll need to #include "rom/system.h". I'm not sure wheter this is safe when multitasking. (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linux Newbie
|
|
(...) I seriously recommend Linux to anyone with a computer background- it has been over a year since I've had anything (major!) other than Netscape crash. Of course, it is a pain in the butt, and neither my roommate nor my girlfriend are real happy (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linux Newbie
|
|
Thanks to Dave and Joel. I looked quickly at those sites, and there are just what I need. I am off to have a closer look now. I realized that Linux isn't required to program with LegOS, but there are other programs I am looking at using as well. (...) (25 years ago, 20-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linux Newbie
|
|
www.linuxnewbie.org (...) Joel Shafer joel@connect.net (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) OK. I was wrong. I should have better analyzed your code... This definitively prove how long still is my way to get my hands on C :) BTW, I wrote an e-mail to Markus but got it bounced back. Mario (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | HOWTO v 0.1
|
|
Hey everyone. I'd like to announce that I've posted to the web a basic version of a HOWTO for LegOS. If everyone has a chance, please take a look at it and let me know what you think. In particular, take a look at the about the HOWTO section, as it (...) (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
(...) It wouldn't, though. First it gets the maximum of the given value or RANGE_SIZE. That is done to prevent a similar overflow at the low end, even though, with current values, that won't happen. Then, that value is compared against the safe (...) (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Linux Newbie
|
|
Linux is a full blown Operating System, available with full source code. A good place to start is (URL) legOS is built using the same tools that are used to build Linux (GNU compiler and tools, etc.), I don't believe that you need to use Linux to (...) (25 years ago, 18-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found
|
|
Lou, thank you for your reply. (...) This should work. (...) This seems wrong to me because sets all the STATE_n_VALUE to k-RANGE_SIZE. For now I modified ds_rotation_handler() in this way (two occurrences): // if ( IN_RANGE ( STATE_0_VALUE ) ) { // (...) (25 years ago, 18-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Experimenting with Visual Basic - Learning Edition
|
|
Hello: Just thought that I would post a comment regarding Visual Basic and RCX programming. I am new to using Visual Basic as a programming language. But I decided since the Lego Mindstorms System can be controlled by Visual Basic, I would look into (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) Indeed. I just figured that since the infrastructure would already be there for networking, it would be elegant to use the same for IPC. As you said, they don't actually need to be integrated. Then, there is your point about compiling in LNP (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LNP Repost
|
|
Very true, but lets try hard not to add any more bytes to the header. The smaller the better since the packets are probably pretty small. -Jake -----Original Message----- From: Ben Laurie [mailto:ben@algroup.co.uk] Sent: Saturday, April 17, 1999 (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LNP Repost
|
|
Those are some really good points, but I am still concerned about the complexity and overhead of implementing IPC on the lego. Since resources are so limited it might just be easier to use shared memory and semaphores to communicate. On the other (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Linux Newbie
|
|
Here is a silly question, but you guys are the right ones to answer it... compliment I think :) I need to find a "What the hell is Linux" webpage. I _think_ it is a OS that is user developed, and is common on UNIX systems. I run windows 98 and (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) For IPC, each (unshared) connection would take 2 ports (src/dest), so 4 bits at least lets us have 7 IPCs (assuming port 0 is reserved as it is in Berkeley sockets, 8 if it is not). I could certainly see having need of more than 3 IPC (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensor bug found (maybe!)
|
|
(...) You've got a point here. What if we hardwire STATE_0_VALUE to the following? #define STATE_0_VALUE (ds_unscale(1023U)-RANGE_SIZE) Or, for a more general approach: #define MIN(a,b) (a<b?a:b) #define MAX(a,b) (a>b?a:b) #define STATE_VALUE(k) ( \ (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor bug found (maybe!)
|
|
I think I might have found a bug in the ds_rotation_handler (direct-sensor.c). The problem arises when the STATE_0_VALUE is checked using the IN_RANGE macro. As STATE_0_VALUE is 1023U<<6, which is about the max value for an unsigned, adding to it (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) Actually, no. On attempt 16, you reserve some more bits further down for the new version number :-) Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) I'd prefer 11111b for broadcast, in keeping with TCP/IP. Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Ir transmission
|
|
(...) Well, in the spirit of FORTH there should be no finite number, just create and destroy them on the fly as and whan you need them. I have been wandering around the internet looking and found that hForth has one already: \ hForth multitasker \ \ (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: LNP Repost
|
|
I personally can't see needing more than about 7 tasks listening at one time anyway. Keep in mind that the resources on the lego are very very small. As far as reserving an address for IPC that would be fine. We could reserve 00000b for IPC and (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) I can see this. but it is starting to feel a little cramped on the ports, though. What functionality is port 0 reserved for? Actually, I was thinking of reserving a host address (such as 0x0) for IPC. I'd probably want to have more than 3 (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor help (some progress)
|
|
Again about my problems with legOS and the rotation sensor. First of all I checked the four values returned by both my two rotation sensor. They are different from the ones inside direct-sensor.c but anyway inside the specified range legOS: (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
I figured that out... Thanks... I am subscribed via email now! Much nicer... I am just too lazy to remeber to go check news groups. -Jake (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
Jacob S. Barrett <jsbarrett@acm.org> wrote in message news:3716681C.D5C8C6...acm.org... (...) You can subscribe to this newsgroup as a mailing list. I would prefer to see it on this group (or less thing to subscribe to) or to have lugnet make a new (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Ir transmission
|
|
(...) I think its around 16 Mhz for the crystal and 4 MHz for the cycle time. I think there is a msec timer buried in the OC1A handler (see Kekoa's disassembly) I agree that we want something to trigger a run flag instead of having to check the (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Ir transmission
|
|
(...) The bytecode interpreter does it, which is what NQC maps to (opcode 43). I'd prefer a timer (or access to a clock) with millisecond resolution rather than a delay because things will get interesting whan multitasking. What is the CPU clock (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
(...) Well, I think your progress so far is very good, I can understand the odd slip-up, it keeps us on our toes. If I get anywhere with the LCD constants for the complicated segments I'll let you know. (...) Because I am trying to reproduce (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | LNP Repost
|
|
I thought it might be good to repost this with some changes... Okay a little smaller... Only a 4 byte header... |0|1|2|3|4|5|6|7|0|1...3|4|5|6|7| ---...--- | 0xF | VER | TOADDR | PORT| FRADDR | PORT| PAYLOADLEN | ---...--- / PAYLOAD / ---...--- / (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) There are indeed many ways to skin a cat...in the end , the effect is the same, but I'm always curious to see how others do things. How many FORTH programmers does it take to screw in a light bulb? Just one, but he has to be the fellow that (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Useful constants
|
|
(...) I have a 4Ah lead acid battery for mine too! Remember to fuse it just in case... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: rhempel at bmts dot com ---...--- (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I am not in position right now, time-wise, to contribute to the LNP, but I am very interested, and may have time to contribute soon. In the mean time, I'd like to keep up with the project. I don't know if you realize, Jacob, but if you prefer (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
Actually, whils I am re-coding things, is there any reason why you didn't do DELAY like this? : DELAY ( 100msec timer -- ) 0 OVER TIMER_SET SWAP ( timer ticks ) BEGIN OVER TIMER_GET OVER > ( timer ticks time>ticks ) UNTIL 2DROP ; I have produced an (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Useful constants
|
|
(...) That is what I intended them for, I just thought that if I put them up here it would save some typing for someone else. I intend my IDE to detect if they are already in the RCX when it starts up, and download them if necessary. The IDE (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: legOS Network Protocol
|
|
This would almost have to be a UDP like protocol just because the RCX has such limited resources and the complexity of adding transmision control to the protocol would be nasty. I really hate news groups, I like having messages sent to me directly. (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor help
|
|
I need some help with legOS and rotation sensors. I compiled and downloaded the demo/rotation-sensor.c program. The behaviour I get on my RCX is not what I expected. When I turn the sensor clockwise, the LCD toggles between 0 and -1, while (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Ir transmission
|
|
(...) Alas, I only used the firmware timers available as core RCX firmware calls. I can look through Kekoa's disassembly to see if there are higher resolution timers available ( I think the motor timers might be useful ) In general, NQC hooks in (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Useful constants
|
|
(...) <snipped constant descriptions> John, These constants are indeed useful, but would make the resulting srec file pretty big. I have tried to make a TCL script to allow a sort of macro substitution. You can always load the constants after the (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) John, Thanks a lot for this catch. Sounds a lot like the email I exchanged with Kekoa regarding power down mode and external stacks, but that's another story... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) OOPS, that SHOULD read 0x0080 since the mode is a BYTE value. Overzealous urge to get content into the website is to blame. For the light sensor, I generally use the percent of scale mode. My website has a page on tricks with the light sensor (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Sounds good. Does it provide a stream interface or datagrams only? My faulty memory suggests that it might be the latter. If the network implementation supports packet reassembly (packets larger than MTU), there may not be a need for a stream (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I too may be interested in this, although probably only the higher level stuff ie I'm not too sure how good I'd be at interfacing with the IR. Anyway, I had a look around and I found some references on a protocol layered on top of IP called (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Ir transmission
|
|
(...) Perhaps EMIT? would do (...) I'm nearly done with my NQC to pbFORTH port of the IR proximity detector, but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC). I expect it isn't critical but the current detector works so well (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Useful constants
|
|
\ I still need to figure out how the datalog and transfer progress \ segments work, I'll be spending some time inside Kehoa's disassembly I \ think BASE @ HEX ( codes for POWER_GET ) 4000 CONSTANT pwrOnOffButtonState 4001 CONSTANT (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: firmdl error
|
|
(...) [Luis sent me the .srec file so I could take a look at it.] The problem is the length of the first line of the srec file. The first line is 80 characters long, which is too long. The cryptic error message is because the line passed into the (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
..and now I have the answer, after extensive grepping around Kekoa's disassembly and the pbFORTH .ASM files. SENSOR_READ should return only the bottom byte, the call to 0x14C0 only returns a byte so the high byte contains garbage (actually it seems (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | firmdl error
|
|
Can anyone here help me out with this error? I have no idea where to even begin. When downloading my binary (light-brait-with-debug.srec) I get the following error message: [usr@cs liv]# legOS-0.1.7/util/firmdl light-brait-with-debug.srec (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
More information: (...) CONSTANT is working - easy to check by doing RawLight . which prints 1 (...) This last line is the problem, if I use a SENSOR_MODE of 80 as in TRACKER.TXT then I get a SENSOR_READ of 0, if I use SENSOR_MODE 0 then I never get (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
(...) I am just dabbling at the moment, trying a few words to try and get them debugged. In order to fully port the SpeedBot (currently in NQC) I'll need multitasking... (...) Oh, good - I wondered if I'd got versions mixed up somewhere. It would be (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) AhA! Another victim within my clutches!!!!! Glad to hear you are trying things out, John. The more questions I get, the sooner I can get a FAQ out to help with the common ones. (...) That's a good sign, at least. (...) You have obviously had (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | SENSOR_READ doesn't return 0
|
|
I have been experimenting with the latest version of pbFORTH (102) Which announces itself thus: hhii hForth H8/300 for RCX RAM Model V1.0.0 by Ralph Hempel, 1998 All noncommercial and commercial uses are granted. Please send comments, bug reports (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: legOS is great!
|
|
(...) Luis, this would be great. Obviously I don't have anything at all to contribute at present moment, but will do as soon as I have something worth to be shared. (...) Yes please. I wait for your URL. Thanks Mario (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS is great!
|
|
(...) I'd love to set-up (and even host) such a depository. However, at the moment, I don't have much to contribute. As I'm working my rear-end off right now, that should change by friday, but :-) (...) Yeah. I was thinking about a HOWTO, in fact. I (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS is great!
|
|
Last weekend I finished setting up my PC (win 95) to use legOS. It took some more than a while to be ready, but now I'm absolutely happy with it. legOS is simply great and I'm very intrigued with it now. I'd like to thank Markus L. Noga and all the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Installation trouble with Linux
|
|
My system is a Redhat 5.1, i586. I had some problems installing the LegOS. Here are the steps I took. 1. I successfully installed binutils, unpacked the legOS-0.1.7 package. 2. I installed the egcs-1.1b package with the exact options given in the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | PS
|
|
As an addendum to my light message, I checked direct-sensor.h, and the numbers there seem to work out just fine. Could this be a compiler problem on my part? Just another thought- Luis ###...### "They call the faithful to their knees to hear the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | light values?
|
|
Another question before I call it a night- under LegOS 0.1.6, light-sensor values were restricted to the range 0-100. Under 0.1.7, I'm now getting a max value (pointed straight at a light bulb) of about 263, or once even 272. 255 would make sense to (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Updated Win32 toolchain
|
|
I've put an updated Windows 95/98/NT H8/300 cross-compiler, based on EGCS 1.1.2 (basically, the EGCS 1.1.2 release plus Mumit Kahn's Win32 patches, plus a couple of source hacks), on (URL) - this time, I've bundled in enough to compile without (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: floats
|
|
Thanks, Kekoa. (...) Well, as it appears I don't have much of an option, I'll stick to ints then :-) -Luis ###...### "They call the faithful to their knees to hear the softly spoken magic spell:" "There's no place like home... There's no place like (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: floats
|
|
(...) The errors you see are due to the fact that there is no hardware support for floating point. The compiler substitutes calls to the software equivalents, which do not exist; hence the linker errors you see. The math routines that do exist are (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | floats
|
|
When I try to use a float in my code, I get a compiler message somewhere along these lines: <begin error message> ../code/light-brait....t-brait.c: undefined reference to `__floatsisf' ../code/light-brait....t-brait.c: undefined reference to (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) legOS has a software solution built-in - when you are ready to quit, hold down the on/off button and press the 'prog' button. Hope this helps! Cheers, Richard (25 years ago, 9-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Web based LegOs compiler for the underprivileged?
|
|
I recently downloaded a program for the palm pilot that displays up to date movie times and locations based from perl parsed data from movies@yahoo.com It is a great program, but getting and setting up Perl on my system was a real pain. Luckily (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: loading s/w
|
|
(...) I skipped something here. The assumption I made is that you want to load new custom firmware. If you want to load the Lego firmware, find the Firm0309.lgo file in your Mindstorms directory, and load that into the RCX exactly as you would (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) I belive LegOS breaks firmware deletion, in the sense that the "delete firmware" opcode is not supported by the IR routines, but I could be wrong about that. If you are using an AC adapter and no batteries, the easiest thing to do is to turn (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I observed the same phenomenon, only I was using gcc-2.8.1. I never did find out what was wrong, but I assumed it might have something to do with the new libgcc stuff which appeared in 0.1.7. I eventually got working by installing egcs-1.1.1. (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) Have you tried the firmdl program in the utils directory? You might need to recompile the executable manually, as on my system it gets compiled for the h8 :) And there's an environment variable that you can set RCXTTY or something - if you (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | xanim plays mod files
|
|
The new version of Xanim (xanim2801.tar.gz) will play the mod files on the Lego MindStorms CD. (URL) hosted LegOS embedded - cool! (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | loading s/w
|
|
After successfully downloading and running tm-and-ir.srec (Linux host), I cannot download to it any longer. Upon power up, the LCD displays LEGO!5 and I can select any other program slots. I could just re-load firmware in '95 but I don't want to (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
OK, I have some more information now. When I build 0.1.6 in my new environment it works fine. 0.1.7 and the snap exhibit the problem. The problem is that when using tm-and-ir, the 'view' button (which is supposed to send the message "Hello World") (...) (25 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) The helpful folks on the crossgcc mailing list told me that this error indicates that no libstdc was found, so no binary could be generated for the target (not host) platform. Since legOS provides a replacement library, there is no problem (...) (25 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
This site is quite useful: (URL) found it via ftp.cygnus.com/pub/crossgcc. I hope it helps you out. Cheers, Vic (...) LANGUAGES="c (...) that (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
I got everything to build using egcs 1.1.2, but I am having problems with the tm-and-ir demo (after modifying it for the new execi syntax) which make me think maybe egcs is not generating correct code. I used the build instructions at (URL) did use (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I did not have this problem. Sounds like Fortran. Did you 'make LANGUAGES="c c++"' or just 'make'? The latter makes the Fortran stuff, too. Remember that if you specify LANGUAGES when building, you should specify the same value when (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I got the same message, and your reasoning about the content of the message sounds AOK by me. But then I did a make install, and that crudded out on me, with the message In file included from ../../../egcs-1.1.2/...com.c:198: (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
I have. I got the same message. I assume it is part of the test suite. I just bit the bullet and did a "make install" anyway, and it works fine. I take it as saying that it cannot generate an executable for the host platform, which would be true, (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) Has anyone successfully built the above target using egcs-1.1.2? My attempt failed in libiberty: ... configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [configure-target-libiberty] Error 1 (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: FORTH editor/IDE
|
|
(...) Yes, I forgot to turn it off after first downloading the firmware, and getting called away to do something else. Luckily they were rechargeables... (...) Thanks, I'll try it. I will be spending more time with FORTH over the next few weeks, (...) (26 years ago, 4-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Ir transmission
|
|
(...) My next project is to port the IR proximity dectector originally posted by Mark R. David (markdavid@mediaone.net) in sort-of-Spirit code which I reposted in NQC whan I had got it working. It is the best performing detector I have found so far. (26 years ago, 4-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: NQC tutorial available
|
|
(...) "if (Random(100) == 0)" used to be a compiler error, but version 1.2 of NQC is smart enough to generate a temporary variable to hold the random number. A trickier problem is Sleep(). Sleep(Random(100)) parses just fine. Since Sleep() is just a (...) (26 years ago, 31-Mar-99, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: NQC tutorial available
|
|
(...) I think Mark is waiting for me to release NQC 1.3 - which is where SetWatch() gets added. In the meantime, you can define it yourself within your source code... #define SetWatch(h, m) asm { 0x22, (h), (m) } Dave (26 years ago, 31-Mar-99, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: NQC tutorial available
|
|
Mark, In the section on "Display", you mention "Setwatch()" is available in V2.3. Any guess when this will be available? Thanks, -Phil (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Re: cputs / argc,argv / snapshot
|
|
Oops. Did I say David? That's what you get for speaking on the phone and typing simultaneously. I meant Dan, of cause! (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | cputs / argc,argv / snapshot
|
|
Hi, I implemented a cleaner cputs(). Should work with all compilers, also 20% smaller. I went ahead and implemented argc/argv parameter passing for execi as well. This prompted a bugfix for memcpy, which I did create. As I was at it, I also merged (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
