G4+ thunder, 1 x 12 button keypad, 2 x Razor PDM

[TomS]

Sorry little bit of a spiel ahead, 

 

I have just updated all the wiring in a drift car, client requested 2 x Razor PDM's and 1 x 12 button keypad from you guys as part of the update, he still runs the G4+ thunder;

 

I have the majority of the simple functions working as I would have hoped on the "front" PDM but here's a list of the other issues;

 

- CAN aux to pdms? i followed through the way i was familiar with but think i may have missed a step on either the PDM side or ecu side,

i am wanting to send 

FP request, 

Engine Fan Request, 

Water pump request, 

brake light DI to rear pdm 

from memory i think that is all

 

-CAN DI to ecu from front PDM/keypad;

boost high

page up (will then go out to dash also if that's able to be done)

page down

 

- Keypad, I had the keypad working perfectly for the front and then tried to add to the rear and it would accept but the back lighting would just flicker;

is the only way to make it behave set it up identical as the front and turn the hz to off/0? 

or does it have to go from front pdm to ecu then to rear PDM? if so then more DI functions would need to be sent to ecu

 

- wiper setup? I made a GP logic set up for the wiper (only slow speed needed) but i can only get the output to put out 12v if i set it to high side, does not seem to work half bridge? unless i have made an error there to

 

sorry for the long winded yarn and my naivety, this is the first I've managed to get my hands on the razor to have a play and of course it had to be a G4+ and for a car that's meant to start drift season in a couple weeks haha

any help at all would be much appreciated, there may be more things I've forgotten, I've had enough brain scramble for the day

 

@Adamw sorry for the bombardment, i have also flick this same message to your email along with the config files from both PDMS and Ecu and i will also attached to this post, trying my best to get as much of it can operational before its due for dyno

 

i know a few of these have been answered before on the forum, but i tried a few ways i could see on here and was unsuccessful

 

Thanks Tom

1 Adam Davies 180sx 13B Razor PDM Rear.pdmc Adam Davies 180sx 13B Razor PDM Front.pdmc Adam Davies 13b 180sx Thunder g4+.pclr

[Adamw]

Sorry, I have been busy the last few days.  

I have done the basics in the attached files.  Virtual auxes should now be received by PDMs.  The rear PDM receives Keypad counts from the front PDM.  

The boost button is received into ECU as CAN DI 1.  

For the page up/down buttons, I suspect you dont need these in the ecu?  Typically we would just set up the dash to receive these directly from the PDM. 

For the half bridge I suspect it will need to be PWM.  Try giving it a fixed DC & frequency like 99%DC and 100Hz and see if that works as intended.  

Adam Davies 13b 180sx Thunder g4+ V1.0.pclr 1 Adam Davies 180sx 13B Razor PDM Rear V1.0.pdmc Adam Davies 180sx 13B Razor PDM Front V1.0.pdmc

[TomS]

Thanks for ya help @Adamw

 

Very useful info as always!! It now it makes so much more sense, all working and happy now 

[TomS]

hi again

i hope your already on holiday @Adamw and dont answer this till your back haha

but quick question haha

Are you able to provide an example of soft starting the engine fan based on time, eg soft start it from say 50% to 100% over 2 seconds as the fans hungry and really notice it kick in, just can't quite get my head around the what does what with the terminology and how to intertwine the parameters to make it ramp over time?

 

Thanks so much once again for all your help and hope you get a well deserved break over Christmas 

[Adamw]

A few ways you can do a soft start - all more complicated than they should be, but here is how I would do it...

The engine fan output set up and the Fan Req CAN function are unchanged from your above configs.

On GP Logic 6 which used to turn on the fan output directly, I have now changed its output pin to "none".  

I have added a math block labelled "Fan Softstart", this generates a ramping duty cycle whenever GP Logic 6 becomes active.  To explain the important bits of the math expression "min((cnt(a)*0.5),100)", the "0.5" is how much the DC increases per 10mS, so 0.5 means you would get to 100% in 2seconds.  Use a smaller value to ramp up speed slower.  The "100" is the maximum DC we want to use.  

I have then added GP Function 7, labelled "Fan Control".  This has the engine fan pin assigned as the output.  For the condition I have set "Fan Softstart >10", this means it will turn on the fan output whenever the mathblock is commanding more than 10%DC.  Effectively this is the minimum DC you want your Fan to start ramping from.  You need to also set a suitable frequency in this GP function, I have set it to 200Hz in this example which will work for most fans.  Then assign the "Fan Softstart>Status" as the Duty parameter in this GP Function.  

[TomS]

4 hours ago, Adamw said:

A few ways you can do a soft start - all more complicated than they should be, but here is how I would do it...

The engine fan output set up and the Fan Req CAN function are unchanged from your above configs.

On GP Logic 6 which used to turn on the fan output directly, I have now changed its output pin to "none".  

I have added a math block labelled "Fan Softstart", this generates a ramping duty cycle whenever GP Logic 6 becomes active.  To explain the important bits of the math expression "min((cnt(a)*0.5),100)", the "0.5" is how much the DC increases per 10mS, so 0.5 means you would get to 100% in 2seconds.  Use a smaller value to ramp up speed slower.  The "100" is the maximum DC we want to use.  

I have then added GP Function 7, labelled "Fan Control".  This has the engine fan pin assigned as the output.  For the condition I have set "Fan Softstart >10", this means it will turn on the fan output whenever the mathblock is commanding more than 10%DC.  Effectively this is the minimum DC you want your Fan to start ramping from.  You need to also set a suitable frequency in this GP function, I have set it to 200Hz in this example which will work for most fans.  Then assign the "Fan Softstart>Status" as the Duty parameter in this GP Function.  

Wow! Yes definitely more co plicated than it needs to be, thank you so much for you help, ill have a play with it and see how we go

 

Thanks Adam

Enjoy the holidays 

[TomS]

Hi guys, 

 

Have another question about above set up, has been working fine for a day on the dyno and a track day or so, then all of a sudden the keypad wouldn't power up, I know the output is okay because it shares it with the dash and it works perfect, only way to make it power up again was to unplug and replug the 4 pin DTM on the rear of the keypad?? Any ideas, I changed the CAN ID from 405 to 400 and stored, then changed back to 405 and stored again, and also added a power on delay of  0.2 seconds and now seems to be fine again at the moment, but trying to prevent it happening again 

 

Thanks in advance 

[Adamw]

I believe this is a Blink firmware issue.  Somewhere along the line recently they updated the processor in some of the keypads and this introduced this random shutoff issue.  I cant remember all details - if there is a known trigger etc.  They have recently given us fixed firmware but it needs a PCAN tool to do the update so will likely have to be returned to Link for the update.  If you have a PCAN tool I can possibly give you the update software but I would need to check in with others if we are allowed to.