MSgpio.com read only forums (Jan.15,2018)

is pin 17 on a different ground plane in the board?

ashford,

No. With the low current signal wires having their own ground pin, the path to the only ground plane in the PCB for the signals is separate from the noisy power grounds, making the signals as 'clean' as possible. The intent of the recommended wiring is that users should separate the high current grounds (for driving solenoids, etc.) from the very low current signal grounds as much as possible. The reason is that the high current grounds will introduce a voltage offset in the path from the device to the PCB's ground plane. If the ground pins/wires were combined with the signal pins/wires, even for short distances (even just through through the Ampseal connector), this could play havoc with signal, especially when using PWM, or when using low voltage signals (like EGT thermocouples). Note that the VSS ground is then separated from the other signals to try to reduce the amount of high frequency noise it might introduce in things like temperature signals.

The PC PWM flickering could also be caused by the controller thinking it is on neutral or other gears (due to the voltage setting issue), as there is a specific limit for neutral that isn't affected by load.

Lance.

pin 18 has only the mlps and pressure transducer on it so that should be ok then? im just used to the ms with the 10 or so ground plane pins i generally use 3 for signal grounds. 1 for crank only 1 for temps an 1 for o2.

as for the pwm flickering on 4116 the only time pwm is at 100(0 actual) is when the engine is not running i have gear P&N set for 40 if that help with digging for problems in the code.

pin 18 has only the mlps and pressure transducer on it so that should be ok then?

ashford,

Yes, as long as these are low current devices, they will be fine.

If the engine isn't running, the PWM is set to 0 (indicated as 100) to reduce the current draw. The pressure can't be controlled if the engine isn't turning the pump, after all! I will have a look and see if I have messed up the calculations though. I have likely missed something in setting up the code, and the settings for P/N and 'engine off' are conflicting.

Lance.

all above mentioned observations were with the engine running, sorry i did not specify. these problems were not present with 4104

ashford,

I will post some code you can try, it makes sure that the neutral setting is only used above 300 rpm:
However, if you could post your MSQ and a datalog the illustrates the problem (using 4.116 or this code), that would be helpful.

Lance.

ill give it a shot after work

ashford,

I have cleaned up the PC PWM logic (w.r.t. neutral and/or engine stopped), so this version might be better than what I posted above:
Lance.

here are the logs from 4116a and msq

for the time being i will run 4104(excuse my dislexia 1404) manually shifting it appears to work, i need to put a load on my engine to seat the rings and rought tune itas the motor is new. ill test the new code probably wendsday or thursday.

also i noticed that the 2 point line pressure always reports 0 but adc works

I will have a look. Lance.

ashford,

The datalog indicates that the controller is not finding a gear that matches the voltages specified in the INI. (This is indicated by the -99 manual gear value.) This also causes the PWM% to vary between the table value and 100%. Did you measure and adjust the manual shift lever voltage values for the new code?

Lance.