EasyC currently "fixes" motor timeouts by setting the no timeout bit on all motor controllers. This is terrible, and not just because the NXT might brick or something: users are likely to forget to set motor power to 0 at the end, so motors will continue running even after the program is terminated. This will potentially cause severe physical damage.
EasyC currently "fixes" motor timeouts by setting the no timeout bit on all motor controllers. This is terrible, and not just because the NXT might brick or something: users are likely to forget to set motor power to 0 at the end, so motors will continue running even after the program is terminated. This will potentially cause severe physical damage.