hello.

I found some funny addresses of evoscan when I was trying to log.
( My rom is 52360018. )

I think M32R's alignment rule is big-endian like mc680x0.

But, IDC, STFT, LTFT-High are defined as BYTE size and those addresses are even.

For example, according to the MUT address table, STFT located ID1:01. We can look up the addresss 808890 for STFT from MUT table in 52360018.

So, the address seems to be correct. But not on the rules of big-endian alignment.

What causes this? Something wrong or, any reasons?

Here is my def of evoscan 2.9.0005 :
---
item name____formula____________res-byte___address__alignment
IDC________[IPW]*3.90625*x/1200____1_____80873E____even
STFT________(0.1953125*x)-25_______1_____808890____even
LTFTH_______(0.1953125*x)-25_______1_____8071FE____even
---

 

IDC is a function of 1byte rpm - well it was, maybe Hamish has changed it to 2byte (juding by that 3e address is has, but it should be 2response bytes not 1)

STFT and LTFT we only care about the low byte.

LTFTH should be LTFTM + 2

thats been fixed in the most recent 2.9 build...

 

Hi,

Thanks to you tephra! I checked all the MUT ID1 again and I could correct the address of LTFT-High.

I also corrected the response byte of the IDC. But the formula I know for IDC is just "IDC=[IPW]*3.90625*x/1200". As you are saying it's the function of byte size RPM, it must be wrong but unfortunately I don't know the formula. Could you help me?


Here is my corrected def of evoscan 2.9.0005 :
---
item name____formula____________res-byte___address__alignment
STFT________(0.1953125*x)-25_______1_____808890____even
LTFTL_______(0.1953125*x)-25_______1_____804573____even
LTFTM_______(0.1953125*x)-25_______1_____804575____even
LTFTH_______(0.1953125*x)-25_______1_____804577____even
---


Still uncorrected IDC :
---
RPM(BYTE)_______31.25*x___________2_____808747____ even (MUT ID1:21)
IPW____________x/100_____________2_____80A934____even (MUT ID1:29, ID2:2A)
IDC________[IPW]*3.90625*x/1200____2_____80873E____even
---

 

MUT21 is RPM_SMALL

so you need to use 1 response bytes...

 

oh, I'm sorry, I took a careless miss. fixed.
>RPM(BYTE)_______31.25*x_________1_____808747____odd (MUT ID1:21)

Still I don't know the correct formula for IDC. What is the correct expression?
>IDC_____[IPW]*3.90625*x/1200____2_____80873E____even

 

that should work ok..

 

well...sorry, I'm a little confused.

I'm sorry for repeat the question, but if the formula ( IDC = [IPW]*3.90625*x/1200 ) is correct, then what do you mean by your mention below? Where is the 1 byte rpm used?

>IDC is a function of 1byte rpm - well it was, maybe Hamish has changed it to 2byte (juding by that 3e address is has, but it should be 2response bytes not 1)

 

This may clear up your confusion...

You can't actually log IDC directly, as it's just a calculation.

IDC = IPW * RPM / 1200

The Address in your above IDC line is for RPM. The formula is just a combination for RPM and IDC. I never, ever, log IDC. I simply calculate it after the fact.

 

Thank you for the formula, Golden. It does helps the problem to be clear.
Currently my evoscan shows the address of RPM(BYTE) as 23808747, and IDC as 2380873E(2byte RPM). It means in my setting, the IDC uses 2byte RPM.

oh, I see. So, tephra said that it should work ok. Thanks a lot to tephra and Golden.

 

it doesn't matter which one you use (1byte or 2byte)

you just need to set the response bytes and modify the formula correctly..

I think EvoScan has a message cache, so if your logging 2byte rpm (as a standalone log item) then your best to use 2byte rpm in the IDC calculation, otherwise EvoScan needs to re-request it...

But yes - like Golden I dont bother with logging IDC, and I calculate it after the fact...

 

>But yes - like Golden I dont bother with logging IDC, and I calculate it after the fact...
clever men! Once write a filter, no need to log it.

 

pfft