 | | c++ classes
|
|
Dear legOSers, I have written a set of c++ classes for manipulating sensors and motors within legOS. The classes include: A) Sensor, a base class for accessing sensors B) LightSensor, derived from Sensor, but uses the LIGHT function to get values C) (...) (24 years ago, 8-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Using the rotation sensor as velocity sensor
|
|
Looks solid to me, and I appreciate the effort to isolate all the code with #defines- hopefully, most future feature additions will be similarly controlled. If no one objects, I'm going to check this into CVS this afternoon. Thanks a lot, Jochen... (...) (24 years ago, 8-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | Using the rotation sensor as velocity sensor
|
|
Hello, For my own project I need to measure the velocity at which my robot is moving. I finally patched the legOS kernel to get accurate values. I think that others may profit from a good velocity sensor. The velocity is given in rotation ticks (...) (24 years ago, 8-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IRPD sensors and LegOS (long)
|
|
Well, I worked on it a bit and added two routines: TurnTo(int New_Direction) => Figures the quickest way to turn from the current Direction to the new one. Retrace(int N) => Retraces the last N number of legs of it's journey. Change the #define LEGS (...) (24 years ago, 30-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IRPD sensors and LegOS (long)
|
|
Since IRPD doesn't use the upper half of the sensor range (above 512), it looks like it could easily be multiplexed with a touch sensor. Has anyone tried this? (I would try it myself, but I haven't bought an IRPD [yet!].) (...) -- ___...___ $50,000 (...) (24 years ago, 30-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | IRPD sensors and LegOS (long)
|
|
Well, after much frustration and a great deal of help from the very wise Rossz, I was finally able to get up and running w/ DJGPP and LegOS 0.2.4 The first thing I did was write a program to use with Pete Sevcik's IRPD proximity detectors that he (...) (24 years ago, 30-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linking failure when 'making' an lx file
|
|
(...) Sorry about the extra stuff, the linking problem was due to the compiler trying to find the above link "___ucmpsi2". When I used h8300-hitachi-hms-nm I could see all the methods and links in my code, and this was the only strange looking one. (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Linking failure when 'making' an lx file
|
|
Hi Can anyone tell me why I'm getting a linking failure when trying to compile my C code, in the standard way. The linker is failing to find a fucntion I have defined in my source: /usr/local/crossgcc/...chi-hms-ld -T ../boot/legOS.lds -relax (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) I guess I'm using lnp_logical_write then? That is, I include the standard lib_lnp.h file into my code and then link my app with liblnp.so.....does this answer your question? Is there a way in which I can call lnp_logical_write directly to test (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) No, I meant lnp_logical_write, which is called from lnp_addressing_write. lnp_logical_write is not within the file lnp.c, which I guess you link into your app. This function is supposed to actually write to the serial device communicating with (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
