What program should I write?
 

Well, nobody has complained about any errors in RoboEmu 1.06, so I'm going to assume it works for everyone (let me know if I'm wrong!). Therefore, I know have a lot of free time, so I want to start another project that people think might be helpful.

Anyway, here's a little explanation on each of the choices:

• RoboEmu for Linux--a linux port of my PBASIC emulator
• RoboGUI for Linux -- a linux port of my program creator
• Computerized Robot Control -- ability to control the robot using a laptop, etc. Seethis post and the replies for more info.
• YADP -- yet another dashboard program for Windows (I already wrote one for Linux).
• Other -- let me know if you have any other ideas.

I'm open to just about any project, whether its a handful of lines of code or mult-thousands of lines (like RoboEmu and RoboGUI), I'm willing to do it if people have the desire for it. Also, it doesn't have to be something to help programmers. If you have ideas for helping the electrical, pneumatics, mechanical, animation, chairman's, etc people, I'd be willing to do that too.

--Rob

P.S. If you haven't checked out RoboEmu, RoboGUI, or gDash (Linux dashboard viewer), they're available at http://FIRSTprograms.tripod.com/Programs.htm

How about a Basic Stamp II Editor/Download Controller that runs native on a Mac under OS X?

I've tried a the expected kludge answers (i.e. stampw.exe running on Virtual PC v5.0 under OS X 10.2, with a Keyspan USB-serial adapter with din-9 to DB-9 cable, etc.) with frustrating results. Anyone up for writing a better solution (and don't say "get a PC" - I'd rather shove a stick in my eye)?

- dave

Running native under OS X? That shouldn't be too bad. After all, it's just BSD. Hmmm.... maybe for MacOS 8, as that's what I have on my OLD desktop (read: 33Mhz). Excellent suggestion, dlavery.

I sent you an e-mail with enough suggestions for updating RoboEmu 1.06 to keep you busy for at least an hour. :)

An hour? At LEAST! They're good suggestions, though, and I'll probably try to incorporate as many of them as I can without gutting the whole program. I especially liked the idea of indicator bars for the PWMs, and lights for the relays. I'll probabbly just write a few more ActiveX controls to handle all the messy drawing stuff. The Paused PWMs staying at 127 is a know issue, but I have absolutely no idea why it does this. My only guess is that it has something to do with my thread syncronization(sp?) stuff. Anyway, I've got an MIT application to finish by Thurs, but after that I'll get back to work on some of this stuff.

As for the computerized Robot Control, codenamed RoboCon, it's coming along. As soon as I get an OI from the school, I'll begin my initial beta tests. Yes, that does mean I have the code mostly done. Again, look for an initial and very buggy release (like the first releasees of RoboEmu) by early next week.

As for a Mac OS X PBASIC IDE, I'm currently planning on writing a Linux version using gtk+, which should also compile on OS X, but I really am not that familiar with MacOS higher than 8.1. From what I've heard, though, I shouldn't even need to modify the code at all. Anyone want to confirm/disprove this?

--Rob

Thanks for the update. Please add the LED outputs for each joystick.

I said "an hour" since you seem to be a very fast programmer. It's amazine that you can get all these programs done so quickly.

Good luck with MIT.

For each joystick?!?!?!?!?

Do you mean relay? I hope so, 'cause otherwise I'm completely lost and confused. Maybe those seven cans of Coke this afternoon wasn't such a good idea....

Robot feedback LED's on joystick ports 1 & 3, pins 5, 8, 9, 15, Variables Out8-Out15.

What about something that allows you to program from a USB port? Seeing as more and more laptops are going "legacy-free", it's hard to find a new laptop suitable for programming.

Your team gets new laptops!? We have an old Pentium-100 with a 640x480 screen running Windows 95. It doesn't even have USB. It has to be plugged in because the battery is dead. And sometimes it crashes for no reason. :(

PS: For you lucky teams with new laptops, I think you can get a PCMCIA to serial or a USB to serial adapter.

