Ecumaster 12 keypad issues

GENERAL
1

Im finding that the button colours are not configurable in my Pro software despite the fact that I am able to see and use the keypad.

I’m using an Ecumaster Pro16, ADU and keypad in my Renault Clio track car… the car already has a CAN system that I have to use that runs at 500 so the Pro, ADU and keypad are all connected to that using CAN2 set to 500.

CAN1 is connected between the Pro and the ADU with a turbosmart electronic wastegate on but nothing else.

I have used the Pro to read the keypad and then send these into CAN1 and the ADU uses the data there so there isn’t any potential conflicts with which one controls.

Have separately tried also using the ADU to change the colours but that also did not work… I’m at a loss what else to try… All keypad is an Ecumaster one so should it not all Communicate out the box or is there an additional step required?

Any guidance would be appreciated.

2

Do you have the Keypad added in the EMU Pro >> Project tree ?? That’s where you can change the colors and buttons logic.

3

Yes it’s in the Pro in the Project tree and I have all the buttons colours set but it has no effect… I see all the buttons in the Pro and can and do use them and even send these into CAN1 for me to use in the ADU.

IMG_1527
IMG_15271920×1440 765 KB

4

Are you sure you selected the correct keypad?

Can you post the keypad’s serial number?

5

I believe I selected the correct one, 2x6 multi colour?

IMG_1530
IMG_15301920×1440 409 KB

IMG_1528
IMG_15281920×2560 911 KB

6

I looked at this again and I think it is an issue with the ECUMASTER Keypad itself as I have seen that the button I have assigned to traction control button goes red when the ecu turns the coolant fan on and I have that button as white going orange in the Pro software with no other external actions.

I guess it’s possible mine has been sent without the Ecumaster CAN loaded? Is this something I can load?

7

Please connect the USBtoCAN to CAN 2, where the keypad is connected.

Download and install the Light Client application from our website.

Open the Light Client and check if you can see the keypad in the device list.

8

I am able to see it in ecumaster light client on CAN2, screen shots below

att.qBHBCcagL9TnmGvHGb_6fTnILW7Gb-waM3iQMSN1Z6U
att.qBHBCcagL9TnmGvHGb_6fTnILW7Gb-waM3iQMSN1Z6U2048×1536 291 KB

IMG_1532
IMG_15321920×2560 991 KB

att.fna-17CocclImPiAJdzyPDCxBtM3NcdBCxg-zt5kZv8
att.fna-17CocclImPiAJdzyPDCxBtM3NcdBCxg-zt5kZv82048×1536 347 KB

ID is 195H

I am not sure why it’s not showing the Pro and ADU as these are also on CAN2 and these screen shots were while I had car running a few minutes ago and I was using the keypad to start the car via the Pro and showing the button presses on the ADU (I have temporarily configured the ADU to show me the button status).

9

I believe I have found the issue… The ‘Renault Clio 3’ protocol is conflicting with the keypad, i noticed colours changing for things on the car not in the Pro or ADU (reverse light for example).

I worked out how to change the speed of the keypad to 1000bmps and have tried it on CAN1 and i am now able to control the colours.

10

There is no Ecumaster communication protocol on CAN 2.
That’s why they are not showing up.
You would see them on CAN 1.

That makes sense.
The Clio stream is sending frame 0x511, which is conflicting with keypad communication.

That’s why we often recommend having all the Ecumaster devices on CAN 1 and OEM stuff on CAN 2.