Filip Verhaeghe | 17 Feb 2006 10:21
Picon

Re: Official MDP Email Date Pool


And then today, I missed a phone call. 
I think there's a slight case of paranoia building... Fortunately, I was
able to traced who called me and it wasn't Lego (or unfortunately??).

Filip
http://www.bNXT.com 

--
View this message in context: http://www.nabble.com/Official-MDP-Email-Date-Pool-t1134250.html#a2985869
Sent from the LEGO Robotics forum at Nabble.com.

ondrew hartigan | 18 Feb 2006 06:48
Picon
Favicon

looking to trade technic beams for black technic beams

I am looking to trade all of my colored technic beams for black. Why, well I
have a decent quantity of technic beams but they're so varied in color I can't
build anything sizable. 

  So far I have only gone through my sorted 1x16's but this could evolve into
all sizes. I'm doing this mostly so I can build a couple bridges but also
because this has been bothering me for ages. I actually started out as a technic
builder not a train head. Go figure. 

If youÂ’re looking to stock up on a single color, this is the cheapest way to do
it. 

1x16's <--more in collection i just need to sort
*96 light gray 
* 6 blue 
* 4 red 
* 6 white
*30 yellow

All parts are considered used but are in excellent shape. 

If youÂ’re looking to stock up on a color or colors please email me. I don't
expect to trade everything but if someone helps me eliminate a color or two it
would be a huge help. 
Thanks, 
 Ondrew 
Roj2323 AT yahoo.com

Steve Hassenplug | 18 Feb 2006 18:38

Re: Official MDP Email Date Pool

In lugnet.robotics, Alexander Sack wrote:
> So, I figure Friday.
>
> -aps
>
> PS The email may have went out already and that explains the current slow
> activity AND the lack of responses to this thread! :)!

It's quite.

I think some people are getting e-mails that say "Congradulations...  Don't tell
anyone."

Steve

pisymbol | 18 Feb 2006 20:08
Picon
Gravatar

Re: Official MDP Email Date Pool

In lugnet.robotics, Steve Hassenplug wrote:
> In lugnet.robotics, Alexander Sack wrote:
>> So, I figure Friday.
>>
>> -aps
>>
>> PS The email may have went out already and that explains the current slow
>> activity AND the lack of responses to this thread! :)!
>
>
>
> It's quite.
>
> I think some people are getting e-mails that say "Congradulations...  Don't tell
> anyone."

Bummer...were all of them sent out already?  (can anyone say anything?)

-aps

Steve Hassenplug | 18 Feb 2006 20:48

Re: Official MDP Email Date Pool

In lugnet.robotics, Alexander Sack wrote:
> In lugnet.robotics, Steve Hassenplug wrote:
>> In lugnet.robotics, Alexander Sack wrote:
>>> So, I figure Friday.
>>>
>>> -aps
>>>
>>> PS The email may have went out already and that explains the current slow
>>> activity AND the lack of responses to this thread! :)!
>>
>>
>>
>> It's quite.
>>
>> I think some people are getting e-mails that say "Congradulations...  Don't tell
>> anyone."
>
> Bummer...were all of them sent out already?  (can anyone say anything?)

I don't think all have been sent

Steve

pisymbol | 18 Feb 2006 20:59
Picon
Gravatar

Re: Official MDP Email Date Pool

In lugnet.robotics, Steve Hassenplug wrote:
> In lugnet.robotics, Alexander Sack wrote:
>> In lugnet.robotics, Steve Hassenplug wrote:
>>> In lugnet.robotics, Alexander Sack wrote:
>>>> So, I figure Friday.
>>>>
>>>> -aps
>>>>
>>>> PS The email may have went out already and that explains the current slow
>>>> activity AND the lack of responses to this thread! :)!
>>>
>>>
>>>
>>> It's quite.
>>>
>>> I think some people are getting e-mails that say "Congradulations...  Don't tell
>>> anyone."
>>
>> Bummer...were all of them sent out already?  (can anyone say anything?)
>
> I don't think all have been sent

Thanks Steve for the small tidbit - comes much appreciated.   Man I was really bummed but now there is a small
glimmer of hope (not just for me but for anyone else tracking MDP progress)...

-aps

