Tinkla Buddy Configuration

What is Tinkla Buddy?

Tinkla Buddy Install Kit

Installing your Tinkla Buddy

Configuring your Tinkla Buddy

Expand

Registering your Tinkla Buddy

In order for your Tinkla Buddy to operate, it needs certificates which are given by the Tinkla server to those that registered their product. When you register your device you receive a free 14 day trial period. During this time your Tinkla Buddy has full functionality.

30 days prior to your the expiration of your license or trial period, you have the option to purchase or renew the yearly subscription using the built in PayPal connection.

Once your trial or license period expires, all functionality on the Tinkla Buddy is removed until you purchase / renew your license.

To register your Tinkla Buddy first you need to create an account on tinkla.us AND confirm your email.

Once you have your tinkla.us account setup, you can register your Tinkla Buddy using the Tinkla Buddy Admin portal.

Once you have verified your credentials, you will be required to enter your personal information as well as select your email notification preferences. These settings can be later changed from the Account menu, by selecting User Preferences

Now it is time to finally register your Tinkla Buddy. You will need to know the VIN of the car you are installing the Tinkla Buddy on. From the main menu select Tinkla Buddy and then Register. Enter your VIN and a nickname for your car. The nickname can be later changed by clicking on it in the details page for your Tinkla Buddy. The VIN can not be changed, so please double check it before creating the record.Then click the Save button.

You will notice that for now your Tinkla Buddy record has no data. The Buddy Software, Tesla Software fields will be empty and the Last Signal and Cert Update fields will show dates in the past. Do not worry, they will get updated the moment your Tinkla Buddy gets its certs for the first time.

It is now time to power up your Tinkla Buddy for the first time.

Expand

Using the Tinkla Buddy Admin portal

Expand

Using the Tinkla Menu

The Tinkla Menu has various basic configuration settings you can activate. You can activate the menu with either four presses on the Wheel's Menu button or (if you're parked) four presses on the Parking Brake. Expand section for more details.

If you plan to use email to send screenshots, please make sure you setup your email address correctly in /home/pi/.tinkla/email_settings. Please allow at least 20 seconds between requests to allow the command to complete. CID screen shot only works if you have persistence enabled.

1. Tinkla
   
   • Buddy
     
     • Restart - Restarts Tinkla Buddy's processes.
     • Reboot - Reboots Tinkla Buddy, entirely. (Not recommend)
     • Update - Checks for a Tinkla Buddy update.
     • Quiet - Puts the device in a quiet mode for Service Center visits.
   • Wifi
     
     • Info - This shows the current Wireless Access Point name and password to join the network and use your car's 3g or LTE internet.
   • IC Int. - Here you can Turn Integration On or Off
     
     • IC integration allows OpenPilot to appear on the Instrument Cluster similar to Tesla AutoPilot. It also shows data from your Baolong TPMS as if you have a Conti TPMS retrofit.
     • Please note: it can take up to a minute for your IC to restart the processes in integration mode and it will flicker twice during the process. The IC isn't rebooted, just restarting processes.
   • Tunnels - Here you can turn Tunnels On or Off
     
     • Turning tunnels on allows you to use the Tinkla Bastillion server to SSH into your Tinkla Buddy and it enables the remote control app (in development)
