 | | new legOS HOWTO and note from our sponsors
|
|
This is just a minor update to the HOWTO- it discusses the new C++ support in CVS, how to access CVS, and links to the new kernel documentation. As usual, it can be found here: (URL) plug: I'd like to note that the past several releases of the HOWTO (...) (24 years ago, 29-Sep-00, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | New Kernel Documentation
|
|
Stig Nielsson has written excellent documentation on the internals of the kernel. I learned a heck of a lot going through it- I think this makes Stig our new designated kernel expert :) Anyway, you can read it here: (URL) you have any comments or (...) (24 years ago, 29-Sep-00, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | C++ support in CVS
|
|
Hey, everyone- Thanks to the patches Pat Welsh posted last week, C++ support is now in the CVS version of legOS. Pat made a number of changes to clean up the makefiles, so everything will compile if you aren't using gcc 2.95 and/or don't plan to use (...) (24 years ago, 21-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: c++ classes
|
|
Hey, everybody. I'm going to try to patch and build this this weekend. (ADSL line goes in today, so it becomes suddenly more feasible to build and test with gcc 2.95.) However, if anyone else has already done that, and can test these (particularly (...) (24 years ago, 8-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Using the rotation sensor as velocity sensor
|
|
Checked in to CVS. Thank you again, Jochen. By the way, for those of you who may want to check it out, I've disabled it by default in boot/config.h (as we probably should with rotation sensors) so you'll have to go in there and uncomment it (...) (24 years ago, 8-Sep-00, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: Blockin LNP calls
|
|
(...) Sorry, I was using an unsigned char variable, this was just a remnant of some testing I did..... I tried a lot of variations ;-) (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) Yes, the problem is on the host PC (running Red Hat 6.2). What I cant figure out is how identical code works fine if I instantiate the wrapper class in a simple demo app, but once I try calling it form within my CORBA server, it blocks on (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) From the statement "data is received by the RCX" I assume you have this problem on the host system. What OS are you using? Also, how does your lnp_logical_write() routine look like? Eddie C. Dost ecd@skynet.be (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) ,testaddress, 8); It shouldn't be the real problem, but are you sure about the port paramenter? How about: result = lnp_addressing_write...estbuffer, testlen ,testaddress, testport); Bye, Paolo. --- Maier's Law: If the facts do not conform to (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
HELP! I'll ellaborate a little on the details of my previous posting: My code (removing some CORBA detail) looks like this: I have a class "nanOrbDemo_i" which has the following constructor: inline nanOrbDemo_i(){ if ( lnp_init(0,0,0,0,0) ){ cout << (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
