 | | Re: C standard functions with legOS?
|
|
(...) As other people have pointed out, its not possible to use them straight off. I've written some floating point code for my own use to do conversions between rectangular (x,y) and polar (dist, bearing) calculations. The codes not documented I'm (...) (23 years ago, 27-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) I've been meaning to butt in on this discussion sometime, but I got caught up in things, but better late than never. The source you refer to is probably mine. I wrote a suite of fixed-point math routines for multiplication, division, and (...) (23 years ago, 27-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) An alternative is using fixed point math. There was some posts time ago, with C source for trigonometric functions. If you are interested, I should have links to them, somewhere (or do a `search' :-). bye Bernardo New e-mail: (...) (23 years ago, 26-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) The cross-compiler is set up to not use standard libraries. This is to give more control over the code produced. Also, many standard functions just wouldn't work on the H8. There is a float library (lib/float), which allows use of floating (...) (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | C standard functions with legOS?
|
|
Is it possible to use functions from C standard libraries with legOS, e.g. sin() from math.h or abs() from stdlib.h? They are a part of gcc, but e.g. math.h seems to produce compiler errors. Best regards. Michael Wisse (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lcd
|
|
Yes, if you have three values, just display them like this : cputw((VALUE_1 << 8) + (VALUE_2 << 4) + (VALUE_3)); (...) (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | lcd
|
|
Is it possible to display 2 lcd intergers on the screen at the same time? ie 2 rotation sensors. Thanks in advance chris (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Sensor Commands and legOS 0.2.3
|
|
(...) TOUCH_1 is a macro defined in dsensor.h starting form version 0.2.4. If you don't want to upgrade, here is the code: #define TOUCH(a) ((unsigned int)(a) < 0x8000) #define TOUCH_1 TOUCH(SENSOR_1) #define TOUCH_2 TOUCH(SENSOR_2) #define TOUCH_3 (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Sensor Commands and legOS 0.2.3
|
|
I just installed legOS 0.2.3 under Redhat 6.2, using the RPM's that were linked to in the HOWTO. Everything I have tried so far has worked great, except for getting my touch sensors to work. The documentation I have read said that in 0.2.x one could (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LegOS scheduler questions
|
|
(...) I don't /think/ so, but I don't have time to check to be certain and it has been now literally 10 months since I looked at kernel source. :\ (...) See #1. :\ (...) By design? As many as you can throw at it- there is no hard-coded limit, and (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LegOS scheduler questions
|
|
Folks, This is my first day with Leogs. I just installed Legos, compiled a program and have run it successfully. Haven't got a chance to take a look at the kernel source. I have the following questions and any response will be greatly appreciated. (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | WinLNP issues
|
|
For those who prefer the Java programming language, I've written some classes that may help with LNP. What you need is : the JDK 1.2, the Java Communication APIs (classes for Java communication through the serial port, and my classes located at : (...) (23 years ago, 23-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | More LNP Issues
|
|
Thanks to Rainer for helping me with the stupid compiler bug :) Now that the PC side of LNP is working, I'm having troubles with the RCX side... I've modified the LNP sample provided on the WinLNP page as follows (with the includes trimmed): #define (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: raw touch sensor values
|
|
(...) SENSOR_1 gives you the raw value from sensor 1. TOUCH_1 gives you the boolean value if it's a touch sensor. In fact SENSOR_1 gives you the raw value no matter what type sensor it is. HTH ROSCO (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | raw touch sensor values
|
|
Hello, Can you access the raw touch sensor values in legOS? I know you can do it in NQC but I haven't figured it out in legOS. Thanks in advance, Nate Ridderman (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: error from makelx: address out of bounds
|
|
I've found it. They must be declared as static: static LightSensor s(LightSensor::S3,false); int main(){ ... } Regards. Michael Wisse (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: WinLNP Issues
|
|
Hi Matt, i had the same problem. That's a Microsoft *feature* ;-) that comes with visual C++ 6.0. (This problem is described in the MSDN. If you've got it installed, you 'll find details there.) You have to get a service pack for this compiler. Get (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | WinLNP Issues
|
|
I'm trying to compile WinLNP, and I've run across a baffling problem: h:\program files\microsoft visual studio\vc98\include\...til.h(101) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1786) Please choose the Technical (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
(...) [snip] (...) Can't see anything glaringly obvious, except you've used different priorities for your tasks. As they're infinite loops with no waiting, it's probably better to make their priorities equal. But the best way is probably to do all (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | code
|
|
Hi,I'm trying to run 2 infinate loops at the same time. Is this possible? this is an example of what I'm trying to do. thanks #include <unistd.h> #include <dmotor.h> #include <dsensor.h> #include <conio.h> #include <time.h> pid_t fun_a; pid_t fun_c; (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Declarations in header files
|
|
(...) "extern inline" means that we are defining an inline function, but if the inline function is not used, there is also an externally defined function with the same purpose. So, if you compile without optimization, it acts like "extern void (...) (23 years ago, 18-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | error from makelx: address out of bounds
|
|
Hallo! My question again: I tried to declare sensors global, out of main(): Motor motor(Motor::B); LightSensor s(LightSensor::S3,false); int main(){ ... } make reports an error: /home/micha/legOS/util/makelx test.ds1 test.ds2 test.lx test.ds1: (...) (23 years ago, 17-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Dynamic lists allowed?
|
|
(...) Thanks for your help. The program is running fine now. Would you happen to know if anyone has created this sort of high level functions? If not more people might be interested. jm (23 years ago, 13-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Dynamic lists allowed?
|
|
(...) This should be "struct tNode *next;" (...) After this, any time you want to refer to a tNode, you need to say "struct tNode". Or you can put "typedef struct tNode tNode" and then use the "tNode" as a type like you're doing. (23 years ago, 12-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Dynamic lists allowed?
|
|
Since I just got started with legOs (thanks to 'Extreme Mindstorms'), I'm creating a set of high level utility functions. This one here is intended to display a DYNAMIC list of values, but there seems to be a problem with the use of 'struct' and (...) (23 years ago, 12-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | c++, sensor declaration
|
|
Hallo! I tried to declare sensors global, out of main(): Motor motor(Motor::B); LightSensor s(LightSensor::S3,false); int main(){ ... } make reports an error: /home/micha/legOS/util/makelx test.ds1 test.ds2 test.lx test.ds1: address out of bounds on (...) (23 years ago, 10-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: c++, classes
|
|
Hallo Frank, yes, it helped, thanks. But I still don't understand the background. Normally, in c++ you can initialize your private components in the body of the constructor or with a initialization list, like in your suggestion. Reagards. Michael (...) (23 years ago, 10-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: dll problems
|
|
Nevermind, I figured it out. Apparently some of the programs weren't compiled correctly in the demo folder because some of them worked and some didn't. I was able to recompile some of them and then they would download. Wierd but at least I figured (...) (23 years ago, 8-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: dll problems
|
|
Hmmm.... After messing around with it some more, I'm getting a new error message: "error creating program" . quite similar to the last one but not quite the same. Thought that might help in figuring this out. Nate Ridderman (23 years ago, 7-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | dll problems
|
|
Hi, I'm trying to install legOS 0.2.4 on my rcx from a windows system. I need to use it for a computer programming class I'm taking. I was able to download everything and successfully installed the firmware, however I'm unable to use the dll program (...) (23 years ago, 7-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX Comm via input-output connection?
|
|
(...) There's a couple of other ways to do it (besides the off / float mentioned by others): 1. Have the motor off RCX1 drive a rotation sensor on RCX2. Requires more space & parts. 2. Use LNP (infra-red communication). But requires that RCXs are in (...) (23 years ago, 6-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | OT: Exploration Mars Balloon Tires Part#
|
|
Hello Does anyone know the LEGO-Shop-At-Home part# for the balloon tires that come with the Exploration Mars Expansion Set ? Thanks Tim Goodwin (23 years ago, 6-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: RCX Comm via input-output connection?
|
|
Hi Jakob, Search for "Electrical Data Link between 2 RCXs" thread on lugnet.robotics.rcx.ncq and various threads on lugnet.robotics ((URL) such as "CM-RCX" and more. I'm finishing up a *NQC* input/output VLL lib that supports direct electrical (...) (23 years ago, 6-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX Comm via input-output connection?
|
|
Hi, Jakob, It is possible and discussed here several times. Have a look at this : (URL) ;-) Why not use the search button ? ;-) (...) (23 years ago, 6-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RCX Comm via input-output connection?
|
|
Hi! Does anyone know if it is possible to have to RCXs communicate by connecting the motor outputs of one to the sensor inputs to the other? I have a slight feeling this could burn things due to the high-voltage (relatively) output of the RCX motor (...) (23 years ago, 6-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: c++, classes
|
|
Hi Michael, if you want to use a declarator list in the constructor you have to use the following syntax: /******* Implementation of the constructor ***...***/ LightSensorHead::Lig...ensorHead( const Motor::Port motorport, const Sensor::Port (...) (23 years ago, 5-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | c++, classes
|
|
Hallo! I try to write a class for legOS in c++. The constructor should get parameters for the used ports for a motor and two sensors, which are private components of the class. Then the contructor should assign these given ports to the private motor (...) (23 years ago, 4-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Can you test it for me?
|
|
I made a lx file, but I can't test it, could you help me? (URL) (23 years ago, 4-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: max size of .lx
|
|
(...) I don't know what the max is, but I have routinely worked with .lx files up to about 12,000 bytes, so you should be fine. (23 years ago, 3-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | max size of .lx
|
|
I got a .lx file that size is 9660 bytes, I am not sure if it can be downloaded to RCX, what is the max size of .lx? Zhengrong (23 years ago, 3-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | What difference between 0.2.4 and 0.2.5?
|
|
I am using 0.2.4 now, I want to know what difference between 0.2.4 and 0.2.5 to decide if I need to upgrade it. Br Zhengrong (23 years ago, 3-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Combo sensors (rotation AND light, same input)
|
|
Hi, I've got a way to use a Rotation sensor and a light sensor on the same input, and get reliable, useful values from both. This is for real. See : (URL) was interested if anyone else has done this. Enjoy everyone. Mike Amy (23 years ago, 2-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Neural network for legOS... ??
|
|
(...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Ser. Col. Only!! I'll cover shipping!!
|
|
(24 years ago, 29-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Serious Collectors Only!
|
|
I'm selling my entire collection for $4,500. There are over 300 sets MISB, and over 200 sets opened but still in mint condition. Over 90% of the opened sets were put together once; and then sealed in zip-lock bags. The boxes of the MISB sets are in (...) (24 years ago, 29-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
(...) If you want to drive directly the motors you should first disable motor handling in legOS (remove CONF_DMOTOR definition in config.h). Then you can create a high priority task that switches motors on and off writing in the motor output port. (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
(...) pulses (...) at (...) would (...) Hmmmm. This should be possible, but it's a bit more tricky with stepper motors - you have to allow for the speed-up and slow-down. Thus just calling motor_speed(50) would have to initiate a task that starts (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
Actually I am trying to control a stepper motor. So when i need to send 50 pulses fast, motor on and off takes same time because there same other tasks running at the same time. So it would be much quicker if I could just call motor speed (50), and (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Assembly in my C-program
|
|
(...) to (...) This should be performed by mapping a variable on top of the memory location, and NOT by inline assembly. (...) What is wrong with speed=0 for off and speed=255 for on? /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Assembly in my C-program
|
|
HI, I was wondering if I could write assembly code in my c-program. I would like to access the motor output port as a digital port and control when it is on and when off (possibly writting something like "mov.b r6l,@0xf000:16"). Or can I change the (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We are going to use this solution. Seems simpler. /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Congratulations! Could you post your source code here, to compare with the solution that we previously submitted to an almost identical question? We use an active light sensor reading in one taks, with a different task bangin zeroes using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
(...) of (...) For the IAR compiler, this should not a problem. The libraries are optimized for minimal size, so we can probably use the standard libraires. And give our students the benefit of a full C lib. /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Neural network for legOS... ??
|
|
(...) Sorry Niels, but I would say just try it yourself, they're not that hard to do, failing that if you can find the source for a small ANN, then that stands a good chance of working, I'm running quite a powerful evolutionary algorithm on mine, (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
Hannes, I got it to work last night. I'm modifying Markus Noga rover.c code (included when you download legos files) to include support for IR port and (passive) light sensor. Great code to look at if you're just learning C/C++. Basically, the (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Commentary below. (...) I must have missed this one the first time around. lnp_logical_write() will block, but it should only block the thread it's called from. Put your send-zero loop in a separate thread and I think you should be set. (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
(...) Huge coincidence that your message should be the first I see after not having read the newsgroup for almost a year. No, as far as I can remember I never got an answer. I am using mindstorms for my final project after not having a chance to (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Running IR in the background
|
|
Hannes, Did you ever get any help with your question (below)? I'm trying to use the IR port on RCX along with light sensor (passive) as collision detection device. Having the same problems you're having. Clayton (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
(...) Not sure of the details, but the linker takes the .o file, and the symbol file LegOS.lds, created during the kernel compile, and produces two files; .ds1 & .ds2, which are then passed to makelx to produce the lx file. So it seems the linker (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) One other possibility is to not use the lx files at all - just stick to the srec format as (I think) LegOS used to (version 0.1.x?). A bit less efficient downloading the kernel all the time, but removes the need to dabble with lx format at (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Declarations in header files
|
|
Hi! This is very technical, but: does the declaration of an "extern inline const void" function really make sense? GCC accepts it, but that is a VERY lenient compiler. An extern function should be definition not have a definition, and 'const void' (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) So in effect, it is dependent on the gcc loader mechanism. Ungh! The idea of using two symbolsrec files: one could be kernel, the other the program. Would make sense for kernel call resolution. (...) I looked at it, and it mainly outputs (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
(...) OK. How are the calls to the kernel resolved? By the makelx program, or by some magical stuff in the linking. I can imagine compiling the kernel, getting a symbol table out, and then when compiling user programs, you use a linker DEFINE or (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Neural network for legOS... ??
|
|
Hi everybody I'm looking for a free neural network library, that I can use with legOS. Anybody knows where to look ?? Niels (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: .lx format
|
|
(...) Look at legOS makefiles. The lx file is generated from two symbolsrec executables linked to different positions. The files are generated with a special linker script "legOS.lds". Maybe you can do the same with your compiler and use the makelx (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
(...) [etc.] Also, don't you use ROTATION_X instead of SENSOR_X once you get the rotation sensor set up on that port? I thought it was something like that. I'd also like to comment that this is dangerous. It's theoretically possible that your sensor (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
yego, The wait_event function takes an event function as the first parameter, not a sensor number. You need something like (forgive any errors - I don't have LegOS available at work) int rotation_event_3(wakeup_t data) { if (SENSOR_3 == data) return (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | code
|
|
Hi, I'm a newbie to c++ and legOS. Here is my code. Do you know what is wrong with it cause I don't. Thanks /* s.c*/ #include <unistd.h> #include <dmotor.h> #include <dsensor.h> int main(int argc, char **argv) { /* turn it on */ (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Library use in LegOS
|
|
Jakob "Fepp" Engblom <fepp@ieee.org> wrote in message news:GAr7Gr.2v3@lugnet.com... (...) handled (...) Each program gets it's own copy (...) Hmmmm. Not sure. Wish I knew more about compiler internals... (...) have (...) It's all custom written - (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS papers?
|
|
(...) I could do with some technical references for my bibiliography, and so after much searching[1], I can reveal that that AUC is Aalborg University, Denmark. Furthermore, most of the authors can be found in the Computer Science department: (URL) (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linking failure when 'making' an lx file
|
|
(...) Syntax error: you are missing a parenthesis at the start, right after the if. But gcc should give a fat error at the ">" sign I believe. if( COND ) STATEMENT; if( (ul_var1 - ul_var2) > sizeof(uchar)) STATEMENT; (...) It is miraculous that the (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Memory Usage
|
|
(...) Having written a few embedded-systems compilers, I must say that using floating point on an 8-bit chip like the H8 is generally considered crazy. The values eat memory, and the libraries drawn in can get really large (at least for a production (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Library use in LegOS
|
|
Hi! Another technical question about LegOS: how are libraries like float handled today? Is there one copy linked into LegOS, or is each downloaded program equipped with its own copy? If I would use a different compiler, with a different set of (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: pass by refrence or value?
|
|
Some basic facts about C semantics: As already stated, globals MUST be volatile if they are accessed by more than one thread, otherwise reads and writes can be out of sync. What are the types of the variables involved? Scalar values like integers (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Obstacle detection : infrared sensor ??
|
|
(...) We have done this in C using LegOS (it is much easier to get it off the ground in nqc). The principle is simple: * Attach the light sensor in front of the brick, close to the IR tranceiver. preferably in a low position, since you want to (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | .lx format
|
|
Hi! I am presently helping some PhD students here at my university prepare the labs for a real-time course using LegOS. As part of the course, we want our students to experience a modern development environment for embedded systems, and have (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Obstacle detection : infrared sensor ??
|
|
(...) Yeah, I built a robot and programed it whith a nqc program that someone else wrote. I dont't remember who and I don't have any links, but I do remember how it worked The rcx would send out a infarad message every cauple of mlseconds and a (...) (24 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Obstacle detection : infrared sensor ??
|
|
Hey.. I don't know if this is a LegOS question, but here it goes... Is it possible to detect obstacles via the infrared sensor, before you bump into them ?? Like measuring reflection of infrared light or something... If it is... how ?? can anybody (...) (24 years ago, 24-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
(...) Are you doing the if() in some kind of loop, or an event function? If the button isn't pressed at the exact time you happen to execute the statement, it won't work. It's difficult to help debug your code without seeing your code 8?) ROSCO (24 years ago, 22-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
(...) havent followed the whole conversation here, but if ur doing an "if "test and it doesnt hit when it should, you might consider displaying the TOUCH_2 variable on the display just before the "if" test, it might not be what you think it is! (...) (24 years ago, 22-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | video game type thing...
|
|
Well, it still doesn't work even with the if(TOUCH_2){} instead of if(TOUCH_2 == 1){} . Any ideas? Nick H. (24 years ago, 22-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: More than one Source C file
|
|
Please ignore this message, Dyanimc objects :) - Ciaran (24 years ago, 20-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | More than one Source C file
|
|
Hi, I'm trying to compile together several C++ objects, each of which is contained in a seperate .c file, with a seperate header file, in GCC, I'd just use gcc foo.c fooa.c foob.c -o out.exe ... or whatever, how do I adjust the legos Makefile to (...) (24 years ago, 20-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Code
|
|
Chris, there's a CVS repository at SourceForge. Go to the legos page at legos.sourceforge.net. You'll need update access if you want to check anything in, but anyone can check out the latest, greatest source (or any previous version). HTH BTW, I (...) (24 years ago, 19-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Code
|
|
Is there a legOS code repository where LegOS users share code? (24 years ago, 19-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: ROM Firmware size limit? Firmdl bug?
|
|
(...) does the (...) them (...) web (...) when (...) rcx_comms (...) have (...) I've not done latest merge (few lines in firmdl.c), but I've modified the rcx_comms to make it win32-working (100%) inside legOS. I will send ASAP modified firmdl source (...) (24 years ago, 17-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: ROM Firmware size limit? Firmdl bug?
|
|
(...) I remember when I added support for larger firmware files, there was a merge that took place to get my changes into the LegOS version of firmdl. Probably Cygwin support got lost during this merge. This should be put back into LegOS for sure, (...) (24 years ago, 17-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: ROM Firmware size limit? Firmdl bug?
|
|
(...) Hmm. Quad speed downloading in Version 3.1 doesn't seem to work under Cygwin on W2K (though single speed does). It always returns either a 'write: permission denied' of 'bad ir link' error (which one it is seems to be random!) , even if the (...) (24 years ago, 17-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: ROM Firmware size limit? Firmdl bug?
|
|
(...) Get the latest version of firmdl and/or the latest version of LegOS. (URL) (24 years ago, 15-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
I'll try that. I thought it was something or other like this. I'll post when I'm at least partially successful. (24 years ago, 15-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
Nick, The TOUCH_x macros are boolean - they return true or false. You should be testing if (TOUCH_2) {....} HTH ROSCO (...) (24 years ago, 15-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
I just got new batteries for my RCX, so I just did an actual test. I didn't get very far. I don't believe that it is registering the touch sensors. Here's how I had it: if(TOUCH_2 == 1) { do this and that and that; } What's wrong with it? I should (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
Or pid_t pid1 = execi... Philippe (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
(...) Shouldn't (...) No, the returned process id is an integer (int) I believe, you just replace it with int pid1 = execi .... for example :) - Ciaran (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
It probably should. But why does it say that "pid1" is undeclared? Shouldn't that be taken care of in tm.h or unistd.h? (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Kernel proposal - message passing and signals
|
|
Hi, I have been poking around in the legOS kernel and it appears that there is no formal way to pass messages between tasks - only shared protected resources through semaphores. I intend to modify the kernel to add the features descried below. Note (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
(...) <-- Cut -- > (...) Shouldn't thist say kill(pid1); ? - ciaran (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: video game type thing...
|
|
I worked on that. I'm having trouble with "execi()" and some stuff related to it. Here's the offending area, but not the entire program: int main(int argc, char **argv) { pid1=execi(&startup, 0, NULL, 1, DEFAULT_STACK_SIZE); MYexit = -1; cputs("x"); (...) (24 years ago, 13-Mar-01, to lugnet.robotics.rcx.legos)
|
