Closed gluca closed 9 years ago
markwj
commented
10 years ago Please make sure you are building in 'release' mode, not 'debug' mode. I also suggest you try without OVMS_LOGGINGMODULE defined.
Does the normal RT specific build work for you?
gluca
commented
10 years ago Normal rt builds. It seems udata segment VEHICLE cannot handle battmon data (191 bytes) even with overlays. Il 03/giu/2014 03:27 "Mark Webb-Johnson" notifications@github.com ha scritto:
Please make sure you are building in 'release' mode, not 'debug' mode. I also suggest you try without OVMS_LOGGINGMODULE defined.
Does the normal RT specific build work for you?
— Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44910672 .
markwj
commented
10 years ago Can you try without OVMS_LOGGINGMODULE?
gluca
commented
10 years ago Still having such error.
Error - section 'VEHICLE' can not fit the section. Section 'VEHICLE' length=0x00000043 Errors : 1 make[2]: *\ [dist/V2_RT_Production_CFG_BATTMON/production/OVMS.X.production.hex] Error 1
I have the free version of the compiler. As stated it doesn't make any optimization. Maybe the error is related to that?
Gianluca Magalotti ITIL V3 Certified
email: gianluca@magalotti.net Mob: +39 340 7418648 Mob: +39 3474 3474 25 Linkedin: http://www.linkedin.com/in/gianlucamagalotti/
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
— Reply to this email directly or view it on GitHub.
gluca
commented
10 years ago Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
— Reply to this email directly or view it on GitHub.
dexterbg
commented
10 years ago Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
gluca
commented
10 years ago Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 — Reply to this email directly or view it on GitHub.
dexterbg
commented
10 years ago The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
gluca
commented
10 years ago Ok. Now I've added a full featured configuration for twizy.
Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:
The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26 — Reply to this email directly or view it on GitHub.
bobbo3
commented
10 years ago I am trying to understand the logging vs. history records, but can not put this in context. Can someone please make a brief summary of what it is and how it is used? I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?
On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:
Ok. Now I've added a full featured configuration for twizy.
Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:
The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub.
markwj
commented
10 years ago The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.
The user can retrieve the log records either via the raw or http apis.
Regards, Mark.
On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:
I am trying to understand the logging vs. history records, but can not put this in context. Can someone please make a brief summary of what it is and how it is used? I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?
On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:
Ok. Now I've added a full featured configuration for twizy.
Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:
The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.
bobbo3
commented
10 years ago Thanks Mark,
How does the user opt-in? Is this a feature? If yes, what id?
On Wednesday, June 4, 2014 2:02 AM, Mark Webb-Johnson notifications@github.com wrote:
The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.
The user can retrieve the log records either via the raw or http apis.
Regards, Mark.
On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:
I am trying to understand the logging vs. history records, but can not put this in context. Can someone please make a brief summary of what it is and how it is used? I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?
On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:
Ok. Now I've added a full featured configuration for twizy.
Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:
The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub.
markwj
commented
10 years ago In ovms.h:
So, setting feature 13 to 6 should log both drives and charges.
Regards, Mark.
On 4 Jun, 2014, at 2:17 pm, bobbo3 notifications@github.com wrote:
Thanks Mark,
How does the user opt-in? Is this a feature? If yes, what id?
On Wednesday, June 4, 2014 2:02 AM, Mark Webb-Johnson notifications@github.com wrote:
The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.
The user can retrieve the log records either via the raw or http apis.
Regards, Mark.
On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:
I am trying to understand the logging vs. history records, but can not put this in context. Can someone please make a brief summary of what it is and how it is used? I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?
On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:
Ok. Now I've added a full featured configuration for twizy.
Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:
The logging module is not used by the Twizy firmware.
Don't confuse logging with the server/history record functionality, that will work without the logging module.
The logging module provides a charge log, a more simple version of that feature also is available in the Twizy firmware by means of history records.
Regards, Michael
Am 03.06.2014 11:04, schrieb Gianluca:
Ok, in the configuration I've excluded logging.c from build and now it works. Now I've enabled OVMS_DIAGMODULE too and it works.
This means if battery monitor is needed no logging available, right?
Is there any way to avoid this?
Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:
Gianluca,
check if the actual acc and logging modules also are excluded from the build (.o files context menu).
Regards, Michael
Am 03.06.2014 08:03, schrieb Gianluca:
Ok, some other info. I've tried using BATTMON and removing CFG. Now it states: Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040
Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.
Gianluca Magalotti
Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:
Can you try without OVMS_LOGGINGMODULE?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub
https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44923110.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/openvehicles/Open-Vehicle-Monitoring-System/issues/132#issuecomment-44940462.
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.
Building twizy version with: OVMS_CAR_NONE OVMS_CAR_RENAULTTWIZY OVMS_HW_V2 OVMS_LOGGINGMODULE OVMS_INTERNALGPS OVMS_TWIZY_CFG OVMS_TWIZY_BATTMON
produce a link error (section VEHICLE. can not fit the section. Section VEHICLE length=0x00000043
Building with MpLab X and C18 v3.40 for os x (free version)