R283 HOKUYO LASER
Maxbotix Sonar Sensor
Maxbotix (Testimonial)
Maxbotix
Maxbotix Sonar Sensor PDF

It has both!?! Great!!! But sounds like it is not really NC... Did you test it with a Volt-Ohm Meter (VOM)??

You want this Switch to be NC, because Looking at the VEX Manual, Pages 7-18 and 7-19, the Micro Switch is mounted low enough, that the Switch is Depressed, making the NC switch Open. This lets you "drive" the robot, until the "floor", drop away, then the Switch becomes "un-depressed" and returns to "normal", and since the switch in now a NC switch, it "triggers" the "Tag/Emergency Stop Sensor" (Analog/Digital Ports 9, 10), which will cause a 2 Second Pause, and will let you back away.

Vex
MythBusters Test the VEX Robotics Design System - Page 1
MythBusters Test the VEX Robotics Design System - Page 2

MythBusters Test the VEX Robotics Design System - Expanded Article - Page 1
MythBusters Test the VEX Robotics Design System - Expanded Article - Page 2
MythBusters Test the VEX Robotics Design System - Expanded Article - Page 3

Vexplorer
Vexplorer Update!

I want to Document the Vex Controller's connectors in a consistent way. Unfortunately there seems to be some confusion about wiring....

There seems to be different ways that the Regestered Jack (RJ) numbering is documented.

Wikipedia (as of 26-AUG-2007) has them documented one way with the entry RJ11, RJ14, RJ25, and the Opposite way with
4P4C modular connector (incorrectly known as RJ9) and the Ethernet Twisted Pair Wiring standard TIA/EIA-568-B.

Vex Labs has the RJ on the Vex Controller documented like the "RJ11, RJ14, RJ25" article above.

Multi-Point Messaging structure like the SAE J1708/J1587 Large Diesel Engine Specification.

Each Vex Controller will have an Identifier (ID) that is unique so that Messages Can be Sent and Conformations of Received Messages can be Received.

The Vex Controller Program will have at least two section (Modules), which will be called Processors. The Processors will be Called the "Communications Processor" and the "Control Processor". The Communications Processor will Receive Messages from the Hardware Linkage (Network) and the Processor either pass the Message to local "Event-driven finite state machine" if Message is for the Local Processor, or Pass it on the Hardware Linkage (Network) to the next Communications Processor.

The First Module, (Communications Processor) will Send and Receive Messages, To and From the Other Vex Controllers. Messages that are Targeted for the ID of the this Vex Controller will be sent to the Second Module (Control Processor).

http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-607.pdf

I am moving this Vex Site to Drupal, so it will be easer to update.... Static Web pages are very Time Consuming...

The old "off-site" links are still to the Left.. My "last" Static Page is http://vex.markoverholser.com/index.html.

Please bear with me....

MarkO