Re: RoboEmu2(code simulator)--now with C!
 

I need a new copy of the MinGW compiler because the one i downloaded didn't work. So if you could, give me a link to get the compiler. Other than that the RoboEmu2 worked fine with the default and it should come in handy so i can work from home because the other person programming on the team won't let me in on anything, but when he makes a mistake he looks at me like "ok find my mistake because you know all the syntax because you learned C and i only know bits and pieces." Yeah, my teams a real bunch of great guys aren't they. you should ask me about last year how they screwed me over and you'll see what kind of people my teammates are.

Re: RoboEmu2(code simulator)--now with C!
 

I'm having trouble with the top buttons. The functions I have for them work fine when they are set to the triggers instead of the top buttons. Anybody else have this problem or just me? Maybe I just missed the latest update, I do that a lot. Thanks.

Re: RoboEmu2(code simulator)--now with C!
 

Does this question have to do with RoboEmu2, or the real robot? It sounds like you're talking about the real robot with real joysticks. And if you are talking about your real robot with the new joysticks we have received the last two years, you need to realize that the joystick button called pX_sw_top is the little round button located under your thumb when you wrap your right hand around the joystick handle, and NOT the 1/2 inch round button sticking up from the top of the handle.

I hope this helps. But if I misinterpreted, and you really are talking about RoboEmu2, I apologize for taking up bandwidth.

Re: RoboEmu2(code simulator)--now with C!
 

should've clarified, talking about the roboemu2 program. Just wanted to know if anybody else is having trouble with the top buttons. I'd appreciate knowing wether its me or the program. Distinct possibility its me.

Re: RoboEmu2(code simulator)--now with C!
 

Read: http://www.chiefdelphi.com/forums/sh...ad.php?t=34247

Myabe the same problem... :yikes:

Re: RoboEmu2(code simulator)--now with C!
 

Hello all, I just wanted to add a little bit more clarification to what Chris was saying, since we still haven't figured this out. While using the RoboEmu 2 program, checking the box for the top buttons doesn't seem to work for us. Specifically, we are checking to see if both buttons are being pressed at the same time. Now if we bind the input to the triggers instead, the code works fine. However, it does nothing when we bind it to the top button on the joysticks. I've checked for typos in the reference to the top button several times and can't find anything. I've even tried binding directly to the inputs associated with the top buttons (from the ifi_aliases.h file) and it still did nothing. So I suspect it's a problem with RoboEmu 2 and not our code, but I'd like to make sure.

I would also like to mention that we will be using older 2-button joysticks on our control platform instead of the newer ones. Am I correct to assume that the second button on the top of the stick is the top button, or should we bind the input to another button?

Thanks in advance.

EDIT: And I had not noticed this before, but PWMs 3 and 4 don't show up for us, either, which is the same problem as that other topic.

Re: RoboEmu2(code simulator)--now with C!
 

We will be running the program on our actual bot real soon, I'll update when we do. Then we'll know if its us or the roboemu program.

Re: RoboEmu2(code simulator)--now with C!
 

You mentioned on your website that you were looking for someone with a mac to port in to OSX. I would be willing, but don't have the slightest idea how I would go about that :rolleyes:. So, if you want to explain it to me, I'd be happy to fool around with it and see what I can do, but if I'm going in over my head here then I'll leave this to someone who *actually* knows what they're doing.

- Toby

P.S. - I know very little C, but have a mac with v10.3.8

Re: RoboEmu2(code simulator)--now with C!
 

We ran the code on the actual bot. PWM's 3&4 work as do the top buttons. Everythings going fine for us except for a few faulty PWM communication lines.