Member #119081

Member Since: February 6, 2010

Country: United States

  • Product WIG-10311 | about 9 months ago

    I was able to get this working by assigning a lower COM number (2). Apparently scratch doesn’t read all available COM ports, but only those up to a certain number.

  • Product WIG-10311 | about 9 months ago

    I should also add that on the Windows 7 machine, I tried using the Windows Driver located on this website: http://www.picocricket.com/picoboardsetupUSB.html . That “driver” is actually an executable and I have no idea what it is doing when it is run.

    I also posted to the Scratch Forums.

  • Product WIG-10311 | about 9 months ago

    Hi All,

    I am new to the picoboards but I like the concept very much. Still I am having issues getting it to work with scratch. I have a Windows 7 machine, 64 bit. I downloaded Scratch 1.4 of 30-Jun-09 today, and scratch works fine until I try to do anything with the sensor blocks. At that point, the program hangs and then goes transparent when I try to do anything (give the “Not Responding” message on the top. I can use the task manager to get out of scratch. I have tried restarting the computer. This behavior happens whether or not the PicoBoard is plugged in (exactly the same behavior in both cases). I have also tried with a Makey-makey which I know to be working based on testing it on their website.

    I have tried running scratch as an administration. I have turned off Bluetooth. No USB devices are plugged into the computer when I run these tests. Scratch works fine with a Makey-Makey (but that’s not surprising since it is just passing the equivalent of keyboard commands).

    Exact circumstances of freezing are shown in the images linked below:

    https://docs.google.com/a/seattleacademy.org/file/d/0B4oBpijiYVvpYUY5N1U0dnFENXc/edit

    https://docs.google.com/a/seattleacademy.org/file/d/0B4oBpijiYVvpNU9YRjhpMlRvVGs/edit

    I have also tried replicating the scenario with a WindowsXP SP3 machine. On this machine, Scratch 1.4 does not crash when you try to use the boolean sensor block (eg to read a button press). However, it does not successfully read the button press from the PicoBoard either. It defaults to the case where the button is not pressed, even when the button is pressed. When you try to use the real-time display for any of the “analog” sensors, it crashes.

    On the Windows7 machine, the PicoBoard is showing up in the Device Manager as a USB Serial Port, COM 57. On the XP machine, it shows up as a USB Serial Port, COM 11.

    The PicoBoard seems to work fine on a Raspberry Pi. So it’s not the board which is the problem.

No public wish lists :(