[krystian.]

What can I say?

It works 100% ok!

[dommeij]

Doesn't work 100%... i've got an 300km/h speedometer an when I try to change it to max 260km/h (just for a test, with the numbers of your screenshot) it says coding ok. But my needle is moving like in a 300km/h speedometer... Could you help me?

[inotherwords]

Doesn't work 100%... i've got an 300km/h speedometer an when I try to change it to max 260km/h (just for a test, with the numbers of your screenshot) it says coding ok. But my needle is moving like in a 300km/h speedometer... Could you help me?

Click on "read everything" button on the main screen and it will show you actual speedometer range. What do you mean "moving like 300"?

[dommeij]

Doesn't work 100%... i've got an 300km/h speedometer an when I try to change it to max 260km/h (just for a test, with the numbers of your screenshot) it says coding ok. But my needle is moving like in a 300km/h speedometer... Could you help me?

Click on "read everything" button on the main screen and it will show you actual speedometer range. What do you mean "moving like 300"?

After clicking on "read everything" button it says Speedometer max 310km/h. Don't really understand why it's not 300km/h.

By saying it's moving like 300 i mean:

Just imagine that the cluster is coded with max. Speed of 300km/h. When I set the "Test-drive" speed to 300km/h, the needle goes to the point x.

After coding it to max. 260km/h and setting the "Test-drive" speed to 260km/h I expect the needle stops at the same point x.

I coded my original 310km/h cluster for testing the software to a max. speed of 260km/h. I set the "Test-drive" speed to 260km/h and the needle doesn't move to the point x, i talked about but to the normal 260km/h point in a 300km/h cluster.

Hope you know what I mean....

[inotherwords]

Doesn't work 100%... i've got an 300km/h speedometer an when I try to change it to max 260km/h (just for a test, with the numbers of your screenshot) it says coding ok. But my needle is moving like in a 300km/h speedometer... Could you help me?

Click on "read everything" button on the main screen and it will show you actual speedometer range. What do you mean "moving like 300"?

After clicking on "read everything" button it says Speedometer max 310km/h. Don't really understand why it's not 300km/h.

By saying it's moving like 300 i mean:

Just imagine that the cluster is coded with max. Speed of 300km/h. When I set the "Test-drive" speed to 300km/h, the needle goes to the point x.

After coding it to max. 260km/h and setting the "Test-drive" speed to 260km/h I expect the needle stops at the same point x.

I coded my original 310km/h cluster for testing the software to a max. speed of 260km/h. I set the "Test-drive" speed to 260km/h and the needle doesn't move to the point x, i talked about but to the normal 260km/h point in a 300km/h cluster.

Hope you know what I mean....

310 km/h means that it was not coded. Show the values you have entered

[dommeij]

Doesn't work 100%... i've got an 300km/h speedometer an when I try to change it to max 260km/h (just for a test, with the numbers of your screenshot) it says coding ok. But my needle is moving like in a 300km/h speedometer... Could you help me?

Click on "read everything" button on the main screen and it will show you actual speedometer range. What do you mean "moving like 300"?

After clicking on "read everything" button it says Speedometer max 310km/h. Don't really understand why it's not 300km/h.

By saying it's moving like 300 i mean:

Just imagine that the cluster is coded with max. Speed of 300km/h. When I set the "Test-drive" speed to 300km/h, the needle goes to the point x.

After coding it to max. 260km/h and setting the "Test-drive" speed to 260km/h I expect the needle stops at the same point x.

I coded my original 310km/h cluster for testing the software to a max. speed of 260km/h. I set the "Test-drive" speed to 260km/h and the needle doesn't move to the point x, i talked about but to the normal 260km/h point in a 300km/h cluster.

Hope you know what I mean....

310 km/h means that it was not coded. Show the values you have entered

No, it shows 310km/h in the ECU Information coded on 310km/h. After coding on 260km/h it shows max 260km/h. So everything is fine there.


Here are my original values of the speedometer:

Start position offset (steps): 61
Damping factor: 6
Effective (real) speed (km/h): 0.0 / 7.5 / 46.8 / 115.6 / 295.2
Displaying speed (km/h): 0.0 / 10.0 / 50.0 / 120.0 / 310.0
Motor steps: 0 / 290 / 1450 / 3480 / 7153



These are the max. 260km/h values I entered:

Start position offset (steps): 32
Damping factor: 3
Effective (real) speed (km/h): 0.0 / 7.8 / 47.1 / 116.0 / 250.0
Displaying speed (km/h): 0.0 / 10.0 / 50.0 / 120.0 / 260.0
Motor steps: 0 / 177 / 888 / 2133 / 4622

[inotherwords]

Your speedometer arrow motor still has 7153 steps to max position (physically). Those steps points reflect how many steps the motor has to pass to get to the corresponding point. For example, when you drive at real 116 km/h (120 km/h as displaying speed), the speedometer arrow should be at point #4 and arrow's motor should pass specified number of steps at steps point #4.

So you need to calculate middle step points (between 0 and 7153) accordingly to your speed points.
For example, point #4 again:

116.0 km/h of 250 km/h (point #5) means 116/250 = 0.464. Multiply it to maximum amount of steps (7153) and you will get amount of steps to get to point #4. 3319 steps in this case.

So try to calculate points #2 and #3 by yourself using the same method. BTW be aware that it works only if your dial is marked linearly (with equal speed steps).

[acolt]

Look on my last thread, there I have posted original values for 260 km dials, simple take or compare the values

[inotherwords]

Look on my last thread, there I have posted original values for 260 km dials, simple take or compare the values

Your dials have different maximum steps. So nothing to compare.

[dommeij]

Your speedometer arrow motor still has 7153 steps to max position (physically). Those steps points reflect how many steps the motor has to pass to get to the corresponding point. For example, when you drive at real 116 km/h (120 km/h as displaying speed), the speedometer arrow should be at point #4 and arrow's motor should pass specified number of steps at steps point #4.

So you need to calculate middle step points (between 0 and 7153) accordingly to your speed points.
For example, point #4 again:

116.0 km/h of 250 km/h (point #5) means 116/250 = 0.464. Multiply it to maximum amount of steps (7153) and you will get amount of steps to get to point #4. 3319 steps in this case.

So try to calculate points #2 and #3 by yourself using the same method. BTW be aware that it works only if your dial is marked linearly (with equal speed steps).

Got it, now it works perfectly.

My only last problem is the "Test-drive"-button now. E.g. I set it up to 50km/h on a clean coded cluster (with the right calculated motor steps) the needle stops at about 40km/h. But when I drive and
speed up to 50km/h (got the digital speed in my BC) the needle is on the right position. Is there a reason why the test speed doesn't work right? Or is that my fault? It concerns only the Speedometer Needle. The other Tests work fine...