[Ovmsdev] i-Miev/C-Zero/iOn
Thomas Bergo
thomas.bergo at gmail.com
Tue Sep 24 04:07:26 HKT 2013
Matt:
I can send you the hex file i'm running in my OVMS module, so you can try
if that woking in your module?
Regards, Thomas
2013/9/23 Thomas Bergo <thomas.bergo at gmail.com>
> I did a rebuild from clean to ensure that i running the exact same code.
> My OVMS module is booting as expected, and only the green led is blinking
> OK (one blink]
>
> Which version of the OVMS FW are you running? I have only tested with the
> 2.5.2 FW.
> Are there any significant changes from 2.5.2 that can impact the code to
> constantly reboot?
>
>
>
>
> Regards, Thomas
>
>
> 2013/9/23 Matt Beard OVMS <smvo at mxf.org.uk>
>
>> OK - either this code is broken, or my OVMS is.
>>
>> I flashed the code and set the unit up - no go, kept rebooting and the
>> GPRS does not work.
>>
>> Rebuild from clean. Reflashed, reloaded settings and still constant
>> rebooting and GPRS does not work.
>>
>> Matt
>>
>>
>>
>> On 23 September 2013 10:24, Thomas Bergo <thomas.bergo at gmail.com> wrote:
>>
>>> Have tested and fixed a lot of errors this weekend. and i believe that
>>> the code is now in a state where it can be merged into the main project.
>>>
>>> Have pushed a release 1.3 to my fork on GitHub.
>>>
>>> Changes:
>>> 1.3 23.09.13 (Thomas)
>>> - Fixed charging notification when battery is full, SOC=100%
>>> - TODO: Fix battery temperature reading.
>>> 1.2 22.09.13 (Thomas)
>>> - Fixed Ideal range
>>> - Added parking timer
>>> - Added detection of car is asleep.
>>> 1.1 21.09.13 (Thomas)
>>> - Fixed ODO
>>> - Fixed filter and mask for poll0 (thanks to Matt Beard)
>>> - Verified estimated range
>>> - Verified SOC
>>> - Verified Charge state
>>> - Added battery temperature reading (thanks to Matt Beard)
>>> 1.0 Initial release
>>>
>>> Regards, Thomas
>>>
>>>
>>>
>>> 2013/9/21 Thomas Bergo <thomas.bergo at gmail.com>
>>>
>>>> Thanks to you all for participate.
>>>>
>>>> Managed to spend some time on this project yesterday and this this
>>>> evening.
>>>>
>>>> Yesterday i was able to fix the ODO. And thanks to Matt i was able test
>>>> the SOC, ideal range and Charge state.
>>>> Added the battery temperature reading form Matt's code.
>>>>
>>>> My car is reporting range and ODO in Km, so added support to handle
>>>> both miles and Km for ODO and Range based on can_mileskm.
>>>>
>>>> *"To receive all 0x3nn messages we could use filter SID 0x300 and mask
>>>> 0x700, but I am worried that may cause a flood of messages."*
>>>> The current code runs with this filter and mask, ans seems to be stable
>>>> so far.
>>>>
>>>> Still see some errors with the ideal range and the temperature reading.
>>>> The app is reporting PEM: -125C, Motor: 144C and Battery: 5C
>>>>
>>>> Pushed the code with updates from Matt to GitHub.
>>>>
>>>> Regards, Thomas
>>>>
>>>>
>>>> 2013/9/21 Michael Jochum <mikeljo at mac.com>
>>>>
>>>>> Hi,
>>>>>
>>>>> You can only set the Mask and Filter in a Configuraton Mode.
>>>>>
>>>>> From Datasheet:
>>>>>
>>>>> 23.3.1 CONFIGURATION MODE
>>>>>
>>>>> The CAN module has to be initialized before the activation. This is
>>>>> only possible if the module is in the Configuration mode. The Configuration
>>>>> mode is requested by setting the REQOP2 bit. Only when the status bit,
>>>>> OPMODE2, has a high level can the initial- ization be performed.
>>>>> Afterwards, the Configuration registers, the Acceptance Mask registers and
>>>>> the Acceptance Filter registers can be written. The module is activated by
>>>>> setting the REQOP control bits to zero.
>>>>>
>>>>> The module will protect the user from accidentally violating the CAN
>>>>> protocol through programming errors. All registers which control the
>>>>> configuration of the module can not be modified while the module is on-
>>>>> line. The CAN module will not be allowed to enter the Configuration mode
>>>>> while a transmission or reception is taking place. The Configuration mode
>>>>> serves as a lock to protect the following registers:
>>>>>
>>>>> • ConfigurationRegisters
>>>>> • FunctionalModeSelectionRegisters • BitTimingRegisters
>>>>> • IdentifierAcceptanceFilterRegisters •
>>>>> IdentifierAcceptanceMaskRegisters • FilterandMaskControlRegisters
>>>>> • MaskSelectionRegisters
>>>>>
>>>>> In the Configuration mode, the module will not transmit or receive.
>>>>> The error counters are cleared and the interrupt flags remain unchanged.
>>>>> The programmer will have access to Configuration registers that are access
>>>>> restricted in other modes.
>>>>>
>>>>> -----------
>>>>>
>>>>> I don't believe that it will work without bad sideeffects.
>>>>>
>>>>> Bye
>>>>> michael
>>>>>
>>>>>
>>>>> Am 21.09.2013 um 11:32 schrieb Matt Beard OVMS <smvo at mxf.org.uk>:
>>>>>
>>>>> I may also try modifying the RX0 mask during the 1-second poll so that
>>>>> it cycles through filtering a single SID each time, meaning that it will
>>>>> take 4 seconds for a full update. I don't think this will be an issue as
>>>>> none of this data is fast changing.
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>
>>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130923/5a2ad7d1/attachment.htm>
More information about the OvmsDev
mailing list