Auto(re)connect

[ARCTiC]

I know there's a function to autoconnecting the interface at the startup... but i was thinking if there's a way to have it autoconnect in the event that the connection being lost.
Here's my situation: when i hybernate the PC (i'm referring to a CarPC) and i resume, Dashcommand is indeed already opened, but then my ODB is disconnected, so i would like to know if there's a way to keep it trying to reconnect, or if there'll be one in the future (update).
Thanks.

[Pierre@PPE]

Hi,

Auto re-connect is on our list of things to add to DashCommand. It's a high priority too but there's a major technical hurdle in the way but I comfident that we'll jump it eventually.

Thanks for the feedback.

Pierre.

[Gt40Eco]

I was going to use the dashcommand for the main display in my project car, this is a major set back due to this problem.

When do you think you will have it working ? is that matter of week or ..... dream

[bengteck]

In fact i'm waiting since ver 1.0.6
but you gotto be patience
as good stuff need time .....


cheers

[Weston@PPE]

This is still on the to-do list.

[Gt40Eco]

Just a follow up, I re-load the Tablet with the win xp and now it work the way it suppose to do , beside the "no reconnecting"

I'm able to boot in 15 second, and then I have to manually open the DC, unless I turn it on Stand By who wake up in less than 5 second.

I bough a smaller digital instrument cluster as back up and ready to go system, when the re-connect feature will be out, I will be able to use my full gauge with the 8" screen .

'B,

[Weston@PPE]

If you're willing to wait for a reboot each time, it would be easy to make a batch file (that is set to run on startup) to start DashCommand, and have it connect and view the dashboards screen.

[drewbp]

A full reboot is what is trying to be avoided though.  The whole rest of my caputer is up and running returning from hibernate or standby, except for a reconnect from DC.

[Weston@PPE]

We're working on this, for now you'll just need to go back to the main menu and hit connect again.

[Dougw133]

Are we anywhere on this yet? Been awhile.

[AuZZZie]

I fail to see how this is taking years to implement sorry.

At very least, why can we not parse a command line switch to initiate the re-connect instead of clicking a GUI button.

That way we could have our other frontend application or even windows, sense the resume state then run the command. Ideally we would want DashCommand to sense the state change and issue the reconnect, but if you guys are really having such a technical hurdle with this my suggestion would be a perfectly workable easy to implement solution.

In the grand scheme of software pricing, DashCommand isn't exactly cheap. Auto-reconnect should really exist by now.

[WordMasterRice]

I fail to see how this is taking years to implement sorry.

At very least, why can we not parse a command line switch to initiate the re-connect instead of clicking a GUI button.

That way we could have our other frontend application or even windows, sense the resume state then run the command. Ideally we would want DashCommand to sense the state change and issue the reconnect, but if you guys are really having such a technical hurdle with this my suggestion would be a perfectly workable easy to implement solution.

In the grand scheme of software pricing, DashCommand isn't exactly cheap. Auto-reconnect should really exist by now.

Yea I'm with you, there really is no technical hurdle, if there is some better engineers need to be hired. If I got a hotkey combination to reconnect it I could write a script in 30 seconds to handle the job and trigger it automatically on resume.

The problem also is that the calculations are absolutely terrible and require the entire program to be relaunched most of the time anyway.  For example the range calculation, if you shut the car off and fill up, then start the car and computer and reconnect dash command it still says you have 20 miles range on the gas tank, it needs to be completely restarted for it to work properly(of course even then the range calculation is only useful for the moment you started the car because you can drive for half the tank and the range decreases by 20 miles).

What a waste of money really...

[Weston@PPE]

DashCommand is written to be cross-platform, we use the same stuff to run DashCommand on Windows, iPhone, and Android. Making an auto re-connect for Windows could break the other versions.

We do have a command line flag to connect automatically when DashCommand is launched, and we have another to go directly to the dashboards page. You can view all of the command line parameters here:
http://www.palmerperformance.com/products/dashcommand/windows/embedding.php

The range calculations are based on the SAE.FLI PID, which comes directly from your vehicle. It uses the FLI (fuel level) PID, your entered fuel tank capacity, and the calculated average MPG to estimate range. We also have a PID priority system, and range would be level 3 -- the lowest -- so it won't update right away (try going to a different tab and then back). A priority 3 PID will update 1 time for every 50 updates of a high priority PID like engine RPM.

If you're having troubles with things like the range calculations, please check your vehicle settings in the Vehicle Manager. An incorrect value WILL cause our calculations to give faulty information. If you don't know a value, its better to leave it blank and have DashCommand use the built-in defaults to avoid messing up any CALC PIDs.

[AuZZZie]

That really doesn't help if the application is already running. It would just launch a second instance that would attempt to auto-connect.

A /switch to initiate what the GUI button already does is ridiculously basic. Even cross, platform I fail too see a technical hurdle.

[Weston@PPE]

It would just launch a second instance that would attempt to auto-connect.

Exactly!

You can't pass a command line parameter to a application that is already running, only when you launch it. The flag we already have is exactly what you just asked for, a command line flag to connect to the vehicle. Whether it starts with a dash (-) or a slash (/), they are the same. You can only specify command line options/flags/switches/parameters (which are all exactly the same thing) when you first launch an application. It is basic, and we've had it in DashCommand for a very long time. Unless I'm misunderstanding the meaning of "command line switch" from your post 3 days ago, you won't be able to send a command line flag to a running application.

Detecting when Windows resumes from Stand by or Hibernate would need to be done in a platform specific way, and we're trying to keep it as platform independent as possible.