EasyC Wish List

[dcbrown]

Ok, don't get me wrong - we like EasyC, but...

I'm finding that we're using "User Code" more and more within all the routines being written. So I thought I'd start a wish list for EasyC.

1. Defines with arguments and these showing up in the user functions list.
For example:

#define SetLeftWheel( _pwm ) SetPWM(2, _pwm)

Yeah, we could code a routine called SetLeftWheel() that simply calls SetPWM(), but the call stack isn't that large and we could end up wasting a lot of its stack entries on simple redirection. The define just makes it easier for us to forget which ports/pins/interrupts go together to make up a specific feature on our robot. A feature for Pro mode only maybe?

2. Storage classes/qualifiers for variables.

static rom near int lookup[42]={0,8,8,8}; for example.

Another Pro only feature?

3. Global "User Code".

Currently we need to define a lookup table that is created readonly in program memory. We're using user code to do this and then initializing the array within a routine. The routine then must be called to access an array member. We'd like to be able to put some user code into a global area so the array can be used by more than one routine easily.

4. Cut & Paste support

In input boxes and being able to copy out the source lines from the source view window. Or an export function that exports the source lines into a straight text C file.

5. PrintToScreen()

We're using hyperterminal so we can save our debug output to a file easier. It needs \r\n at the end of prints to get to the start of a new line. Unfortunately we can enter "Data is %d mgs\r\n" - we'd like to add the %d format character ourselves and then select the variable. Maybe a check to see if a format selection is already present and then just add the variable to the end of the line? Because we can't output multiple variables per PrintToScreen() call, we've been using the following:

PrintToScreen( "Data1, Data1, Data3\r\n");
user code[ PrintToScreen( "%d, ", data1 ); ]
user code[ PrintToScreen( "%d, ", data2 ); ]
user code[ PrintToScreen( "%d\r\n", data3);]

Maybe if there was a selection box to enable/disable adding the newline at the end. We print out the data this way so it can be pulled into an excel spreadsheet and charted easily.

6. The ability to use the Ctrl key to add to and accumulate sets of code to
cut/delete etc. Select an line item, hold down the Ctrl key and select
another line item, etc.

