Hi KeesSmit,

Thanks for the followup.

Hopefully the next version will come soon­.

Of all the things...

I never thought I would see that again :

**Severe*:Out of static memory for variable allocation.

I'm sure I don't even use 20k of space for my variables... With the EV3, can I know what is the maximum static memory we can use?

Thanks,

Frederic

Hi all,

I'm new user of EV3. I used to program with RobotC 2.x on my NXT bricks.
After following tutorial, it's quite easy to use but some bugs are still there (I know, it's only a beta version but it's useful to say to fix them for the official version).
First of all, I can't use RCX touch sensor. It works with NXT Touch sensor but not for RCX one. It worked with NXT and RobotC 2.x
Then PlaySound and PlayTone functions don't work. It's clearly not the most important
Another thing more important for me about variables windows : I can't see any local variables, even in the good window (nothing appears), and it's impossible to modify values of global variables. When I try it, the brick is locked, I must remove battery, and restart RobotC.
Last thing is about "short" variables

gives
Behaviour is OK is int is used intead of short.

For now, everything else is working well

I am using RObotC 4.10 F/W 10.10 on a VM WinXP running on Ubuntu.

Hello,

I haven't tried downloading to my nxt, but when I compile my programme, any errors that I have previously had occur in the programme!
E.g. I do the code:

And I get the errors:

**Error**:Undefined procedure 'motr'.
*Warning*:Invalid '=' operation for types 'void' and 'char'

Nothing wrong about that. If I fix the code to:

I get the same errors! Also, if I create a completely new programme (even if I've restarted my computer or RobotC), when I compile it, I get the errors that I got from the "motr(motorB) = 0;" mistake, even though it was in a different programme!

I am using a Windows 7 Home Prem Edition, RobotC 4.09 Beta 1 set to NXT.

PACTeam,

It should be motor[] with square brackets, it's a variable, not a function.

= Xander

I don't think the memory heap has been changed significantly for the EV3, compared to the NXT. It's probably something that will be addressed at some point, though, but may require a fair bit of work on the internal VM side of things.

= Xander

I am “playing” with the code od RobotC 4.10 for EV3 and found that there is a problem (is it?) with the interpretation of the variable with wait1Msec(). When inserting the direct value e.g. wait1Msec(70); It works fine but when the variable e.g. ‘watime’ is inserted then the read time is extended for x times of the value - almost infinity.

Here is the example:





Any logical explanation please?

Xander,

Sorry if this is offensive, but that was an example. ANY error I make, even if I fix it, turns up in the 'error list', not just that one!

PACTeam,

Please give me an example of a complete program that you are having issues with. not just a single statement.

= Xander

Hey bety,

I've had the same problem here with #define and even "const int". Value works, but compiler directive doesn't.

-JD

I have downloaded the new 4.1, and I am excited to try it out on the EV3! I noticed as I was playing around with it that it says Natural Language is not currently supported. Anybody have a guess on when/if this will be added?

I know it's being tested in teachers classes, so maybe for the next release

= Xander

Thanks!

Looking forward to the update - any estimates as to when it is likely to be released

RSN™ (Real Soon Now)!

In all seriousness, I believe that a production release is due in about 2 weeks or so. I'll ask about a beta release in the mean time.

= Xander