Group items tagged

It is straightforward to implement an interpreter-like interface, where user commands are transparently compiled, downloaded, and executed.

The Cricket virtual machine is burned into the PIC microprocessor's internal ROM

The user's code resides in a serial EEPROM

Built-in infrared communications routines include a protocol for reading and writing to this external EEPROM, and for asking the virtual machine to begin execution of byte codes already loaded into the EEPROM.

Users write programs for the Cricket in Cricket Logo, a dialect of Logo specialized for the Cricket virtual machine. Essentially, there is a one-to-one mapping between statements in Cricket Logo and primitive functions built into the virtual machine. This makes the implementation of the compiler far simpler than typical compilers.

The infrared protocol includes the following capabilities: Check that a Cricket is present and ready for other commands. Write a byte to the Cricket's EEPROM. Read a byte from the Cricket's memory. Begin program execution from a particular memory address.

we have found that a debugger is not necessary because of the interactive and incremental style of project development that occurs when using the Cricket.

The compiler includes an interactive mode—a text window where user expressions are compiled, downloaded, and executed in one step when the user presses the return key. A portion of the Cricket's memory is set aside for these dynamic programs.

User-level primitive functions compile to one, two, or three bytes of object code for the Cricket virtual machine.

The Cricket virtual machine has two process threads: a foreground process and a background daemon. In most Cricket programs, the foreground thread handles all the work, but for some tasks, the background daemon is valuable. For example, the background daemon can be used to instigate a periodic activity, or take action when some event occurs.

There are hardware-specific primitives for interacting with on-board Cricket hardware. Motor commands set state (on or off), direction, and power levels for each of the two integrated motor drivers. Analog sensor primitives (sensora and sensorb) return a value (0 to 255) for each of the two voltage inputs. These inputs also may be interpreted as digital values using the switcha and switchb primitives. There is a pair of primitive functions for generating tones on the piezo beeper: beep and note, the latter taking pitch and duration arguments.

there is a background millisecond timer that is updated every four milliseconds

One foreground thread plus one background daemon Daemon fires when provided Boolean expression makes false-to-true transition

Set one straightened paper clip aside, you will use it at the end. Bend the two tips of one of the two paper clips as shown.

Put it in through the fuse clip like this, but make sure the notch in the fuse clip is facing out. (The clip has one edge bent inwards. This is the part that has to face outwards). Study this next picture closely.

From the position above, bend the paper clip up and then around the lead of the fuse clip as in the next picture.

Bend the paper clip under the fuse clip...

then up and over the fuse clip:

then around its other lead and you're almost done with the first fuse clip.

First clip -- wire is on the RIGHT side of the fuse clip leads... Second Clip -- wire is on the LEFT side of the fuse clip leads... But remember to make sure the notch in the fuse clip is facing out. (The clip has one edge bent inwards. This is the part that has to face outwards).  Follow all the steps above with the second clip and you get this: