Hi Stefan,

See this short video. Before the video started I selected E01 G050 and did Save Settings, then exited to BC.

- Opened FIS Control menu by long-press of Up key
- Selected Measurement: got E01 G050
- Did Settings/Save Settings again (just to show it happened)
- Back to Measurement and selected G051 to see if I got the current group or the saved group
- Changed Control Unit to AWD (22), opened Measurement: got group 001. I was expecting either 050 or 051.
- Selected E22 G051
- Changed control unit to Engine (01), opened Measurement: got group 001. Again I was expecting 050 or 051.

Does this help? Maybe I still don't quite understand.

Nick

Ah! I had misunderstood what you meant by "stored group". I thought this was saving a default group for each different ECU in the new software. I think I get it now, thank you for explaining.

Test 3: Yes, I think it would be better if you always used a consistent "last group" when moving from a Collection to a Measurement. This would take away the random element.

Maybe if you always used the first item in the collection? Then I could order the collections differently to always go directly and quickly to a chosen group, to see the other values in that group which weren't part of the collection.

I have attached my config so you get an idea of how I use it smile

Hi Stefan!

Sorry for missing this post, I didn't have notifications turned on...

Thank you for adding this feature. It has solved half of my problem!
I have upgraded to fw 2020-11-22 and tried Settings->Save Settings with my "favourite" groups for each control unit. Now, like you say, if I am in Measurement and then go to Settings->Control Unit, change to a different unit and then select Measurement again, it jumps to the stored Group. This is much more useful! smile The ABS controller doesn't crash any more when the FIS Control tries to connect to it.

However this still does not quite work in my normal use case.
Example: I have Group 002 stored as the "favourite" for my AWD controller on Control Unit 22.
For this Control Unit the mask shows groups 001, 002, 050, 051, 052 [etc].
Most of my Presets are Collections, but I have some single values and Measurements too.
Say I am looking at a Preset which shows a Measurement, E01 Group 031 (fuel-air ratios).
Test 1) If I now enter the menu and select Measurement, I see E01 G 031 - fine, normal, useful. I think this is the most useful behaviour if the Preset is a Measurement.

Test 2) If I instead enter the menu and select Settings->Control Unit->AWD (22), then go back out of Settings and select Measurement, I do not see my stored group G002, but instead the closest available (unmasked) group to G031 which happens to be G050. I think it would be better if this showed the group I stored...

Test 3) Looking at a Preset which is a Collection (six different values all from E01), if I press Reset to get the menu and then choose Measurement, I get a random Group from the six which were used in the collection. I think if you go from a Collection straight to a Measurement it should first show the stored Group, not a random choice from the Collection.

Does that make sense? I can attach my configuration if I didn't explain well. Oder vielleicht könnte ich versuchen, es auf Deutsch erklaren smile

Thank you!

Nick

Thank you! Sorry if I didn't explain very well.

Hi Stefan,

If I've manually changed control unit and then go to Measurements then I always want to go to 01... it's already a lot of button presses.

In a Preset (for me almost always a collection)
Press Set to get main menu
Go to Settings
Go to Control Unit
Select control unit
Back to Settings
Back to Main Menu
Go to Measurement
- displays "Connecting..."
Get some random group number because you don't know which group was last read in the collection

I never want to go from (for example) group 02 in one control unit to group 02 in a different control unit because there are none in my car that are compared like this. Maybe you do this more often in vehicles with CAN connected to the FIS-Control? For me, as each preset can only show values from one control unit I have almost all of them from the ECU to avoid many different connect/disconnect cycles when scrolling through them.

I don't think I understand your example. I agree when switching from preset to measurement that it's useful to go back in the same group, but if I change control unit and then go straight into Measurement I always always want to look from the start of that control unit. If I went in Presets it would change control unit again..?

Yes, I could make a preset of E22/G001 but that only makes it shorter to change control unit. By definition any time I change control unit by hand, it's because I want to check a group I don't check often enough to have as a preset! smile

Another good reason - my ABS controller seems to have a bug where it stops communicating if you ask it for a group outside the range 01-07. I didn't manage to make it work until today so I hadn't set the masks for that unit! This might explain some odd "cannot communicate" bugs as you don't display which group you requested until after communication is established...

Maybe this could be a tweak so users can choose?

Nick

Hi Stefan,

It often happens that I want to look at a different control unit while driving. But the last-read group from the previous control unit is used as a start point, which is not predictable.

If I am in Presets and have ECU 01 Group 15 shown, when I select Measurement then FIS-Control will first show me Group 15. This is helpful! When a Collection preset is viewed, on selecting Measurement the group first shown will be one of the ones from the collection (depends which was read last, I guess). Less helpful but still ok.

But, say I then set the Control Unit to AWD (22). When I select Measurement, FIS-Control gives me Group 50 in control unit 22. This is because my AWD unit only has values in groups 01, 02, 50-59, 61-62, 70... and my configuration file has all others masked.

If I switch back to ECU 01, then I get ECU 01 Group 50...to get back to Group 15 I have to press the down button a lot!

I think that after changing ECU, the next group shown in Measurement should start from G01.

Car is a Mk4 Golf if that is relevant smile

Thanks,

Nick

Great idea! Thanks, I'll try that smile

