The HiTechnic Blog is all about HiTechnic sensors and our other products. We will show you how you can build cool models and explain how to program them. There will building tips and programming tips. We will talk about sensor data analysis so you can understand what the robot ’sees’ and figure out how it can respond.
There will also posts with links to articles about other projects out there that use HiTechnic sensors or multiplexers.
The first article coming up will be about an EOPD based wall tracking robot built on a new robot base called the HiTechnic Trike. The HiTechnic Trike is designed so that it can be built from either a 1.0 or a 2.0 LEGO Mindstorms NXT set. The only difference is the part colors and the tires. Here is a preview of the WallBot built from a 2.0 set:


Does it works if you don’t have the EPOD SENSOR?
You can build the Trike and use it as a robot base for your own creations. As far as the Wall follower goes, you may try this with the Light Sensor or Color Sensor and it may work okay. You will have to adjust the program though and it won’t handle variations in ambient light as well.
Why don’t you use the ultra sonic sensor?
The WallBot does use the Ultrasonic sensor to detect the inside corners. For tracking the wall the Ultrasonic sensor is much slower and has a lower resolution than the EOPD sensor.
My PF/NXT-Aragna wouldn’t be possible without your IR-link!
( http://www.youtube.com/watch?v=zd0lsrUdvz0 )
I planed a lot more models with the IR-link so I have a stock of it now.
Help! I have a question. When programming with the NXT IR link block, I have a problem. (in the form of a question) and ask
loudly: I can set the speed pf motors? (There is no box you with power.) I program with NXT-G
Use the Power Function Extended IR Link block! This block gives you a slider so you can set the power of the PF motors.
Hi everyone!
I have a question about the Tilt Sensor, used in the BallShooter. I followed the code and don’t understand one of the operations. In the LimitHVPos block there is a substraction = 60 – zAxis value . Why this substraction is needed?
Thanks!
The z-axis of the Acceleration sensor is used to control the up and down movement of the shooter. In this code I am converting the z axis of the sensor into a usable vertical position. I want 0 for the bottom of the range and 100 for the top. Since the z axis is 0 when the controller is held exactly vertical (z axis is horizontal) this math will give me a value of 60 for the vertical position. If I tilt the controller forward, the z axis value will go up, when it has gone up to 60, the result of the math will be zero and that will be my bottom limit. If I move the controller towards me past vertical, then I can get to the 100 limit.
If I wanted straight up and down to be half way in the range I would have done 50-z but I chose to offset it forward a little as I felt the controller was more comfortable in that position.