EvoScan bug reading MUT 07
#1
EvoScan bug reading MUT 07
Just thought that I'd let everyone know that based on some logging I did today, it appears that EvoScan v2.9.0100 does not properly read MUT07 when making a 1-byte data request. EvoScan gives some garbage value. However, if MUT07 is used in a 2-byte data request, i.e., RAM high byte is written to MUT06 and RAM low byte is written to MUT07, then interestingly, MUT07 works.
Thread
Thread Starter
Forum
Replies
Last Post