ETS2/ATS Telemetry Web Server + Mobile Dashboard

[Funbit]

I'm sorry then But it would be great to have both logical & physical gear in the telemetry as proposed by the supric.

@klauzzy:
Nice installation!

[romabysen]

Well, I can report that the 64bit build of the plugin works just fine. However, when I launch Ets2Telemtry.exe as an Administrator I get a warning, "Exception has been thrown by the target of an invocation", and then the apps start but it's bound to the autoconfig address (169.254.*.*). Since it does not happen when running as a regular user I'm guessing it has something to do with enumerating network interfaces.
Perhaps it would be good to have an option to specify what interface (or address) to bind to.

[SiSL]

That error happens when you have more than 1 Network Interface...

OP has been offered a fix for that already

[Funbit]

I'm sorry for this bug with multiple network interfaces.

The updated server (Version 1.0.1) is available for download from the same URL as before:
https://github.com/Funbit/ets2-telemetry-server

Issues fixed in 1.0.1:

- Fixed bug with multiple network interfaces (thanks to thorerik)
- Made application run under Administrator by default (thanks to thorerik)
- Updated application icon and added it to the HTML app
- Minor refactoring and bug fixes (including HTML app)

[Funbit]

The server is updated to version 1.0.2:
https://github.com/Funbit/ets2-telemetry-server

1.0.2 changes:

- Refactored gauge screen fitting algorithm, the app should work in any modern browser now (gauge automatically fits into desktop browsers now too!)
- Added logging
- Added support for binding on a particular network interface
- Added Cordova mobile application (compiled Android APK is included in the bundle!)
- Various fixes and improvements
- Made HTML5 application URL shorter

[klauzzy]

Very nice!! I´m working something with your gauge.....I´ll send it to you today. I think you`ll like it

[Funbit]

The server is updated to version 1.0.3:
https://github.com/Funbit/ets2-telemetry-server

1.0.3 changes:

- Fixed bug with invalid day of the week
- Improved connection stability
- Completely decoupled gauge design and gauge update engine (coded in Typescript) so it is easier to create custom skins
- Added some scripts to simplify the installation for new users
- Updated Android application

2klauzzy: Looking forward to

PS. I'm going to be pretty busy next week so probably there won't be any major updates. But the current version is pretty stable and thoroughly tested on the following devices and browsers: iPhone 6 Plus, Galaxy Note 1/2, Kindle Fire HD, Galaxy Tab S, Firefox 34, Chrome 39, IE 11.

[klauzzy]

[ external image ]
[ external image ]

My skin for your fantastic gauge



In the moment i have some problems i can´t solve by my own...

- the tachometer and the speedometer are to long....if i make them shorter they dont show the correct speed/rpm
- i cant find the correct position of the fuel- and temperature arrow


PS. i´ll create the background skin completely new to be looking as perfect as possible.....that skin was only a test to see if my idea is working or not

[Funbit]

Wow, looks cool!

As for the meter arrows, here is the explanation of how it works:

index.html
There are some data attributes for meter divs:
data-min-angle: angle in degress for the arrow for data-min value (0 = vertical)
data-max-angle: angle in degress for the arrow for data-max value
data-min: minimal possible value (in JSON response)
data-max: maximum possible value (in JSON response)
data-prev: internal usage only

style.less
transform-origin: defines the central point of your analog meter, i.e. pivot point (calculation starts from the top-left point of your arrow)
transform rotate: defines the angle of the arrow (0 = vertical, negative = left, positive = right); initial value is not important, it will be changed automatically by the app (it is just useful to have it in CSS for debugging)
left,top: left and top point of the top-left corner of the arrow (when it is in vertical position)
width,height: width and height of the arrow

To make it a bit more comprehensible I drew a diagram to explain speedometer values:

left: 571px;
top: 121px;
width: 10px;
height: 110px;
transform: rotate(-114deg);
transform-origin: 50% 440px;
data-min="0" (0 km/h)
data-max="140" (140 km/h max, if values goes further - it will stay on 140 anyway)
data-min-angle="-114" (-114 degrees for 0 km/h value)
data-max-angle="+114" (+114 degrees for 140 km/h value)

[ external image ]

Also, please note that your background is a little bit skewed, and the gauge assumes linear arrow moving. So the final arrow may shift for a couple of pixels no matter what values you set in CSS.

[denilsonsa]

Excellent! This HTML-style dashboard is exactly what I wanted!

Wishes:

• Show when Cruise Control is enabled. I see the HTML element is there, but I don't see it lighting up when I enable CC.
• Show the air pressure. This is important because of the brakes.
• Show how much time I have left to the delivery deadline. (it currently shows the absolute value, but I need to do the math in my head)
• To make it easier to read, I'd move the Deadline line next to the current time. That way, the time/date should line up and will be next to each other, so they will be easier to read and to compare.
• Show fuel consumption, and how far can I still drive with the remaining fuel (how many kilometers).
• Show parking brake and retarder brake.
• Turn things off when the engine is off.
• Show a compass, or at least the current heading direction. (I've seen this Arduino-based prototype showing the heading, so it can be done)

Wishes that most likely need to wait until the SDK exposes these variables:

• Show the current Cruise Control speed (maybe as a green arrow, similar to the "speedometer-arrow" element).
• Show the speed limit for the current road (maybe as a yellow arrow).
• Show the current fatigue level, and how long until the next rest.

I noticed that when I press the "light horn" button, which is the one that blinks the high beam, nothing lights up in the telemetry. Not sure if this is a limitation of the SDK. Likewise, having high beam enabled will disable the low beam indicator (while the in-game dashboard shows both, again, maybe a limitation of the SDK)