File Error

[apratt2003]

Greetings everyone,

My kids keep getting a file error on the brick when they add one more color sensor wait block to the end of their program. They can add other actions fine without error. File size is only 37K with all other programs deleted on the brick.

Any ideas?

Andy Pratt
Team #55
Middletown, RI

[ISHW]

I fear your team ran into a bug that other teams apparently also encounter.
http://forums.usfirst.org/showthread.php?t=18316

I would try first to isolate the problem. Maybe do the following:

• Create a small program consisting of one move block (unlimited) and add the suspicious wait-for-color-sensor. See if it works without file error.
• Replace the wait-for-color-sensor in the original program with the same (working) block you created in the small program (copy / paste). Do you get a file error now?

You write your kids can add other actions to the program. Instead of wait-for-color try a wait-for-light or a wait-for-touch for testing purposes. Do you get the file error?

I fear if you are not able to isolate the problem, then a more complex bug is the culprit. My team ran into a similar problem when trying to create a menu program that links all tournament programs together. We were not able to solve the problem, but maybe your experience provides a further hint where to search.

[apratt2003]

we took the risk and updated firmware from 1.28 to 1.31. No change in file error status.

changed wait block from color sensor to time, works fine.

the team uses this same wait block many times earlier in the program and works fine. we even ctrl-drag copy a good block with no success.

it almost seems to be a file size problem, but there is more than double the amount of free storage.

to be continued...

[Dean Hystad]

Originally Posted by apratt2003

we took the risk and updated firmware from 1.28 to 1.31. No change in file error status.

changed wait block from color sensor to time, works fine.

the team uses this same wait block many times earlier in the program and works fine. we even ctrl-drag copy a good block with no success.

it almost seems to be a file size problem, but there is more than double the amount of free storage.

to be continued...

I don't think this is a file size problem. You said you can replace this block with a timed wait and the program works. If anything replacing the color sensor wait with a timed wait made the program bigger. In NXT you pay a big memory penalty the first time you use a block and a small penalty every time after.

I would look at the "last block in the program" being a problem and "uses the same wait block many times earlier in the program" being fine. What happens if you add some blocks after the color sensor wait?

[apratt2003]

Tested problem on 3 bricks. Same results.

Added 12-15 move blocks to end of program, with out color sensor wait block. no problems.

can have multiple color sensor wait blocks in a "new" program. no problems.

ctrl-drag copy existing "working" color sensor wait block. "File Error" on brick. (see attched picture)

i am stumped

[Dean Hystad]

Originally Posted by apratt2003

Tested problem on 3 bricks. Same results.

Added 12-15 move blocks to end of program, with out color sensor wait block. no problems.

can have multiple color sensor wait blocks in a "new" program. no problems.

ctrl-drag copy existing "working" color sensor wait block. "File Error" on brick. (see attched picture)

i am stumped

Does "Multiple color sensor blocks in a new program" equate to the same number of color sensor wait blocks in the program that is having problems?

[timdavid]

Originally Posted by apratt2003

Tested problem on 3 bricks. Same results.

Added 12-15 move blocks to end of program, with out color sensor wait block. no problems.

can have multiple color sensor wait blocks in a "new" program. no problems.

ctrl-drag copy existing "working" color sensor wait block. "File Error" on brick. (see attched picture)

i am stumped

What version of the PC/Mac NXT Mindstorms NXT-G software are you using?
Commercial versus Educational?
2.0 or 2.1?
PC versus Mac?
What operating system on the PC / Mac?

Can you create a pack and go file with the problem program and make it available for people to grab (via Dropbox or some other site) and try in another environment?

I'd be happy to try it on my local machines to see if I can recreate the error. I promise not to steal any of your code for tournament use...

[apratt2003]

Originally Posted by Dean Hystad

Does "Multiple color sensor blocks in a new program" equate to the same number of color sensor wait blocks in the program that is having problems?

yes. i started with the same sequence:

move 75% unlimited
wait for white
move 75% unlimited
wait for black
move 75% unlimited
wait for white
move 75% unlimited
wait for blue
move 75% unlimited
wait for white
move 75% unlimited
wait for black
move 75% unlimited
wait for white

worked fine.

[apratt2003]

Originally Posted by timdavid

What version of the PC/Mac NXT Mindstorms NXT-G software are you using?
Commercial versus Educational?
2.0 or 2.1?
PC versus Mac?
What operating system on the PC / Mac?

Can you create a pack and go file with the problem program and make it available for people to grab (via Dropbox or some other site) and try in another environment?

I'd be happy to try it on my local machines to see if I can recreate the error. I promise not to steal any of your code for tournament use...

PC version 2.0 commercial with windows vista. I never tried a pack and go file nor used dropbox, but i will give it a try.

[timdavid]

Originally Posted by apratt2003

PC version 2.0 commercial with windows vista. I never tried a pack and go file nor used dropbox, but i will give it a try.

If you haven't used dropbox, you can just create a zip file containing the pack and go file (.rbtx extension I think), and post a reply to this thread.
I'm not usually a fan of posting source on the forum, but you can delete the post after any volunteers have grabbed it to test.

The pack and go tool just creates a single file containing all the used MyBlocks for a program. Very convenient when trying to share programs between computers.