Tesla Model 3: What we know!

Yes! I did it! I ordered my Model 3 🙂 It was a great day and seeing all the people talking to each other has been and extraordinary experience for me. This blog entry gives an overview of all the features that has been announced in the first unveil or by Elon Musk via Twitter – as he answers a lot of questions there!

Features from unveil:

  • 215 Miles range
  • 0-60mph (100km/h) in under 6 seconds
  • Comfortable seating for 5 adults
  • 5-star Safety Rating
  • Supercharging ‚capability‘
  • 35.000$
  • Full glass roof

Even more features

But even more features have been announced via Twitter. Here’s a list with more features!

Some speculations

As you can see in the variety of pictures, the Model 3 has a single monitor in the front. Elon says it will make sense after part 2 of the unveil. Twitter.

The actual steeing controls will be different. Twitter.

A bike will still fit in the trunk! Twitter.

Some more facts

Compiling a C++ project for STM32F4 Discovery with RAW GCC Toolchain and without any IDE

Makefile


STLINK_PATH=<PathTo "ST-LINK Utility"> GCC_PATH=<PathTo "GCC"> DICOVERY_FIRMWARE_PATH=<PathTo "DisoceryFirmware"> CMSIS_PATH=$(DICOVERY_FIRMWARE_PATH)/Libraries/CMSIS
CMSIS_DEVICE_PATH=$(CMSIS_PATH)/ST/STM32F4xx/
DISCOVERY_PATH=$(DICOVERY_FIRMWARE_PATH)/Utilities/STM32F4-Discovery
STDPERIPH_PATH=$(DICOVERY_FIRMWARE_PATH)/Libraries/STM32F4xx_StdPeriph_Driver
STARTUP=startup_stm32f4xx.S
FILES="$(STDPERIPH_PATH)/src/stm32f4xx_rcc.c" $(STDPERIPH_PATH)/src/stm32f4xx_gpio.c $(STDPERIPH_PATH)/src/stm32f4xx_exti.c $(STDPERIPH_PATH)/src/stm32f4xx_syscfg.c $(STDPERIPH_PATH)/src/misc.c $(DISCOVERY_PATH)/stm32f4_discovery.c $(CMSIS_DEVICE_PATH)/Source/Templates/system_stm32f4xx.c

OPTIONS=-nostartfiles -mfpu=fpv4-sp-d16 -mthumb –specs=nosys.specs -ffunction-sections -fdata-sections -Os -flto -T STM32F407VG_FLASH.ld –std=c++11 -v -Wall
LIBRARIES=-I“.“ -I$(CMSIS_PATH)/Include -I$(STDPERIPH_PATH)/inc -I$(DISCOVERY_PATH) -I$(CMSIS_DEVICE_PATH)/Include
DEFINES=-DUSE_STDPERIPH_DRIVER -DUSE_STM32_DISCOVERY -DHSE_VALUE=8000000

%.elf : main.c $(STARTUP)
„$(GCC_PATH)“\arm-none-eabi-g++.exe $(OPTIONS) $(DEFINES) $(LIBRARIES) -o $@ $? $(FILES)

%.bin : %.elf
„$(GCC_PATH)“\arm-none-eabi-objcopy.exe -O binary $< $@

%.upload : %.bin
$(STLINK_PATH)/ST-LINK_CLI.exe -V -P $< 0x08000000
$(STLINK_PATH)/ST-LINK_CLI.exe -Rst

all: blinky.upload

Mixing styles from an attribute and .style in dart in a polymer element

I came across this behaviour by chance. Imagine the following code that is used in a custom polymer element:

...
<polymer-element...>
<template>
...
<div id="foo" style="width: {{ totalWidth }}px;"></div>
...
</template>
</polymer-element>
...

And in Dart I tried the following:

$['foo'].style.backgroundImage = 'url('+imgAsBase64+')';

I tried all different syntaxes of URL()… but never got it working. What happens here is pretty simple: I tried to set the backgroudn image via the style attribute before the style attribute was evaluated by polymer. So the re-rendering (because I changed totalWidth also) overwrites my changes. Mixing is complicated that’s why I finally put it all into the HTML Code:

...
<polymer-element...>
<template>
...
<div id="foo" style="width: {{ totalWidth }}px; background-image: url({{ img }});"></div>
...
</template>
</polymer-element>
...

My blog

I have been thinking for years now if I should start blogging or not. Finally I decided to do so 🙂

I will be blogging about all web topics I will deal with. Nevertheless I want to focus on Dart + Polymer I have been working on recently.