2. Tesla
   
   • Tokens - If you are a security researcher and have access to your car's systems, you'll be able to see it here.
   • Ludi
     
     • Temps - This option adds a temperature gauge to the bottom left third of the power graph when using IC Int.
     • On - This option adds the temperature gauge from above, shows a wireframe of your car exposing front and rear motors, and adds a power value and peak usage graph to the left side of your IC.
     • Off - Disables all of the Ludi additions.
   • Misc
     
     • VLow - Sets air suspension very low (your car must be parked to enable).
     • IC SS - <Known Bug> This will take a screenshot of your IC and email it to you. (You'll need to SSH into Tinkla Buddy to configure /home/pi/.tinkla/email_settings)
     • CID SS - This will take a screenshot of your Central Infotainment Display [CID] and email it to you. (You'll need to SSH into Tinkla Buddy to configure /home/pi/.tinkla/email_settings). CID screen shot only works if you have persistence enabled!
   • Advanced
     
     • Dev - This will enable you to access Dev Mode.
     • Fact - This will enable you to enter Factory Mode.
     • Unlock -This will unlock the Diagnostic Port.
     • Kill - This will kill any staged software updates.
3. Info
   • ...
4. Custom
   
   • This set of menus are for your use to add/run your own menu scripts to run from the Tinkla Buddy and show the results on your CID. All additions and changes will need to be added to your Tinkla Buddy via SSH to /home/pi/.tinkla/your_commands.json
     

Expand

Using the Tinkla Access Point webapp

Setup WiFi for access to Tinkla Buddy App.

First activate the TB on your CID using either the wheel menu button or (if parked) parking button four times. Select Tinkla.

Then select WiFi.

Then select On, to turn on the WiFi SSID.

On your Cell phone look for the SSID tinklaAP, the WiFi password is teslaFr33

Select the SSID and it will assign an IP (it may tell you there is no internet). The next thing to do is go to your favorite browser on the phone, and enter the following URL http://10.5.5.1

You will be presented with the log in screen. The first time password is 1234

Then of course hit Login

Now you can start exploring.

Expand

Customize Tinkla Menu

In the /home/pi/.tinkla folder there is a file called your_commands.json Where the custom menu items should be added. There are already examples in the file you can follow.

For long command sequences it is best to create a script in /home/pi/.tinkla and just call the script with something like /bin/bash /home/pi/.tinkla/my_script.sh from the your_commands.json.

{"menu":[
{"id":1000,"text":"The file that generates this section is /home/pi/.tinkla/your_commands.json. The base menu for it has ID 1000 and we suggest to keep all the other submenus you might create with unique IDs above 1000. Look at the file for suggestions how to create custom commands. ","options":[
{"label":"Menu","type":"menu","value":"1001"}, #this will open the menu defined as id:1001
{"label":"Reboot TB","type":"shell","value":"reboot"}, #this sends "reboot" as a command. 
{"label":"Some Script","type":"shell","value":"/bin/bash /home/pi/.tinkla/my_script.sh"} #no comma after the last option.
]},
{"id":1001,"text":"This is just an example of a submenu. Here I just defined 1 button. The Back button is added automatically to any Menu.","options":[
{"label":"Main Menu","type":"menu","value":"1"}
]}                                                                                                              ]}

To run a script on the CID, and as long as you have persistence enabled, then you can include these commands inside my_script.sh to have some thing run on the CID:

scp CID_script.sh cid:/tmp/CID_script.sh
ssh cid bash /tmp/CID_script.sh
ssh cid rm /tmp/CID_script.sh

Expand

Cron Jobs

If you already have persistence setup, then you can have scripts set to run periodically based on where you place your script.sh. Based on the directory you use, you can have a script run afterReboot (MCU reboot, not Tinkla Buddy), every 1, 5, 15, or 60 minutes.

Scripts within these folders MUST have filenames ending in .sh.

/opt/tinkla/cron/afterReboot
/opt/tinkla/cron/everyOneMinute
/opt/tinkla/cron/everyFiveMinutes
/opt/tinkla/cron/everyFifteenminutes
/opt/tinkla/cron/everyHour

For those users that have root persistence, I recommend adding a clean_traces.sh file to the /opt/tinkla/cron/everyOneMinute folder containing the following code

sed -i '/192\.168\.90\.101/d' /var/log/sshd/current
sed -i '/key type ssh-dss not/d' /var/log/sshd/current
cat /dev/null > /var/log/auth.log
echo 'set +o history' > /root/.bashrc
cat /dev/null > /root/.bash_history
echo 'set +o history' > /home/tesla/.bashrc
cat /dev/null > /home/tesla/.bash_history

If you have root persistence and want the AutoPilot screen on CID, create a script called ap_screen.sh in the /opt/tinkla/cron/afterReboot folder containing this code:

edit-settings-conf.pl -a vapi/forceHasAutopilot=true
edit-settings-conf.pl -a vapi/forceHasDriveOnNav=true
edit-settings-conf.pl -a vapi/forceHasDriveOnNavMaps=true
/usr/local/bin/sdv GUI_autopilotAlwaysOn true
/usr/local/bin/sdv GUI_autosteerOnRequest true
/usr/local/bin/sdv GUI_autosteerDisabled false
/usr/local/bin/sdv GUI_accFromZero true
/usr/local/bin/sdv DAS_mapAvailability true
/usr/local/bin/sdv GUI_redLightStopSignOnRequest true
/usr/local/bin/sdv GUI_enableMapStops true
/usr/local/bin/sdv GUI_enableVisionStops true
/usr/local/bin/sdv GUI_enableFSDFunctions true
/usr/local/bin/sdv GUI_stopAndGo true
/usr/local/bin/sdv GUI_noaEverywhere true
/usr/local/bin/sdv DAS_navAvailable true
/usr/local/bin/sdv GUI_accFollowDistance 2
/usr/local/bin/sdv GUI_accOvertakeOnRequest true
/usr/local/bin/sdv GUI_autopilotControlRequest 0
/usr/local/bin/sdv FEATURE_dasDriveOnNavEnabled true
/usr/local/bin/sdv FEATURE_dasDriveOnNavMapsOkay true
/usr/local/bin/sdv VAPI_backupCameraCalibrated true
/usr/local/bin/sdv VAPI_fisheyeCameraCalibrated true
/usr/local/bin/sdv VAPI_lPillarCameraCalibrated true
/usr/local/bin/sdv VAPI_lRepeaterCameraCalibrated true
/usr/local/bin/sdv VAPI_mainCameraCalibrated true
/usr/local/bin/sdv VAPI_narrowCameraCalibrated true
/usr/local/bin/sdv VAPI_rPillarCameraCalibrated true
/usr/local/bin/sdv VAPI_rRepeaterCameraCalibrated true
echo "1" > /var/etc/dashw
echo "dashw 1" >> /var/etc/gateway.cfg
echo "autopilot 1" >> /var/etc/gateway.cfg
stop qtcar-audiod
stop qtcar
stop qtcar-carserver
start qtcar-carserver
start qtcar
start qtcar-audiod

References