Quote:
Originally Posted by MPaulHolmes
T
TR=364 CR=364 CF=329 PW=511 HS=0361 RT=0491 FB=00 BA=340 AH=xxx.x
TR=364 CR=364 CF=012 PW=512 HS=0362 RT=0491 FB=00 BA=000 AH=xxx.x
TR=364 CR=365 CF=024 PW=512 HS=0362 RT=0491 FB=00 BA=000 AH=xxx.x
Here's the relevant data. BA is battery amps. CF is current feedback. PW is pulse width (the duty).
The default max motor amps at the moment is set to 100amp (PER IGBT). The scale on the data above for Current Feedback is 0-511 (to make it compatible with RTD Explorer). 512 means 100amp (PER IGBT). So, it says BA (battery amps) got up to 364, which is 364/512*100 = 71amp (per igbt). So the battery amps got up to 213 real life amps. I need to update this to real life amps, like on the AC controller.
|
I know this will mess up the code a bit ... but a suggestion ...
If you leave rtd-period as the command for logging and leave the output this way (compatible version) then it will still be compatible with RTD Explorer (which I should test since I have a new version that works with Windows 7/8/8.1/10)
And if the new scaling method is used and tied to data-stream-period then the code-base can be brought inline with the AC controller.
Do I need to change a setting to allow a higher DC current? I'm *STILL* trying to test out your hardware over-current on the AC controller! I hope to finish up the testing this weekend so I can get my garage back, and then get the DC controller installed in my Mazda.