RoboEmu 1.03

Technical Programming
1

Well, this should be the last of the 20-hour apart releases, but it all depends on how many errors you guys manage to find.

Anyway, it now works with all the code I have, both real robot code and test programs I’ve created. I fixed the offset error gwross pointed out, as well as a few other bugs. See the changelog for full details.

In any event, it’s available, as always, at:
http://FIRSTprograms.tripod.com/Programs.htm

2

One thing RoboEmu needs is some sort of project file which would store the program file names. (Actually, why should we need to specify all the file names at all? It’s all right there in the main program file.) It would also be nice to be able to specify alternate labels for all the inputs and outputs. I.e. instead of PWM 1, it would be nice to see Left Wheel; and instead of Switch 3, Right Goal Lifter Limit Switch would be much clearer. (All this would of course be stored in the project file too.)

3

Good idea. For now, I have a lot of school work to do (national merit application do tomorrow!), but I’ll work on it when I get the chance. The idea of changing names of things is definately on my list of priorities now that you mentioned it. As is project files.

Does the current version work correctly for your program, gwross? I know it runs without errors, but is the output correct?

4

*Originally posted by rbayer *
**Does the current version work correctly for your program, gwross? I know it runs without errors, but is the output correct? **

I’m not sure. I didn’t take the time to figure out which PWM controls which wheel, and which joystick is which, etc.

5

Okay, I just finished the updates and uploaded the new version. I fixed the MFC42d.dll error while I was at it, too. Let me know what you think!

6

Rob,

Thanks for the MFC42d.dll fixes I can now run the program. Now for my bug list:

  1. When I type in a number in the Sensors field and press Enter, the Inputs window closes.
  2. I get frequent Application Errors when opening or changing projects: (“The instruction at “0x7800d307” referenced memory at “0x00411314”. The memory could not be written”)
  3. When I try to run a multi slot program, all the output stay Paused if I have “RUN 1” in the program. (I will e-mail my code to you)

Wish List Item:

  1. Add a “recently used project list” to the File menu.
  2. Show Debug outputs on your screen.
    :slight_smile:
7

Rob,

This is a great program.

I’m having problems opening files. I can open and run the basic DefaultProgram.bsx, which I downloaded from Innovation First. But when I try opening your Cogsquad code I get a program error. I get the same error when I try opening one of our programs. I’m running this on Windows 2K.

What are all the slot fields for in the Open Files Dialog box? I’m entering the program file in slot 0 field.

Thanks,
Andres Teene

8

Andres,

The basic stamp processors has up to 8 slots for programs. All the slots share the same RAM and Scratch Pad RAM space. So be careful in using multiple slots in your programming.

I am also having some problems loading programs. I can’t get any programs to load us WinXP and I get occational Application Errors us WinNT.

9

Hmm… I don’t have any winNT-based computers in my house, so I haven’t tested it on those platforms.

As for the other errors, I’m working on it. Check back later tonight for (hopefully) 1.05, which should fix all the problems.

10

Well, this really blows. For some reason, “Debug” builds work just fine, but “Release” builds die miserably. Unfortunately, I can’t release a “Debug” build because it links against MFC42d.dll instead of MFC42.dll. The problem comes from the fact that MS doesn’t allow the redistribution of the “d” version. At least I have something to do for the rest of the night.