We started using IMEs recently and we’ve been having a host of strange seemingly meaningless issues (we’re using PROS).
I think it’s best to describe what happened in time order:
We initialized the encoders and everything seemed to be working fine (we were getting the correct values just as we expected based on wheel turns in the LCD display). However, we have a method to record autonomous and programming skills routines (for which we want to use the encoder), and simply adding the single line “imeInitializeAll()” caused this routine to move random motors on our robot. This is very odd, since for debugging purposes, we had this routine NOT use any encoder values, which means that the act of initializing the encoders itself caused the strange motion (and not the fact that encoder values were not zero). Curiously, driver control worked normally, which led us to think that perhaps memory overflow or some sort of memory corruption was occurring (screwing up our autonomous recorder, which uses around 6 kb of memory). Later, the cortex randomly started to crash just after we finished saving a file (this was working perfectly before the IMEs were added) and gave a blank error code over serial. This consistently occurred every time we tried to save an autonomous file. About an hour later, we tried testing once more, except this time, “imeInitializeAll” returned 0 every time and the lights on the encoders remained yellow, even though we changed nothing about the connections. Based on previous posts, we considered the possibility that built up static charge could have affected our IME performance, but we can’t seem to understand how that would cause all these symptoms. Any help is welcome