Home | AVRO Kits | BASCOM | MicroGUI | Co-Pros | Order Info

'AVRO' Single-Chip Stamp

   Parts / Accessories

Dual 7 Segment Display
This HP display is a direct drive from any of the AVROs and with a good light level. The example programs multiplex the digit segments to minimise the pins needed, but not sufficiently to use the AVRO-T13. The required resistors are included.

Small Speaker
This 1.125" diameter device generates good sound for its size thanks to the enclosure. The CD includes a sophisticated PC tool the 'Ringtone Exerciser' for importing RTTTL tunes, modifying, composing, and playing on the AVRO in real-time. When complete, the tunes can be encoded for standalone operation on any of the AVROs and including the Tiny13.
The interface capacitor is included and no audio amplifier is needed for one/two room applications - direct drive is sufficient. If small size is important, e.g. 'refrigerator door open' reminder, then this is perfect. Whereas in other cases, an old PC speaker can make a good alternative - see the manuals.

More Details on the Experimenter and CD

(Available soon)
Optionally Converting to a PCB
Prototyping on a PCB is normally not a good route. But once a Project has been proven on a Breadboard then PCBs are perfect for making that Project permanent.

  Both Real & Virtual I/O Devices are Included

No further purchases are needed to do something meaningful on day#1. The Experimenter even includes a Quadrature Encoder, and many Ready-to-Run Example Programs - the Kits are Complete.

Having Mastered Real I/O, move onto Virtual I/O (or vice-versa)

MicroGUI-Lite is included on the Kit's CD - it is limited in features, not time

The Lite version is limited to one Project, upper left. But the components of that project can be quickly re-arranged or hidden as shown by the two upper right pictures.
The Scope Wizard and the Scope itself are included for evaluation and will not run with actual Projects. But a license costs less than $20 which is more than reasonable for a limited-market product.

One of the Scope's most unique features is tracing 'By Event' - enormous value for Learning.

The bottom picture of a Debug Screen, offers its own unique facility and is fully functional. The Screen can be used in the conventional manner, but in Shorthand mode it offers so much more. Essentially it removes all repetitive data and only displays changes. It also has a read on-the-fly feature where data can be input 'Off-line' and then collected by the project in mSecs.

Without additional PC Tools, the user would be developing code for the Host (our examples use a Parallax BS2), and the AVRO at the same time. During Debug, deciding which code was responsible for a problem could be very difficult.

But by fully developing the Co-Processor using the PC as a temporary Host, the user can then establish full functionality before ever writing code for the intended final Host. That Separation creates two simple tasks from an otherwise complex task.

For Example:
Here the CoPro Exerciser is showing Command Strings for three totally different Examples, and purely for this quick explanation. Normally they would all be specific to just one AVRO under test.

1) Example is a Serial Controller for an LCD, any size, and using an AVRO-T23 or M48 because of pins required.

• 9,1,3 Says Command #9, Locate, 1&3 define the Row & Column
• "Row 1 Col 3" Says Print this text at that Location
• Back to Back Commands (no waiting for completion) is OK, it is using Background Receive, but transparent to User

2) Example is a Stepper Controller and using an AVRO-T13

• 3,100,20 Says Mode3(half-step), 100 Steps, 20 mS Hold-time/Step
• 11,100,20 Says Mode3 +8 says Reverse, 100 Steps, 20mS Hold-time/Step 
• Back to Back Commands (no waiting for completion) is OK, it is using Background Receive, but transparent to User

3) Example is a Serial Buffer on a Data Highway and using an AVRO-T13
    Note that there are 4 Serial Buffer examples, and this is the 3rd most sophisticated

• 1,2,3,4,5,6,7,8,9 is junk to try and confuse the AVRO
• The AVRO is looking for $EE which it knows is the Start of a new Packet of Serial Data
• The '4' immediately afterwards is the Node ID to receive this Packet
• The AVRO #4 collects "Test"

All returned data is displayed in 3 lower textboxes. Only one is shown above, but by resizing there are 2 more. They display vertically aligned representations of each byte received, as Hexadecimal, Decimal, and ASCII characters to cover all situations. 

Copy and Paste
It is so simple issuing new Commands that the AVRO code can be 'fully' tested. When finalised, simply Copy and Paste the Command strings that work, into the BS2/Final Host code. 

Debugging the Co-Processor and Host code separately dramatically reduces the potential complexity - they become nothing more than two simple and separate programs.

Extracted from the manual AVROs as Co-Processors

In the above CoPro examples, it was easy for the user to enter the Row#, "Text", Steps etc. when testing. Here it would be far more difficult because the AVRO expects 3 parameters compressed into a single byte. Hence a tool specifically for RingTone data. A further advantage is that it helps with visualisation when modifying or composing.

At the CP end there are two ready-to-run programs for most AVROs (this is a fun project). The 'RT-PC' programs just follow commands that the PC sends down the shared Serial Cable. This way the user gets to hear exactly how they will sound before loading them into the associated AVRO 'RT-Mem' program that plays directly from its own memory.

How and when they are selected to play is up to the User. Using BASCOM's IR code makes a very neat solution for activating on demand using an IR Remote. Sensors for Light, Proximity, Switches, Temperature etc are equally suitable. Or using Background Receive to queue a whole sequence of Tunes is another alternative.