suggestion - auto add control PIDs to read

[evlo]

I always fall into trap that i add pids I want to control into control and then wonder how to control it before i figure out to add them to read and then it works. Would it be possible to automatically add pids selected to control into read or some nicer solution if i just want to control for diagnosis?

[oldtinfords]

I always fall into trap that i add pids I want to control into control and then wonder how to control it before i figure out to add them to read and then it works. Would it be possible to automatically add pids selected to control into read or some nicer solution if i just want to control for diagnosis?

FORScan support don't monitor the forums for suggestions.
Selecting & adding PIDS has been kept simple & works well.

You can currently select a PID & view extra details without it automatically being added to the "Selected PIDs" list. What you are suggesting would mean every PID someone selected, to look at additional details would be added to the "Selected PIDs" list. You would then be complaining because the logger was laggy because you forgot to remove PIDs you didn't want in the "selected PIDs" list

[HappyPenguin]

I always fall into trap that i add pids I want to control into control and then wonder how to control it before i figure out to add them to read and then it works. Would it be possible to automatically add pids selected to control into read or some nicer solution if i just want to control for diagnosis?

You can currently select a PID & view extra details without it automatically being added to the "Selected PIDs" list. What you are suggesting would mean every PID someone selected, to look at additional details would be added to the "Selected PIDs" list.

You apparently misunderstood the OP's worthy suggestion. IIUC, it's got nothing to do with "extra details" (as you say). The OP is talking about PIDs using a "Type:" of "Control" as opposed to "Read".

FORScan will not allow any PID-based vehicle control without at least 1 PID being in the "Read" set.

@evlo: Although it's unintuitive and less-than-ideal, you can add just 1 PID to the "Read" set and it doesn't even have to be one of the PIDs that are in your "Control" set. Having just 1 "Read" PID will allow you to activate the "play" icon, thereby making all the "Control" PIDs "active".

So, unsurprisingly, I think your suggestion is very sensible, given that most folks will want to monitor ("Read") all of the same PIDs that are being controlled.

[evlo]

I would now even consider it a bug if it works with ANY PID added as read.

[HappyPenguin]

I would now even consider it a bug if it works with ANY PID added as read.

I would not agree with that. It's up to the user what PIDs they want to monitor ("Read"). It would definitely be helpful for FORScan to auto-populate the list based on "Control" PID additions, but the user might have reasons to do what they've configured.

I suspect that the weird, unintuitive FORScan interface (where you have to "Read" a PID before you can "Control" any PIDs) is simply because the "Read" PIDs' processing is internally "driving the loop". This would make more sense if you ever get into the depths of how "Control" PIDs really work, but it's hard to concisely explain.