Mindboards

fuzzball27 wrote:...If it didn't there wouldn't even be a raw value option in NXT-G for the touch sensor. thats impractical...

Sorry, I forgot to answer this part.

Why not? The touch sensor block can be used for many other sensors. The block is simply a block that gives you access to the analog values of the port's analog pin. Normally people might just use the boolean value, but there is no reason to not use the RAW value. The reason that it is there, is that the code that the block represents, has access to the RAW value, so why not make that user accessible?

fuzzball27 wrote:Any progress on the car?

Yes, actually. The car itself is almost built. (The only thing left is exact spacing for placement of the NXT parts, I just guessed based on some LDraw parts.) In other words, the car is built, it's waiting for me to buy an NXT set and attach it.

Here is a 16-bit jpeg of the car:
It is called the Scarlet Stryker (or "SS" for short).

Picture links: Full-size, Smaller (what you see above).
You can PM me with your email and I can send you some much better pics, I just quickly threw those up there for this post.

Hopefully, some LDraw models will be available soon. I am very new to the program, so progress is slow, but I have the basics down. The only major obstacle is my object database, which I can't seem to update. Some vital parts are missing, and since I don't know how to update my parts list, I'm stuck. On the bright side, my car is built almost entirely out of existing parts (at least, they exist in my database). Exceptions (that I know of) include the treads on the wheels, and parts of the wheel graphics themselves are missing. Anyhow, I'll try to get some prints-creened models up soon.

- Stryker

Thanks for the info Matt. (I'm obviously new to advanced programming and the likes)

Here is the master program It is designed to have a stick on each end of the NXT like a remote control. To reset the sticks to their original position, just push the nxt left/right button. It definitely needs some major tweaking, but its a decent base program. I suggest using NXC though, because NXT-G has much larger file sizes and is jittery
Its well worth the time to learn C type.

your program seems to consist of 4 or so MyBlocks, which obviously can't be opened on just anybody's computer. Could you perhaps post a printscreen of your program? (File -> Print; Print as an HTML from there, I think. Then just search for HTML files, organize them by date created, and you're good to go.)

- Stryker

P.S. My car's LDraw model is missing a few pieces. Namely this one:

Color Family: Black; Exact Color: Black; Category: Technic; Element ID: 4540065; Design ID: 41669

It can be found by going to LEGO's Pick-A-Brick page and punching in the above info. If I can get the LDraw part for that, then I'm good to go. Otherwise....

haha. Sorry about that. I'll just post the my blocks on here:

Thanks!

- Stryker

And the rest:

sorry I haven't posted on here in a while I've been really... busy.

I've been flipping back-and-forth between programming in NXT-G, programming in NXC (for the NXT), and programming for the Nintendo DS, so my world is really messy.

At any rate... This topic has sort of been abandoned. I found out that it would be much better to just use rubberbands, because the other method involves rapidly switching the motor between stalled/coast/powered/coast/stalled etc., which burns out the motors. Real fast.

I will eventually come up with a design that doesn't do that, but it will probably just be rubber bands or something.

Anyways, have a nice day!