Other teams have their own laptops for programming?:( We have one for web-design and we technical people have to buy/use our own (actually, Rob just "borrowed" his laptop from another high school--that was a few years ago and we're not sure if they're missing it yet).

Macs
 

How about a RoboGUI and RoboEMU for Mac OS9. Maybe even that DashboardSpec thing for mac.

Apple gave our county a grant and we all get shiny new iBooks.

Too bad there isn't a useful program on them, no office, no .avi player. Also they are locked down so we can't load anything on them, no freeware, no Parallax, etc.

Yes it would be great if we could use these for programming, but common nonsense has prevailed again

I gave that one back and you know it! Sam's point still stands though: I have to use my own.


OK, back to my actual responses:
Unfortunately, the Stamp processor doesn't understand USB electrical/signaling protocols, so you'd need to convert it to RS-232 anyway.

OS 9 would be almost impossible as I don't have any OS 9 computers. If I ever get around to doing a Linux port, it should compile under OS X, as well. Speaking of laptops, I'd be perfectly willing to try my hand at an OS 9 version if someone wants to donate a Mac laptop to me....

Currently, I'm working on RoboCon, the computerized robot control, but as soon as that's done, I'm going to port as much of my stuff to Linux as I can.

In any event, RoboEmu 1.07 is done, so check it out if you have the time.

--Rob

Actually, the laptop I use is my own personal machine. I have a nice, new laptop that I bought, and it doesn't have serial. Right now, we're stuck with an old NEC Pentium 90 that has no CD or battery. It's also Win95, but with an 800x600 screen.

Gimme a few weeks and I might be able to port your unix programs to OS X (and port it to cocoa while I'm at it)

OS 9 programming is worthless. That OS is dead to developers anyway.

A coupla suggestions for Emu...
1. Key mapping to joysticks (i.e. joystick 1 = W/A/S/D for movement, Q/E for wheel, TAB and LSHIFT for trigger/top button; joystick 2 uses NUM8/NUM4/NUM6/NUM2 for movement, NUM7/NUM9 for wheel, NUM1 for trig, NUM3 for top, etc...)
2. Possibly an actual robot graphic for simple movement (PWM1 is right wheel, PWM2 is left wheel)
3. Buttons to start/stop simulation and switch modes (rather than those drop-down menus at the top)

And for GUI...
1. Drag-and0drop interface
2. Ability to change properties after creation (switching PWM from being controlled by Joystick 1 y to being controlled by joystick 2 y), so that it is not necessary to delete and re-create
3. Ability to enter own code (the user can enter their own PBasic code and conditions in a text box); i.e. under properties for a switch, code can be typed in

Other than this, EMU and GUI are great programs. Keepup the good work!!!

hmmm....interesting..... btw rbayer, awesome programs you create, they've helped a lot this past year (it was our first year)

as far as laptops go, I just used the old 133MHz machine I have stashed in my room, as our school hasnt donated anything and checking one out each and every day would be a pain

hmmm.....what do I want to see as far as new/updated programs? well first, I'd like to mention the ongoing (dont hurt me for bringing this up! :p ) debate about next years controllers. While FIRST has not released anything official, I have heard from several reliable sources (as have many others) that there will be a new controller this year, and with it a different programming language......granted without definite information or details, you cant begin coding for the upcoming year, but do realize that spending time to port to the MAC (if it may become an issue, but then again, its another good challenge lol), may not be all that worthwhile, excluding any modifying of last years code (in which case there probably is A computer still around capable of programming it) or any new robots using an old control system *shrugs* a nice side project to have tho

Ok, well on to what this thread is ACTUALLY about lol, features that should be changed and or added...... DEFINATELY add a button, slider etc to be able to change between normal, autonomous, paused and running, etc. Also, a feature that would allow "reload code from file" would be very helpful. Last year when I was doing autonomous with 4 or 5 files, when I had to change one timing and had to select and reload all of the files just to update roboemu.....which was a bit of a pain. I tried using the project thing so that I would only have to reopen one file, but I had trouble getting that to work 100% of the time. Anyways, a reload/refresh button would help. Plus a few additional debugging tools would help :) Oh, and any thought to having one be able to control one of the joysticks with......an actual joystick hooked up to the computer? just a thought. Well, I've rambled enough for one night, let me know what you think.

Yay for dead thread revivals! Anyways, a few notes:

1. I'm hesitant to do anything to RoboEmu until I get info on what this years control system will be.

2. If it's drastically different, RoboEmu may be scrapped completely as it isn't exactly good software engineering and it would probably be faster to just start over and do things right this time (like use Regular Expressions, etc).

3. I like the button thing. I'll see what I can do.

4. I did some work on a plugin-like interface that would let teams provide a way of graphically showing what's happening with their robot based on RoboEmu's output. The 2.0 core (not released yet, but close to complete) is designed to facilitate uses such as this.

5. RoboGUI needs a LOT of work. I'm aware of the fact and may, at some point, get around to doing some of it. RoboEmu, however, is my first priority since it is far more popular.

6. The newest version of RoboEmu (1.11beta1), which is available at http://www.chiefdelphi.com/forums/sh...threadid=1762, will automatically reload files if you pause the emulator and then unpause it.

7. You have been able to control joysticks using a real joystick for a long time now. It's under the advanced menu, and called something like Bind Joystick. I don't really remember too clearly as it's been a LONG time since I wrote that code and I haven't touched it since.


-Rob

I looked through the thread, and couldn't find the file. Anyways, thanks for being a big part of the programming and FIRST community :)

Hmmm... something weird happened with the copy-paste. The correct link is:

http://www.chiefdelphi.com/forums/sh...threadid=17626

Thanks for the link ;)

I'm sure this will be helpful for our team this year (RoboEMU and RoboGUI has always been).

Emulator for the Microchip controller!!!

The MicroChip SW development tools (free) come with a simulator.

PBasic <-> PIC C
 

I know that many things will not be compatible, but how about a PBasic <-> converter? Especially the PBasic to C converter, which should work out. I personally shouldn't have any problems with C, but it may be useful for others, for training purposes, or for quickly converting old code to code for the new controller.

Re: PBasic <-> PIC C
 

That might work out when the standard code is released.

I'll be up for it if Rob isn't, it'll give me something to do (I'm seriously bored right now :().