Compilation issues, OVMS.X/v2_RT with Battmon and Cfg
Hi, Willing to use Michael’s last commit featuring "save/load sevcon profile » commands, I pulled the latest code and went to MPLab X IDE v2 (c18 v3.40). Alone it compiles fine. But if I add OVMS_TWIZY_BATTMON and OVMS_TWIZY_CFG (to a duplicated from V2_RT_Production conf) to the definitions I end up on a : "/Applications/microchip/mplabc18/v3.40/bin/mplink" -p18f2685 -w -m"build/memorymap" -u_EXTENDEDMODE -z__MPLAB_BUILD=1 -u_CRUNTIME -l "/Applications/microchip/mplabc18/v3.40/bin"/../lib -o dist/Copy_of_V2_RT_Production/production/OVMS.X.production.cof build/Copy_of_V2_RT_Production/production/UARTIntC.o build/Copy_of_V2_RT_Production/production/crypt_base64.o build/Copy_of_V2_RT_Production/production/crypt_hmac.o build/Copy_of_V2_RT_Production/production/crypt_md5.o build/Copy_of_V2_RT_Production/production/crypt_rc4.o build/Copy_of_V2_RT_Production/production/led.o build/Copy_of_V2_RT_Production/production/net.o build/Copy_of_V2_RT_Production/production/net_msg.o build/Copy_of_V2_RT_Production/production/net_sms.o build/Copy_of_V2_RT_Production/production/ovms.o build/Copy_of_V2_RT_Production/production/params.o build/Copy_of_V2_RT_Production/production/utils.o build/Copy_of_V2_RT_Production/production/inputs.o build/Copy_of_V2_RT_Production/production/diag.o build/Copy_of_V2_RT_Production/production/vehicle_twizy.o build/Copy_of_V2_RT_Production/production/vehicle.o build/Copy_of_V2_RT_Production/production/vehicle_none.o build/Copy_of_V2_RT_Production/production/logging.o MPLINK 4.40, Linker Device Database Version 1.3 Copyright (c) 1998-2011 Microchip Technology Inc. Error - section 'VEHICLE' can not fit the section. Section 'VEHICLE' length=0x00000043 Errors : 1 make[2]: *** [dist/Copy_of_V2_RT_Production/production/OVMS.X.production.hex] Error 1 make[1]: *** [.build-conf] Error 2 make: *** [.build-impl] Error 2 Can actually all the Definitions fit ? Am I doing anything wrong or is my setup wrong? Thanks, Julien. PS: Twizy ravaged friday night, they took everything but the OVMS, breaking the glovebox, including half of the smartphone holder making it useless even for the stealer… cool :( -- Julien (JaXX) Banchet
Hi Julien, Am 02.03.2014 15:01, schrieb Julien (JaXX) Banchet:
"/Applications/microchip/mplabc18/v3.40/bin/mplink" ... build/Copy_of_V2_RT_Production/production/*logging.o*
you need to exclude the logging.c module from the build (via file properties) & disable the OVMS_LOGGINGMODULE switch.
Julien. PS: Twizy ravaged friday night, they took everything but the OVMS, breaking the glovebox, including half of the smartphone holder making it useless even for the stealer… cool :(
Sad to read. I guess smart thieves don't need to break into gloveboxes. Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
De: Michael Balzer dexter@expeedo.de
Hi Julien,
Am 02.03.2014 15:01, schrieb Julien (JaXX) Banchet:
"/Applications/microchip/mplabc18/v3.40/bin/mplink" ... build/Copy_of_V2_RT_Production/production/*logging.o*
you need to exclude the logging.c module from the build (via file properties) & disable the OVMS_LOGGINGMODULE switch.
Bingo ! Thanks, thought that was essential :-)
Julien. PS: Twizy ravaged friday night, they took everything but the OVMS, breaking the glovebox, including half of the smartphone holder making it useless even for the stealer… cool :(
Sad to read. I guess smart thieves don't need to break into gloveboxes.
Or they’d know that nobody with a twizy would leave anything worthy of breaking things, oh well… It does bring me to a point: Using some remaining GPIO ports, 1 in (microwave presence sensor), and 1 or 2 out (for a relay or siren, or siren plus a calmer beeper), could we make a simple alarm system ? Detection: Sends optional SMS and sends a short beep every second or a message until a CAN bus message (or something else) gives it legitimate state, or alarm deactivated by message/app/ovms server. After a settable amount of seconds if still detecting, SMS, alarm goes off, until legitimate state or deactivation. It would, activate on it’s own, key off after presence left, etc... Well you get the idea of an alarm system. The device is getting a bit cramped up in features, but could it fit ? The awesome would be having an RFID on I2C/TWI to badge in :-) I have so many of rfid devices in my drawers in storage, I seriously need an apartment with an extra room :-) Tried getting in touch with the Renault Engineers who were part of the TwizyWay project of Saint-Quentin en Yvelines (Self service Twizy on subscription, Geofenced to the city, using a Mifare badge, no keys otherwise, M2M reporting position&energy state, etc...) but without any luck… well, they’ll probably tell me they bought it off the shelf or got it done by someone else… JaXX, Would love 3 day weekends to have time./. -- Julien (JaXX) Banchet
participants (2)
-
Julien (JaXX) Banchet -
Michael Balzer