@zarpspeed I'm here too (with a different name ;-) )
What do you want to read back on the FT600?There is no possibility to configure the Fueltech ECUs 😏 So it needs a "hack".For example I have a Blink 12 button CAN keypad. My PDM15 sends a message to emulate a Fueltech 4 button Switch panel. So I can use 4 buttons in the FT500 ECU and 8 buttons are used via PDM.
I have done a little bit reverse engineering for the O2slim. I try to find out how the Gearcontroller messages are created. But it isn't ready until now.
you can lookup a post from Noah Perkins in Fueltech USA tech on Facebook. Sven Small has some details on the comments. Here are some of the details
Svem SmallI have created a little "datasheet".My research was done on a 8 button panel. The panel works without any ECU. But I have tested with a Fueltech FT500 ECU too.The bus works on 1Mbit.The panels have fixed CAN IDs. Fueltech describes how the CAN ID is build, ProductId: 0x0244 + Unique-Id. The Unique-Id decides the "button count"0x12200320 - old style 8 button panel0x12208320 - 4 button panel mini0x12210320 - 5 button panel mini0x12218320 - 8 button panel miniThe Panel keeps the state of colors and dimming if it gets no more information.The ECU will response every time if it get a message from the panel immediately, independent if it has a configuration of it. So if we want to overwrite the information, the PDM should detect the messages from the ECU and send their own in short time after the message from the ECU.The CAN message is build:byte 0: first button row control (button 1-4)- bit 0-3: dimming - bit 4-6: (unused) - bit 7 state (on or off)byte 1: second button row control (button 1-4)- bit 0-3: dimming - bit 4-6: (unused) - bit 7 state (on or off)byte 2: first button row state- bit 0: button 1 pressed- bit 1: button 2 pressed- bit 2: button 3 pressed- bit 3: butten 4 pressed- bit 4-7 unusedbyte 2: second button row state- bit 0: button 5 pressed- bit 1: button 6 pressed- bit 2: button 7 pressed- bit 3: butten 8 pressed- bit 4-7 unusedbyte 3-7 are filled but unsed -> DLC 8The ECU responce on this CAN messages every time and sends information to set colors and dimming information. Independent if configurated or not.
https://drive.google.com/drive/u/0/folders/1s7ABRJ6dtp7GD-plYOAk-O7xeM9UUsTvhere is the variables that will be pulled in from Fueltech. You can download the software and take a look. If you want to send anything back to Fueltech it will need to be configured in the CAN Output portion. you will need to look at the Fueltech documentationyou can also wire some outputs to Hardwire inputs to trigger things
@zarpspeed I'm here too (with a different name ;-) )
What do you want to read back on the FT600? There is no possibility to configure the Fueltech ECUs 😏 So it needs a "hack". For example I have a Blink 12 button CAN keypad. My PDM15 sends a message to emulate a Fueltech 4 button Switch panel. So I can use 4 buttons in the FT500 ECU and 8 buttons are used via PDM.
I have done a little bit reverse engineering for the O2slim. I try to find out how the Gearcontroller messages are created. But it isn't ready until now.
https://files.fueltech.net/manuals/Protocol_FTCAN20_Public_R020.pdf
this may also be helpful
you can lookup a post from Noah Perkins in Fueltech USA tech on Facebook. Sven Small has some details on the comments. Here are some of the details
Svem SmallI have created a little "datasheet". My research was done on a 8 button panel. The panel works without any ECU. But I have tested with a Fueltech FT500 ECU too. The bus works on 1Mbit. The panels have fixed CAN IDs. Fueltech describes how the CAN ID is build, ProductId: 0x0244 + Unique-Id. The Unique-Id decides the "button count" 0x12200320 - old style 8 button panel 0x12208320 - 4 button panel mini 0x12210320 - 5 button panel mini 0x12218320 - 8 button panel mini The Panel keeps the state of colors and dimming if it gets no more information. The ECU will response every time if it get a message from the panel immediately, independent if it has a configuration of it. So if we want to overwrite the information, the PDM should detect the messages from the ECU and send their own in short time after the message from the ECU. The CAN message is build: byte 0: first button row control (button 1-4) - bit 0-3: dimming - bit 4-6: (unused) - bit 7 state (on or off) byte 1: second button row control (button 1-4) - bit 0-3: dimming - bit 4-6: (unused) - bit 7 state (on or off) byte 2: first button row state - bit 0: button 1 pressed - bit 1: button 2 pressed - bit 2: button 3 pressed - bit 3: butten 4 pressed - bit 4-7 unused byte 2: second button row state - bit 0: button 5 pressed - bit 1: button 6 pressed - bit 2: button 7 pressed - bit 3: butten 8 pressed - bit 4-7 unused byte 3-7 are filled but unsed -> DLC 8 The ECU responce on this CAN messages every time and sends information to set colors and dimming information. Independent if configurated or not.
https://scontent.fewr1-6.fna.fbcdn.net/v/t39.30808-6/s261x260/260536766_4505342866252364_3762959851062082146_n.jpg?_nc_cat=101&_nc_rgb565=1&ccb=1-5&_nc_sid=dbeb18&_nc_ohc=t36nrcxgzVgAX9RtWT_&_nc_ht=scontent.fewr1-6.fna&oh=00_AT_FZv1GuxPJNNSR4CG31hGH_XJBy_1YV2C65KIKeQTPBQ&oe=61D1777E
https://drive.google.com/drive/u/0/folders/1s7ABRJ6dtp7GD-plYOAk-O7xeM9UUsTv here is the variables that will be pulled in from Fueltech. You can download the software and take a look. If you want to send anything back to Fueltech it will need to be configured in the CAN Output portion. you will need to look at the Fueltech documentation you can also wire some outputs to Hardwire inputs to trigger things