Hi Matt,
New feature noticed, not sure if its operation is intended to indicate something else but I've found it confusing.
ecu: PS13/RPS13-SR20
OS: W7 32 SP1
Nistune v0.17
problem: clicking on 'consult' to enable ecu connection,
consult disconnects but consult still appears to show its connected shown by the scanning back and forth under consult button.
press F6 to show gauges and all greyed out as consult is not connected.
workaround: press consult (F4) off, then back on.
when consult connection appears to be connected and is not can cause DAQ loss if not reconnected.
if possible, when consult disconnects or fails, a loud beep and the scanning visual aid under the consult button should stop to indicate a change in connectivity.
consult showing connected but not connected
Moderator: Matt
Re: consult showing connected but not connected
There is a problem with the time out routine which I am still to sort. When the scrolling is happening it is still running consult code in Nistune but is actually disconnected. As you found clicking the button again stops it. Needs to be fixed
Re: consult showing connected but not connected
I don't recall this in the earlier versions though. 0.12 etc.
Re: consult showing connected but not connected
It has existed from 0.12 onwards. There haven't been that many changes to the consult code otherwise looking from the release note updates