+1 to this
Personally, I hope this never becomes a feature. Rerun code just discourages taking time to learn to program - whether it be by finding the most efficient way of using a sensor, to developing a system of driving to a certain point based on XY coordinates, and even just the value of grinding out an autonomous. Vex exists to encourage people to get into STEM, it doesn’t promise everything is going to be done for you, and honestly, I think it should stay that way.
+1 to that
I know @OverlyOptimisticProgramer is passionate about this type of program (so he’s slowly but surely working on developing his own version). It can be a great learning experience trying to implement it.
Ability to compile and download from a CLI
@Barin @Carl cough cough jpearman just said rerun autonomous is good and has worked for a bunch of teams… anyways back on track… I’ve been working (well it’s been a side project that’s almost always been considered too buggy to put in a competition and too time consuming to test and fix my many bugs… ) on a rerun code since the end of toss up… the first year I tried programming it completely outclassed me… the second year I got closer but was trying to record what state the buttons were in which meant I had to sacrifice update time due to not enough storage… the next year I think I got it working (but still too buggy to put in a competition) but I was the only person that knew anything about hardware on that team and my hardware is/was too bad/slow to give me time to really work on it… but the key was to count how long each button is pressed or not pressed and then switch rows when it changed… but there was still the problem of channels and the bugs… so this year I have the arrays count how long a motor is at a certain power and switch rows if that value changes… and we got it working… but… wait I’m getting WAY off topic my point is if we add a rerun that’s already programmed in then I know I wouldn’t be half as good at programming and other programmers may have similar stories…
The ability to search for a specific keyword in your code would be cool
Make it actually read sensor values instead of being strictly timer-based. Also, the Cortex can’t be left on all night long.
To clarify for those not familiar with our program: @OverlyOptimisticProgramer is strictly a programmer – one that shouldn’t even come close to doing hardware.
This I second.
I said some teams have successfully used it, that’s all.
RobotC added datalogging last year, one way of using datalogging would be to record the motor control values, this is setup through the datalog dialog and does not require any code, the sample time is adjustable (10mS is the minimum time). You would need the datalog debug window open to record more than a few seconds (I think we use a 4k buffer).
Here is a very old (5 years) rerun program I posted way back, it may or may not work anymore.
@OverlyOptimisticProgramer cough cough I wonder what a certain other person once suggested.
Not sure I understand this request. We can search for any word in the code, selecting a variable or function name and using right mouse click allows you to jump to the definition of that item. What was it you would like to see in addition to this?
@jpearman thanks!
I’ll add it in soon… I need to test my current improvements before making more…
anyways as far as suggestions for robotc, in there is a ringtone to robotc converter for music and it would be really cool if there was a MP3 or other music type to robotc converter… but it’s not that big of a deal as Programmers can do it online… also if anyone has seen the TI basic code for graphing there are commands like pixelOn(Row,column) or some equivalent that would make the LCD have a lot more potential… similar commands would be pixelOff and pixelTest (pixelTest returns a true if the pixel is on and false if the pixel is on)
Another cool function would be an a self navigation program… but then the whole argument of someone who would have otherwise learned from it is just going to use it and not learn comes up again… if you do a self navigating robot, it would also be cool to have that same program be able to DRIVE the robot to that point…
I haven’t done that much research though so there might be equivalents of all of these commands buried somewhere…
also robotc is pretty darn awesome so nice job!
Hardware limitations prevent this. The LCD can only display characters listed here. In extremely simplified terms, the software/Cortex tells the LCD display some character at some position rather than enable these pixels at these positions.
P.S. The VEX IQ Brain’s integrated display supports this in RobotC. Change your platform type to VEX IQ and look at the function library to be jealous.
A comprehensive, indexed, searchable user manual that includes all possible commands, extensive examples, explanations, best practices, etc. I find the on-line robotc manual lacking. Plus, the ideal manual would include not just commands but concepts - such as PID and how it works, troubleshooting code, interfacing with Vex components, how functions work, how tasks work, how to use the competition template (the use of #include). I am the programming coach and not much of a programmer - but I have muddled through by asking lots of questions here, trial and error, internet searches, youtube videos, and learning from other more experienced people. It would be really nice if there was one compendium of information.
FUDGE!
Yeah that was another place I drew inspiration from for that request…
+10 to this… I don’t even mind if the only thing is there is all the commands and what their arguments are…
Auto integration of the accelorometer to get velocity and position in the background.
Function pointer would be a fantastic thing but what I think we need the most right now is better autocomplete and the sorts in the ide. Oh, and multi-file project support, so you don’t have to switch to your main file each time you compile.
CLI support, VCS support, and the ability to integrate RobotC with other editors a la FRC.
I remember tweeting with robomatter folks a while back, but I always wanted the ability in RVW to import your CADded robot and use it on the VEX field. Would change the whole game up and there’s no telling the amount of money I would spend to have that feature.
Better documentation as well.
But in terms of priorities I want
- VCS Support
- Integrability with other editors
- CLI Support
-Upload CAD.
Does any one have any links to other threads about rerun programs? I’m curious to look into it now!
You know James is something like the VP of Robotmatter, not a developer.
My wish list:
- Free
- Function pointers
- Dark theme (which a little birdy tells me would be nearly trivial to “implement”)
- Multiple files, including headers and source files
yes, thatd be fantastic, i hate bright white screens