Andrew Meyer | 19 Feb 2006 01:46
Picon
Gravatar

Motor Analysis

The FLL team that I mentor has several hundred motors, both the new and the old
ones. This wealth of motors got me thinking "Well, out of that size a sample,
there's gotta be two that are perfectly matched, and some that are close. I
should analyze all of them..." So, I built a simple little test mount to run
them in. It has a rotation sensor connected to the motor by the double bevel
gears, using the friction cross-over pins to simulate a load. That...was the
easy part. The part that I thought would be easy (the code) isn't. What I tried
to do is run the motor at power levels 1-5 forward, while recording the sensor
data as data points. Then, I run the motor in reverse, power levels 1-5, while
datalogging the rotation sensor data. This process is repeated three times. What
I wanted all of that to do is calculate the loaded RPM of the motor at each
power level, as a useful and fair method of motor comparison. It doesn't. The
problems I think I ran into:
*integer math
*no absolute value function
*unfamiliarity with Robolab's Investigator section

Is what I'm trying to do a reasonable thing to want to do with an RCX and some
free time? Is it possible? Has anyone else ever done things like this before?

Any and all help will be much appreciated, and I can email code if you let me
know. Also can post pictures of rig if needed.

Andrew Meyer

John Barnes | 19 Feb 2006 03:28

Re: Motor Analysis

In lugnet.robotics, Andrew Meyer wrote:
> The FLL team that I mentor has several hundred motors, both the new and the old
> ones. This wealth of motors got me thinking "Well, out of that size a sample,
> there's gotta be two that are perfectly matched, and some that are close. I
> should analyze all of them..." So, I built a simple little test mount to run
> them in. It has a rotation sensor connected to the motor by the double bevel
> gears, using the friction cross-over pins to simulate a load. That...was the
> easy part. The part that I thought would be easy (the code) isn't. What I tried
> to do is run the motor at power levels 1-5 forward, while recording the sensor
> data as data points. Then, I run the motor in reverse, power levels 1-5, while
> datalogging the rotation sensor data. This process is repeated three times. What
> I wanted all of that to do is calculate the loaded RPM of the motor at each
> power level, as a useful and fair method of motor comparison. It doesn't. The
> problems I think I ran into:
> *integer math
> *no absolute value function
> *unfamiliarity with Robolab's Investigator section
>
> Is what I'm trying to do a reasonable thing to want to do with an RCX and some
> free time? Is it possible? Has anyone else ever done things like this before?
>
> Any and all help will be much appreciated, and I can email code if you let me
> know. Also can post pictures of rig if needed.
>

Did you check here;

http://www.philohome.com/motors/motorcomp.htm

Philippe has done a lot of work which might be of use.
(Continue reading)

Matthew Ruschmann | 19 Feb 2006 04:09

Re: Motor Analysis

> Is what I'm trying to do a reasonable thing to want to do with an RCX and some
> free time? Is it possible? Has anyone else ever done things like this before?
>
> Any and all help will be much appreciated, and I can email code if you let me
> know. Also can post pictures of rig if needed.

I'm not sure how to grab data from the RCX with the 'standard' tools.

However...  as much as I am for wild statistical analysis with a computer, the
easiest solution might be to just use one of those cool LEGO differential axels.
Put one motor on each end and if the third axel spins, then you know they motors
don't match.  You can even put the rotation sensor on the third axel and write a
software program that runs each level for 10 or 15 seconds and checks the third
axel.  Have it beep 'bad' if the motors don't match.  Best of all, this is
something your FLLers can handle with the standard software!

Sorry I couldn't be of any help for doing it the 'cool' way

-----
Matthew Ruschmann
http://matthew.ruschmann.net

Andrew Lea | 19 Feb 2006 12:09
Picon
Favicon

Linking NXT and RCX

Does anyone know if there will be a way - preferably an easy way - to 
get the new NXT  Mindstorms to communicate with the old?  An obvious 
design is to combine the old with the new.  For example, considering a 
"Mars Rover" design, use the old RCX to control the motors in the rover, 
and use the new to control a robotic arm.  The need for this is, of 
course, to increase the number of output ports.

I can think of two methods using sensors and motors, but they both take 
up ports.  (Unlike communicating between two RXCs, say.)

Andrew


Gmane