For now, I think I'm going to do a release as-is, just so people can start playing with the 2.5 syntax. After I finish packaging it and updating my website, I'll sit down and try to implement as many of these features as I reasonably can. Some of them I know will be easy, but some I'm going to have to do some pretty heavy reading out of the MSDN library to get to work. 1.10 final coming later today. 1.11 coming later this week.

will the other syntax still work, becuase my team is using the old syntax.

If ever REALLY have time.....
 

'--------------------------not directly related-------------------------------
Well, I've got an idea that would take about 2 years to complete. Obviously impossible, but I figured I'd through it out there anyway. I was just thinking - we're given cad softwware, and pbasic, and we can get roboemu/anything else you make, so....

Use pictures created in the cad program (or create your own) - allow ways to define joints, and where motors are. Example, I draw a 3d arm with one joint, and then select the motor you drew and define it as pwm1. Then, when you emulate, it runs all the motors, etc. and your robot moves around a field. You could (in the technically possible sense) even integrate sensors - define this line as retroreflective, allow inserting extra objects, etc.

Like I said, not a prayer it'll ever get done, but I thought I'd throw it out there.
'-------------------------end not directly related---------------------------
As for RoboEmu 1.10...Go over your code that checks for too much time between serout command, we have code that serouts frequently (no questions often enough), and serins what should be often enough. We run it, and it goes through the loop many times, quickly, and gradually slows down, eventually stopping with the 'your robot is dead' message.

Maybe you could just put something to turn the serout error on and off, via a menu or some thing. Also, if you run the same code on a faster computer, it does not slow down, but can run forever with out an error. If you move one of the pwm's, even for a very short time (50ms), it will give an the error. What timing does the RC need to not have a basic run error?

As of right now, it's setup to allow up to 1sec of delay. That's FAR more than the RC will ever tolerate, but I figure that it's a good indicator of infinite loops, etc.

Anways, grab the official version from my website or the whitepapers as it changes the timing from 400ms to 1s.

--Rob

Thanks, with the new version, the code works just fine. Now we just need a robot to test it in:) .

Rob,

Thanks for all of your hard work. RoboEMU make our programming so much easier.

Tim Tedrow

another problem
 

not sure where to put this, but:

RoboEmu doesn't seem to be working as far as knowing when autonomous mode is running. Autonomous mode should be indicated by auton_mode = 1. Using debugs (before we even do anything, as well as in other places in the code), I can't ever get your program to say auton_mode = 1. It should change the value of PB_mode to accomplish this, whenver there is a serin just overwrite that variable.

First, please don't post the same thing in multiple threads.

Second, my answer is at http://www.chiefdelphi.com/forums/sh...380#post124380

sorry
 

I apologize, but I wasn't sure which you would bother to check, and I wanted others to see it so they new what was going on (especially if they had the same problem), so I couldn't just e-mail or pm you.

Do check my response on the "problems with roboemu 1.10" forum.

Grand job on the progam over all, by the way; you're a huge help us to all. Being able to test even one part of one program without a robot is more than I ever dreamed of. Keep up the good work.

I just finished writing the code for team 61, and the 2.5 syntax was perfect. The one problem I had was that it all of a sudden jumped into almost a triple time loop speed, and stayed that way until I reset RoboEmu.:confused: Other than that, it was perfect.

Could you also add a function to restart the code you had insted of re opening it?