No!!!!!!!!!!

[rbayer]

InnovationFIRST just posted the new RC default code and I'm not happy. First, it seems to use PBASIC 2.5, which doesn't exist according to google. Ditto on the use of the C-style (similar to switch) select commands.

Not only that, but it won't even tokenize correctly under the most recent STAMP software (1.33).

I'm hoping it's some kind of sick joke to make people like me hyperventilate, but it looks genuine. Depending on what happens in the next few days, this may mean I have to completely gut RoboEmu, not to mention un-teach all my mentees old PBASIC.

http://www.innovationfirst.com/FIRST...umentation.htm

[sanddrag]

That is horrible. Perhaps the game can be easily won using the default code?

What does the Programming Reference Guide say?

And what about autonomous mode? Does the code indicate we will need to use it?

Sorry but I'm not a programmer but I'd like to know about these things nonetheless.

[rbayer]

OK, between the periods of being passed out from the aforementioned hyperventilation (), I've done a little research. The programming guide says to refer to BASIC stamp manual 2.0c. I just looked through the entire 353 page thing and there's not a single occurance of the word else, or any reference to select...case constructs. The latter appears very similar to the QBASIC syntax, but that's another matter...

Also the $PBASIC directive doesn't seem to exist and the documentation completely ignores it, even though they do explain the $STAMP directive.

Given that the new RC code is dated 12-18-02, it seems really odd that they didn't post this earlier.

Anyway, as I said before, the default code doesn't even work anymore.

After reading the rest of the documentation, I'm a little calmer, as it says EduBot code and Full-size RC code are completely interchangeable, meaning RoboEmu should still work, at least with code written under the "old" style.

Finally, there references to autonomous mode appear to be copied-and-pasted straight fromt the EduCode, so it doesn't really give anything new away. It is definately there though.

[Alphawolf829]

im confused.... can we still use the old program style? or only that program and the edurobotic program?

[rbayer]

Originally posted by Alphawolf829
im confused.... can we still use the old program style? or only that program and the edurobotic program?

The edurobotic program is the old style, so my guess would be yes. (rhyme unintentional. I swear.)

[Alphawolf829]

lol I guess the only way to be really sure is to test...

[josh_johnson]

I looked at the code and i think that this will be easier to program with than the previous version. It also suggests automation which will be fun as well.

But now I am going to have to print the new programming manual.

[sanddrag]

Originally posted by Alphawolf829
lol I guess the only way to be really sure is to test...

Or wait a few more hours.

[Alphawolf829]

actually just spoke to a friend says he straightened it out have to wait an see though...

[Morgan Jones]

I should hope the appropriate software comes in the KOP. This new syntax could be very useful if we are given something that will tokenize it...

[Jnadke]

How to Program the Robot Controllers

The extra commands are the last 2 pages of the manual, although some more explanation would be nice...

[rbayer]

Originally posted by Jnadke
How to Program the Robot Controllers

The extra commands are the last 2 pages of the manual, although some more explanation would be nice...

Yes, they are there. I know that. The problem is that it says to refer to the BASIC Stamp manual for more information, but the manual doesn't have anyting on DO...LOOP,SELECT, etc. I even have the same version they are referencing (2.0c).

Unless there's something brand spanking new inside the KOP, I'm not sure how any of this is going to work.

[Noah]

Also, if you look at lines 468 - 479

if rc_sw5 = 1 then p3_y = p3_y MAX 127
if rc_sw6 = 1 then p3_y = p3_y MIN 127
if rc_sw7 = 1 then p4_y = p4_y MAX 127
if rc_sw8 = 1 then p4_y = p4_y MIN 127
if rc_sw9 = 1 then p1_wheel = p1_wheel MAX 127
if rc_sw10 = 1 then p1_wheel = p1_wheel MIN 127
if rc_sw11 = 1 then p2_wheel = p2_wheel MAX 127
if rc_sw12 = 1 then p2_wheel = p2_wheel MIN 127
if rc_sw13 = 1 then p3_wheel = p3_wheel MAX 127
if rc_sw14 = 1 then p3_wheel = p3_wheel MIN 127
if rc_sw15 = 1 then p4_wheel = p4_wheel MAX 127
if rc_sw16 = 1 then p4_wheel = p4_wheel MIN 127

According to my manual (version 2.0c) THis is also illegal. The only thing allowed after a then is an address that program control will be shifted to. Personally, I prefer this way, but last time I tried it she didn't work...

[cybermind]

Ok, I am trying to calm down now that I realize that I am not the only one who is stunned by the default program!

The IF Statements are all wrong, the PBASIC 2.5 directive is not supported on the latest PBASIC Stamp Editor, Where in the manual is the SELECT command?, or the DO...LOOP. I am not going to argue that I rather program in this "new" language, it seems simpler, but umm... if it can't tokenize then isn't it kinda useless?

What do they expect the programmers to do? On top of autonomous mode are they going to have us make our own tokenizer too?

What is going on? I thought I would have this programming thing under control!

[rbayer]

I just sent off an email straight to Parallax asking them if PBASIC 2.5 even exists. I'll let you guys know if they get back to me.