Hi Stefan,

Would it be possible to add the ability to change module softcoding within the FIS-Control menu system?

It would be really nice to be able to enable and disable ESP for track use, without having to have my laptop in the car as well!

Alternatively a suggestion for a good app that supports the FIS-Control bluetooth<->OBD functions on Android and allows soft-coding changes would be very welcome smile

Thanks!

Nick

9

(17 replies, posted in English forum)

OK, no problem. I'll let you know if I work it out smile

10

(17 replies, posted in English forum)

I should have clarified - I never saw any data from the ABS module. The display shows "Connecting..." while the ABS light flashes on the instrument cluster and then after a couple of seconds goes blank and shows a down arrow. After pressing the Down button on the stalk it shows the baudrate, protocol and number of attempts briefly (before giving the "...failed" message). Using the Measurement menu item this doesn't happen, it just shows a group selection with stationary dot and no data.

11

(17 replies, posted in English forum)

Whoops, that was a typo. It should have read KWP2027.

When I use VCDS it connects fine but says it's using KWP2000 instead of KWP1821, is there any way to force which protocol is used for which control unit? If I can't make it work I may have to just add in the CAN wiring to my harness, I think you said before that it now works with the Golf 4..?

12

(17 replies, posted in English forum)

You're a genius. This works perfectly, thanks! smile

I only have one issue left - although almost everything works I have never been able to use the FIS-Control to connect to the ABS controller. When I select 03 as the control unit and then try to enter measurement the ABS light flashes in the cluster and the display then shows "Communication with control module failed". If I use ECU Info it says it's using KWP3027 at baudrate 10417, does this seem right?

I already tried increasing the interbyte delay and block delay in Tweaks but this hasn't helped. Fast Init is turned off. Is there anything else you can suggest?

Thanks,

Nick

13

(17 replies, posted in English forum)

Hi Stefan,

I have another question. Is it possible to do calculations on measured values before display? I realise you already do this for the unit conversions but this is hidden from the user...

The reason I ask is because my engine ECU outputs air-to-fuel ration (AFR) as a lambda value (eg 1.088). This equates to a lean burn of 16:1 air:fuel; 1.088 is multiplied by 14.7 because this is the stoichiometric ratio for gasoline. I can't easily multiply by 14.7 in my head - but FIS-Control could!

If this isn't currently possible I don't know the easiest way to add it in - maybe you could add a 'multiplier' field for each item in a collection and do this calculation before display? This would limit you to only displaying AFR as part of a collection but this is probably the most useful anyway as you may want to look at the raw lambda values in the measurement or OBD views. Your thoughts?

Thanks,

Nick

14

(17 replies, posted in English forum)

That was quick - thanks a lot! smile

15

(17 replies, posted in English forum)

Thanks Stefan, you're the man! I didn't realise the label checkbox was there. When I ticked them and set everything to upper case it worked perfectly smile

Now to finish tweaking everything...

Nick

16

(17 replies, posted in English forum)

To clarify the above - my collection labels are working but the individual measurements are not labelled. See the attached pic.

I did notice that some of the settings were not being updated when I uploaded a new settings file (example: bootlogo delay was set to 300ms in the car, then I uploaded a settings file with a 250ms delay and the preset labels changed but the bootlogo delay stayed at 300ms. I don't know if that helps!)

17

(17 replies, posted in English forum)

Hi Stefan,

Installed my FIS-Control in my Mk4 Golf today and I'm very impressed so far. I have a couple of questions about how things work though, since I've not quite managed to get it to behave as I want...

I've managed to update to the newest software, set up the basic settings and get my bootlogo collection loaded through the Android app. (kudos to you for this, it works really well!)

Observations:
1) In the Settings/Collections menu, the Group is prefilled to 255 on all entries. However going 'up' from 255 doesn't wrap around to 001 like it does with the measurement view. Is this a bug?

2) Manual section about Units: "The control units are normally using the metric unit system for their readings.
But you can also choose imperial or US unit system. The FIS-Control will convert the readings accordingly.
So liters will be gallons, kilometers will be miles and Bar will be PSI."
Please could you add a 'UK' option? We use miles and PSI but litres...

3) Strange things happen if I use lowercase text in the Preset labels (missing letters, wrong letters...) - although this works fine if I use capitals. Maybe another bug?

4) As I use OSX I am having trouble getting the 'send settings' option to work. I need to be connected through Bluetooth before I can set up the xmodem receive file options, but the FIS-Control doesn't activate the Bluetooth unit until after you hit Send Settings, and then it's too late..! I am however able to use the configurator and upload the settings file using the Android app. It would be really awesome if the Android app could receive as well as transmit...another feature request? wink

5) I have set up two collections which work as I expect, but I cannot get the measurement labels to work. In fact they don't work in presets set to Measurement either. Basically I want to achieve the same effect that you previously posted in this picture:
http://fis-control.de/images/2016-08-20_-_MAH04098snapshot.png

Could you please have a look at the attached settings file and see what might be the problem?

Thanks in advance,

Nick

A software patch for the instrument cluster to allow staging aka needle sweep is available. See here: http://www.users.on.net/~graeme86/sweep … ep501.html

This performs very well and is compatible with FIS-Control's bootlogo option :-)