Debugging

So you've got a problem? Here is a list of things that might help! Before anything else, make sure your Cricket beeps when you turn it on!

Can't start LogoBlocks in PC?

• The path under which you have your programs should have names shorter than 8 characters. An easy ways to correct this is to put LogoBlocks underneath a sigle directory like C:\logob\

Can't find the Interface?

• Check to make sure the Interface is plugged in all the way, and on.
• If you have using a Mac with a USB->Serial adapter, try switching the port on the adapter which the serial cable is plugged into.
• On a Mac, switch to using another serial port by typing "serial-init-alt" into the Command Center.
• On a PC, switch to using another serial port by typing "serial-alt-init" into the Command Center.

Can't download to the Cricket?

• Before trying anything else, turn the Cricket and Interface off, leave them for several seconds, and then turn them on again. Then try again - sometimes this is enough to solve the problem.
• Make sure you only have one cricket on and pointing towards the interface. If more than one Cricket thinks it is being talked to, then downloading won't work!
• Check the battery on the Cricket - sometimes a low battery causes "flakey" behaviour.
• A rarer possibility is that you have too many bus devices connected. If you have over 4, disconnect them, then download and reconnect them.

Can't get CricketLogo in MicroWorlds to work?

• If the program freezes when you try to download, and you are using a Keyspan adaptor, open the control panel for it and make sure that the "emulate printer port" option is enabled.
• If you get a "can't load in startup" error message, try replacing your "-tools-" file.
• If you get a "can't find file or directory" message, make sure you have a "compiler" file in the folder with Microworlds.

Bus device doesn't work?

• It's a very likely possiblity that you have a bad bus cable, just try another one!