7. A defined upgrade path from EasyC to MPLab.
As programmers become more adept and comfortable with programming. They should be able to easily grow from EasyC to MPLab and carry their work with them. This would promote quick prototyping in EasyC but support programmers growth to using MPLab. At the moment the transition is abrupt and you have to start again in MPLab. Maybe an Export Project to MPLab function to create the sources/includes and a template MPLab project or instructions for using the new sources and WPI lib from MPLab. (Ok, I admit it - I tried hacking apart the BDS file to do this but didn't get anywhere other than being able to do some fundamental record breakdown/breakout).

I'm sure there might be others. But these are the ones we have at the moment.


DCBrown

[BradAMiller]

Originally Posted by dcbrown

Ok, don't get me wrong - we like EasyC, but...

I'm finding that we're using "User Code" more and more within all the routines being written. So I thought I'd start a wish list for EasyC.

1. Defines with arguments and these showing up in the user functions list.
For example:

#define SetLeftWheel( _pwm ) SetPWM(2, _pwm)

Yeah, we could code a routine called SetLeftWheel() that simply calls SetPWM(), but the call stack isn't that large and we could end up wasting a lot of its stack entries on simple redirection. The define just makes it easier for us to forget which ports/pins/interrupts go together to make up a specific feature on our robot. A feature for Pro mode only maybe?

If you are asking if the defines can show up as user functions, then that would be a nice feature and isn't currently available. If you're asking if you can have defines with parameters, then you can do that by opening the globals window and adding the defines there. You have to put the argument list in the Value column of the Program Globals/Define dialog box. Effectively you do this:

#define SetLeftWheel  (speed)SetPWM(3,speed)

then it works.
The "functions" would have to be hand entered in user code blocks or in assignment blocks (or any other place an expressions is allowed).

Originally Posted by dcbrown

2. Storage classes/qualifiers for variables.

static rom near int lookup[42]={0,8,8,8}; for example.

Another Pro only feature?

Yup, that would be nice. And so...

The next version of EasyC that should be available soon will let you create external functions in MPLab and add them to the linked image. There is already an option to add a header file (.h) so you might try creating those tables in MPLab, then creating a function in the same MPLab module with the "rom" storage class identifier that returns the result to the EasyC program.

It sounds like you know how to do this, but if not, post something and we can try to help you out.

Originally Posted by dcbrown

3. Global "User Code".

Currently we need to define a lookup table that is created readonly in program memory. We're using user code to do this and then initializing the array within a routine. The routine then must be called to access an array member. We'd like to be able to put some user code into a global area so the array can be used by more than one routine easily.

See above.

Originally Posted by dcbrown

4. Cut & Paste support

In input boxes and being able to copy out the source lines from the source view window. Or an export function that exports the source lines into a straight text C file.

It turns out that you can copy out of those source file windows on the "Project" tab in EasyC. To do it you need to select the text and then right-click on the selected area. A menu with "copy" as an option pops up. You probably tried to use ctrl-C to do the copy, and that isn't yet implemented.

Originally Posted by dcbrown

5. PrintToScreen()

We're using hyperterminal so we can save our debug output to a file easier. It needs \r\n at the end of prints to get to the start of a new line. Unfortunately we can enter "Data is %d mgs\r\n" - we'd like to add the %d format character ourselves and then select the variable. Maybe a check to see if a format selection is already present and then just add the variable to the end of the line? Because we can't output multiple variables per PrintToScreen() call, we've been using the following:

PrintToScreen( "Data1, Data1, Data3\r\n");
user code[ PrintToScreen( "%d, ", data1 ); ]
user code[ PrintToScreen( "%d, ", data2 ); ]
user code[ PrintToScreen( "%d\r\n", data3);]

Maybe if there was a selection box to enable/disable adding the newline at the end. We print out the data this way so it can be pulled into an excel spreadsheet and charted easily.

I'd suggest calling the printf function from the C library. It is what print to screen does internally. You can do that in a user code block from EasyC. You should also do an include of "stdio.h" using the "File Inclusion" from the Options menu. It has the definition of printf.

Originally Posted by dcbrown

6. The ability to use the Ctrl key to add to and accumulate sets of code to
cut/delete etc. Select an line item, hold down the Ctrl key and select
another line item, etc.

EasyC lets you select contiguous sets of blocks at the same level with Shift-Select. If one of those blocks is a compound statement, like an IF statement, then all the stuff inside the IF will be selected too. After you select, right-click on the set of blocks and select "Copy". You can then paste them somewhere else in the current function or another function.

EasyC does not let you select non-contiguous blocks - for that case you need to do multiple select-copy-paste operations.

Originally Posted by dcbrown

7. A defined upgrade path from EasyC to MPLab.
As programmers become more adept and comfortable with programming. They should be able to easily grow from EasyC to MPLab and carry their work with them.
DCBrown

It turns out that the runtime system of EasyC is called WPILib and you can use it with MPLab. WPILib stand-alone has all the functions that EasyC has plue more. What this means for you is this: you can write parts of your program with EasyC and other parts with MPLab (using WPILIb) or you can write the whole program with WPILib.

Check out the WPILib forum for more information on how to get it and how to use it. There is a 57 page document that describes its use.

[dcbrown]

Originally Posted by BradAMiller

The next version of EasyC that should be available soon will let you create external functions in MPLab and add them to the linked image. There is already an option to add a header file (.h) so you might try creating those tables in MPLab, then creating a function in the same MPLab module with the "rom" storage class identifier that returns the result to the EasyC program.

I'm still having problems. I might not fully understand what you are suggesting.

I created a .h file of:

#ifndef LOOKUP_H
int mytable[4] = {1,2,3,4};
#endif
#ifdef LOOKUP_H
extern int mytable[];
#endif
#define LOOKUP_H

and did a file inclusion. The problem I've run across is that it must be compiled multiple times into the project. The project won't link, I get multiple defines at link time. If I put an error into the include file I get seven syntax errors. I don't know if that means it is compiled into 7 different modules or not. I could make the table static and that does link cleanly, but that means mytable[] is replicated multiple times in the system.

Our real lookup table could be a couple kbytes in size, having this replicated in the system a bunch of times might not be a good thing.

Looking for additional guidance.

Thanks,
DCBrown

[BradAMiller]

Originally Posted by dcbrown

Our real lookup table could be a couple kbytes in size, having this replicated in the system a bunch of times might not be a good thing.

Looking for additional guidance.

Thanks,
DCBrown

My explanation was kind of unclear. You're right, that each time the include file with the variable definition is listed, it will be included in your output file.

There is a new version of EasyC that will be availble shortly (by next week, I'd think) that will let you link your programs with an external object file. Then the idea is to create a C source file in MPLab with your table, compile it, and add that object file into the build in EasyC (next version). The table will only be allocated once, since the definition of the table only appears in that object file.

Then make your include file only contain an extern for that table and whatever types you need to make it work. That file won't generate any memory since there is only an extern declaration and not the table itself.

[dcbrown]

Thanks! The new methodology available in the next release sounds a lot cleaner as well as having a lot more applicability including creating a possible migration path between EasyC and MPLab environments for team code.

Can't wait to try out the new version!

Regards,
DCBrown

[Gdeaver]

Intellitec may may be on the way to robot programming Nirvana if the can have a full expansion path that will take care of the newbies and at the same time allow extensions that will satisfy the experienced programmer. Not there yet but, there is a path.

[dcbrown]

Is there a way in EasyC to get the rc_main_batt and rc_backup_batt? These are the field names in the rx data packet under MPLab/ifi default code. I read WPILib and EasyC help but couldn't find anything.

Regards,
DCBrown

[P1h3r1e3d13]

Originally Posted by dcbrown

1. Defines with arguments and these showing up in the user functions list.
For example:

#define SetLeftWheel( _pwm ) SetPWM(2, _pwm)

Yeah, we could code a routine called SetLeftWheel() that simply calls SetPWM(), but the call stack isn't that large and we could end up wasting a lot of its stack entries on simple redirection. The define just makes it easier for us to forget which ports/pins/interrupts go together to make up a specific feature on our robot. A feature for Pro mode only maybe?

Depending on exactly what you are trying to accomplish, you might try what I've done:
I defined global constants such as R_DRIVE_PWM and LIMIT_SW_1_INPUT as numbers (3 and 1, in this case). Then I use PWM Control and Limit Switch blocks and select the corresponding constants from the dropdown. It ends up like so:

SetPWM (R_DRIVE_PWM, speed)

and

sw1 = GetDigitalInput (LIMIT_SW_1_INPUT)

This allows me to modify almost everything I need to tweak right from the Macros and Constants dialog without having to search through all my code and change each place I set my drive speed, for example. It also makes the code easier for a non-programmer or a newcomer to understand.

[Kingofl337]

Originally Posted by dcbrown

Is there a way in EasyC to get the rc_main_batt and rc_backup_batt? These are the field names in the rx data packet under MPLab/ifi default code. I read WPILib and EasyC help but couldn't find anything.

Regards,
DCBrown

var = GetBackupBattery()
var2 = GetMainBattery()

[gabrielse]

We make new folders to save working versions of our code. However, if we try to create a folder while saving it is automatically named New Folder and can't be renamed from within EasyC. Please fix this for next year.

[Kingofl337]

Originally Posted by gabrielse

We make new folders to save working versions of our code. However, if we try to create a folder while saving it is automatically named New Folder and can't be renamed from within EasyC. Please fix this for next year.

Will do.

[P1h3r1e3d13]

More support for pointers. They can't be initialized like regular variables.
I'd like to be able to grab PWM/relay/digital output values to variables, and I assume pointers would somehow be the way do do so. Is that at all possible now?

[intelitek_Chris]

Sorry, its not possible. Pointers were intentionally not supported this year because we were trying to keep things as simple as possible for the user. The only occurrence of pointers is the in the camera capture code and was necessitated by the complexity of the camera.

But it doesn't hurt to write it on the wish list and keep your fingers crossed! Santa might be kind next year.

On the other hand, if you are looking to get your PWM, Relay, and output values into variables, that is very easy. Instead of trying to get the values out of Tank2() or OIToRelay(), use the OI Digital Input and OI Analog Input blocks from the RC group. Those get the values directly from your controls and joysticks. The only thing you can't do, is get the 'post mixed' values being sent to your drive motors from the Arcade2() and Arcade4() functions.

[Stuart]

I would love to be able to "click into" the code and manuly type in things(for quick logical oops fixing)

[P1h3r1e3d13]

1. User-friendlier printing:

I would like to be able to select from a list (perhaps with check boxes) which parts of the program to print (variables, constants, specific functions, header files, etc.) and also have options to automatically select everything, or all user functions, or all included files, or entire libraries, or all variables, or everything that's called from a certain function; you get the idea.

I'd also like the "Select and Print Flow Chart" feature to (optionally) print everything I select at a certain scale and automatically break it up into pages, instead of squeezing the whole thing onto a single page in electron-microscope-size font or me having to select individual areas and print them one at a time.

2. The options in the Window menu to view only blocks, only code, etc. should apply either to all windows or to the window I'm in when I select the option. I'm assuming it's a bug rather than a design flaw, but now it only applies to Main, at least when in a competition project.

3. I know the debugging ability of the compiler is only supposed to be rudimentary, but it seems buggy. Sometimes it lists all instances of the same error, but sometimes it only lists one. Sometimes it doesn't notice that I'm using variables and constants that I haven't defined or initialized. Once it insisted on a syntax error on line 31 of a function, no matter what was on that line. I don't know what causes the problems, but please fix them.

4. The ability to comment out a block of code, such as everything inside a While loop or an entire If/Else structure. Also, there should be an option to ignore errors in blocks that have been commented out, as they have no bearing on the compiled code.

5. The ability to select multiple, nonsequential, blocks with Ctrl and Shift. (I know someone mentioned this, but it's a big deal.)