MembersPage/PhatBob/ConfigProblem (2005-11-09 23:26:29)

I am looking at a Webshop customer's v3.2 board. He was reporting problems that Jorgen guessed was a config issue.

I made a config (how? in text?) which cured his issues, and downloaded it to his 3.2 Then as a test I uploaded the config (how?), remade it and downloaded it again - the problems he reported came back.

Uploading the config again and comparing them showed the following problem: the variables are offsetted

this sounds like a PC side error

intended config.txtoutput of mcd
als_ignretard=FFals_ignretard=FF
als_rich=FFals_rich=FF
misc1out_minrpm=FFals_rev_limit=FF
misc1out_maxrpm=FFmisc1out_minrpm=FF
misc1out_mintps=FFmisc1out_maxrpm=FF
misc1out_maxtps=FFmisc1out_mintps=FF
misc1out_minmap=FFmisc1out_maxtps=FF
misc1out_maxmap=FFmisc1out_minmap=FF
misc1out_channel=FFmisc1out_maxmap=FF
misc2out_minrpm=FFmisc1out_channel=FF
misc2out_maxrpm=FFmisc2out_minrpm=FF
misc2out_mintps=FFmisc2out_maxrpm=FF
misc2out_maxtps=FFmisc2out_mintps=FF
misc2out_minmap=FFmisc2out_maxtps=FF
misc2out_maxmap=FFmisc2out_minmap=FF
misc2out_channel=FFmisc2out_maxmap=FF
act_wot_rpm=FFmisc2out_channel=FF
act_wot_channel=FFact_wot_rpm=FF
act_rpm_rpm=FFact_wot_channel=FF
act_rpm_channel=FFact_rpm_rpm=FF
egt1_cal=49act_rpm_channel=FF
egt1_offs=00egt1_cal=49
boost_conf=00egt1_offs=00
boost_targetoffs=00boost_conf=00
boost_minpressure=FFboost_targetoffs=00
boost_pid_kp=20boost_minpressure=FF
boost_pid_ki=80boost_pid_kp=20
boost_pid_kd=01bip_b
boost_pid_ilimit=FF_yw00roFkfF=r
boost_channel=FF 
water_pump_temp=00 
hybrid_rpm_a=00 
hybrid_rpm_m=00 
water_pump_hyst=00 
water_pump_channel=FF 

And the config:\nÿ2ÿ

And the mtt file\n

Mantt
g00c04
g01cA0
g02c64
g03c14
g04c03
g05c00
g06cA0
g07c0A
g08c00
g09c14
g0Ac28
g0Bc3C
g0Cc50
g0Dc64
g0Ec78
g0Fc8C
g10cAA
g11cC8
g12cAA
g13cAA
g14cAA
g15c96
g16c96
g17c82
g18c78
g19c6E
g1Ac69
g1Bc64
g1CcFF
g1Dc30
g1Ec03
g1Fc01
g20c1A
g21c4D
g22c7D
g23c80
g24c04
g25cFF
g26cFF
g27cFF
g28cFF
g29c07
g2AcD0
g2Bc00
g2Cc05
g2Dc14
g2Ec28
g2Fc4D
g30c03
g31c05
g32c07
g33c0F
g34c05
g35c03
g36c96
g37c02
g38c64
g39c1A
g3AcFF
g3BcFF
g3Cc43
g3Dc62
g3Ec51
g3Fc50
g40c02
g41cA3
g42c80
g43c64
g44c0C
g45cF9
g46c38
g47c55
g48c09
g49cFF
g4AcD8
g4Bc18
g4CcBF
g4Dc0F
g4EcBF
g4FcC7
g50c64
g51c64
g52c99
g53c73
g54c0A
g55c30
g56c04
g57c0B
g58c05
g59c19
g5Ac41
g5Bc19
g5CcB8
g5Dc0A
g5Ec03
g5Fc01
g60c02
g61cBE
g62cBE
g63cC8
g64cC8
g65cC8
g66cC3
g67cC3
g68cBE
g69cBE
g6AcBE
g6BcFF
g6Cc00
g6Dc00
g6Ec00
g6Fc00
g70c00
g71c26
g72c05
g73c94
g74cFF
g75c37
g76c05
g77cFF
g78c3C
g79c0D
g7Ac05
g7Bc96
g7Cc00
g7Dc03
g7Ec19
g7FcFF
g80cFA
g81cFF
g82cE4
g83cA0
g84c60
g85c06
g86cBA
g87c50
g88c96
g89c8D
g8Ac64
g8BcAE
g8Cc46
g8Dc10
g8Ec1A
g8Fc80
g90c40
g91c2E
g92c08
g93c84
g94c80
g95c00
g96cFF
g97c29
g98cFF
g99cFF
g9Ac29
g9BcFF
g9CcFF
g9DcFF
g9EcFF
g9FcFF
gA0c00
gA1cFF
gA2cFF
gA3cFF
gA4cFF
gA5cFF
gA6cFF
gA7cFF
gA8cFF
gA9cFF
gAAcFF
gABcFF
gACcFF
gADcFF
gAEcFF
gAFc00
gB0cFF
gB1c11
gB2cFF
gB3cFF
gB4cFF
gB5cFF
gB6cFF
gB7c00
gB8c01
gB9c02
gBAc3A
gBBc03
gBCc14
gBDc50
gBEc06
gBFc12
gC0cFF
gC1cFF
gC2cFF
gC3c84
gC4c27
gC5c8A
gC6c50
gC7c70
gC8c02
gC9c08
gCAc0F
gCBc57
gCCcFF
gCDcFF
gCEcFF
gCFcFF
gD0cFF
gD1cFF
gD2cFF
gD3cFF
gD4cFF
gD5cFF
gD6cFF
gD7cFF
gD8cFF
gD9cFF
gDAcFF
gDBcFF
gDCcFF
gDDcFF
gDEcFF
gDFcFF
gE0cFF
gE1cFF
gE2cFF
gE3cFF
gE4cFF
gE5cFF
gE6c49
gE7c00
gE8c00
gE9c00
gEAcFF
gEBc20
gECc80
gEDc01
gEEcFF
gEFcFF
gF0c00
gF1c00
gF2c00
gF3c00
gF4cFF
gF5cFF
gF6cFF
gF7cFF
gF8cFF
gF9cFF
gFAcFF
gFBcFF
gFCcFF
gFDcFF
mcs
bye

That seems clearly bad.\n

gD2cFF
gD3cFF
gD4cFF
<code>
What is gD3cFF doing there ?
Should be

<code>
gD2cFF
gD4cFF

since in varstr.h in any recent firmware 
char _varname_str_d2[] PROGMEM = "als_rich";
char _varname_str_d3[] PROGMEM = "als_rev_limit";
char _varname_str_d4[] PROGMEM = "misc1out_minrpm";

So D3 position is als_rev_limit which is not specified in the config. So again, check that global.h matches firmware.

But it does not worth to investigate if firmware version is not provided.