Tips

From Unofficial Tesla Tech
Jump to navigation Jump to search

Some brief tips that you might like to have in your explorations.

Errors Which are Unrelated -- 2012-2016

Seeing intermittent, or several seemingly unrelated errors? Model S' had a problem with a ground stud breaking off, and sometimes intermittently making contact. It's located on the inside of the front frame rail on the right (passenger's) side.

If you find this, it is not possible to fix the old stud, you'll have to drill a new hole and either tap it or use a self-tapping bolt. Scrape the frame rail around the hole to expose the aluminum, and coat with silicone grease. ("dielectric grease", auto parts store) Also coat the wire connectors with grease and reassemble.

It'd be best if we didn't have to depend on the threads in the frame rail, but in most cases there is no access to the other side of the surface. Sure you could drill a larger hole in the top or other side of the frame rail but this is not adviseable as this is a crash structure, and safety is most important.

Hardware Details

For exquisite details on just about all aspects of Tesla hardware and functions, click over to TeslaTap Undocumented.

Kernel Configuration

Tesla likes to compile all modules into the kernel rather than have them load as modules, which makes sense to save space. (So hint, hint get rid of /lib/modules/2.6.36.2, 2.6.36.2, etc)

But inquiring minds want to know, how do we find out what settings our current kernel is compiled with?

# zcat /proc/config.gz
# zcat /proc/config.gz |grep LOG

Rebooting

On the CID or IC if you do a simple 'reboot', You're Doing It Wrong™. Tesla was forced into the silly 'emits' system of Upstart. This tries to coordinate actions with subsystems like udev, etc.

  • Reboot IC - # emit-reboot-cluster
  • Reboot CID - # emit-reboot-cid
  • Reboot the gateway, CID, IC, and every ECM in the car - # emit-reboot-gateway

Please use these rather than having the temptation to issue a simple 'reboot'.

Ubuntu Release - Which Am I?

Wondering which zany Ubongo release you are at? That's easy.

Get your kernel version with the (very intuitive) command:
# uname -r

... and look it up in this handy table:

20.04   Focal Fossa       5.4		12.04   Precise Pangolin  3.2
19.10   Eoan Ermine       5.3		11.10   Oneiric Ocelot    3.0
19.04   Disco Dingo       5.0		11.04   Natty Narwhal     2.6.38
18.10   Cosmic Cuttlefish 4.18		10.10   Maverick Meerkat  2.6.35
18.04   Bionic Beaver     4.15		10.04   Lucid Lynx        2.6.32
17.10   Artful Aardvark   4.13		09.10   Karmic Koala      2.6.31
17.04   Zesty Zapus       4.10		09.04   Jaunty Jackalope  2.6.28
16.10   Yakkety Yak       4.8		08.10   Intrepid Ibex     2.6.27
16.04   Xenial Xerus      4.4		08.04   Hardy Heron       2.6.24
15.10   Wily Werewolf     4.2		07.10   Gutsy Gibbon      2.6.22
15.04   Vivid Vervet      3.19		07.04   Feisty Fawn       2.6.20
14.10   Utopic Unicorn    3.16		06.10   Edgy Eft          2.6.17
14.04   Trusty Tahr       3.13		06.06   Dapper Drake      2.6.16
13.10   Saucy Salamander  3.11		05.10   Breezy Badger     2.6.12
13.04   Raring Ringtail   3.8		05.04   Hoary Hedgehog    2.6.10
12.10   Quantal Quetzal   3.5		04.10   Warty Warthog     2.6.8

At the monent I'm on kernel 4.4.35-release-03mar2017-g352318b-dirty (firmware 18.36.2), so that is "'Xenial Xerus'". How embarrassing...

This is useful for example, when you want to graft in an executable, from somewhere in Ubongo's ARM ecosystem;  you want to graft in one from your epoch. Chances are though it'll need a library, so if it fails run an
# strace {whatevertheexeis}.

WiFi Connexion Problems?

When your car connects to your wireless network it looks for multimedia devices like blu-ray players and streaming TV boxes, using DNLA. Some devices confuse the Tesla, causing the Wi-Fi/Bluetooth radios to reset. When the car connects again the cycle repeats.

Isolate your car from your multimedia and other devices by having it connect to a "guest" network on your router (or if your router/AP can do it, a second/third/fourth SSID) and the problem goes away. Make sure your guest network has "intranet" access disabled. (or, sometimes this means "private" mode enabled)


Carl A. Cook