Answered: Test Program Code Error

VEX V5 Technical Support OFFICIAL Tech Support
1

I tried to run the Test Code, but its got issues with consistency. Almost 80 percent of the times I ran the code it ended up showing the line “IFI> Master Code Version 8” with a little jerk motion of a single or more motors when every time the line comes up.

Please Help.:frowning:

Test Code Error.jpg
Test Code Error.jpg489×990 71 KB

2

Is this with or without VEXnet?

3

Running it without Vex Net and now the problem seems to be getting out of hand. I can’t get past Testing Motor 1 and it is getting executed again and again that way. :frowning:

Please Help, as this is not letting me run any other programs either.

4

I bought the Protobot Kit with no VEXnet upgrade.

I am using Easy C V2.9.3.0 with Master Code V8d

I tried updating it to Easy C V2.9.3.3 with Master Code V10

Yet, I am still getting the same error.

"Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

IFI>Master Code Version: 10

"
"
"
"
"

with every “IFI>Master Code Version: 10” statement comes a little jerky motion of all the motors connected.

Please Help, need to showcase this in my Final Year Project next month.:frowning:

5

**Just to clarify things - you state that you are receiving the error "FI>Master Code Version: 10 ", yet your screen shot shows version 8. Which one is it?

Have you treid replacing both the master code and default firmware?**

6

The Master Processor keeps resetting the Vex Controller…
A Low Battery, or Bad Code in the User Processor will cause this behavior. If you reload the Vex Default Code, does the problem go away??

Can you post you Source Code?? If you post the EasyC Project, include both Files…

7

Sorry, if I went Hyper on the postings. As I didn’t find the solution to it anywhere on the forum.:frowning:

Anyway, The problem has been solved,:rolleyes: and the source for it was that I was using almost depleted batteries in the receiver which lead to it.

Thanks for the help, Sean Daugherty and MarkO. :smiley:

8

Thanks a lot, MarkO.

The problem was not related to a specific program and occurred while executing all the programs.

The problem was indeed with Low Battery and has been solved after replacing them with new ones.

Thanks a lot again.:smiley:

9