 | | 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: New Group?
|
|
Hi All, Although I started with NCQ I've used Gordon's Brick Programmer quite a bit. Its neat for putting things together quickly and I use the library import screen a lot to reuse bits from old projects. I'd like to hear about how other people use (...) (24 years ago, 27-Mar-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | 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: light sensor multiplexer
|
|
Hi Stef, sorry for little late. What I am doing is that I need to get the voltahge down and most efficient way of doing that without losing swing ( if you divide you lose swing too) is level shift it and you can do it by putting by Zener. I need (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx)
|
| |
| | 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)
|
| |
| | Re: New Group?
|
|
As the author of GBP I get 3 or 4 emails a week about it and there have been 9,647 hits (I just checked) or the download page since I installed the counter about a year ago. My only problem with the idea of setting up a GBP group is that it might (...) (24 years ago, 27-Mar-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: The sound of train
|
|
I don't have any specifically for trains, but my crane has a two-tone warning sound - you can find the programming info at (URL) The warning sound is generated by RCX1. I'm not sure how difficult it will be to translate this into NQC, but basically (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: The sound of train
|
|
Thanks. Could you show me legOS source? (both steam and diesel), I have no idea about music or sound. I can convert it to NQC, what I am using NQC is that I want to make all my programs that can be used both by RCX and Scout. Zhengrong (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: The sound of train
|
|
Your original post mentioned "warning or alert". Are you looking for train sounds, or warning sounds? The train sounds that Sonnich is talking about is actually the puff-puff of a steam engine, and would be very difficult to duplicate with the RCX, (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: The sound of train
|
|
You used hardware? that is not my hoping. Zhengrong (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: New Group?
|
|
(...) Well, sometimes there's only one way to find out -- build it and see if they come. If we create a group/list for it and it turns out DOA then we can either delete it or ignore it. If there's a user-base for GBP, and you've got (...) (24 years ago, 26-Mar-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Thanks for the info on the electric datalink. It's a clever idea that I never would have thought of myself. It seems to me that you could cut down on your transmission time if you changed the shape of your pulse train. The pauses between bits don't (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: The sound of train
|
|
I guess not - I don't even know what it is. All I have seen of this is some schematics of the electronic circuit for it. And that was 1 years ago I think Sonnich Zhengrong Zang <mikezang@iname.com> wrote in message news:3ABEA0D8.2F4462...ame.com... (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx, lugnet.trains)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
I am not positive about this, but some of the jitter may be due to the mode in which the motor outputs work. They are PWM at 125 Hz, so I am wondering if, when the byte code to change an output setting is executed, the new state setting is placed (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Hi Bernd, When you need it really fast, you sholud use legOS instead of NQC. A program written with NQC uses the LEGO firmware, which is a ByteCode Interpreter. This pogram is interpreted Byte after Byte from firmaware. The firmware executes the (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
