I’m very happy to see that custom rev limiters are supported via CAN now, but if possible, one change would be great.
It appears to be 8 discreet steps at the moment, rather than linearly interpolated. This makes sense, if only a rotary switch was being used, however making it a continuous adjustment would be excellent for cases where gearboxes need the ECU to target a specific speed (such as DCTs while the forks are being moved around during a skip downshift).
Otherwise, an implementation of gearbox engine speed target would be even better, with an accompanying blip table and basic parameters for the cut/speed limiting.
Thanks for the great work on v3, it’s really coming together and the improvements are very very welcome! 
There is an option to send the exact rev limiter target via user defined CAN:
CAN BUS target control - an input activating the rev limiter set via the CAN BUS. The rev limiter RPM value should be read from the CAN BUS using User-defined CAN and assigned to the CAN logging channel as Rev limiter target CAN BUS. If the next CAN frame defining the rev limiter RPM does not appear within 500ms, the value of CAN to Rev limiter target CAN BUS will be changed to 20,000 RPM.
In the DSG support there is a exact rev matching strategy. The gearbox sends the required RPM and the ECU try to keep them. I can imagine to allow using this strategy without DSG.
Thanks for the quick reply Jadzwin. When I read the documentation earlier I interpreted it as something to do only with rotary switches - glad to hear it’s definable specifically. 
Being able to use the DSG rev match strategy would likely be best. Since my use case isn’t particularly common, it may just be easier for both of us if I used the DSG CAN protocol for my application. Would you be able to provide the message structure for one of the DSG boxes which use the strategy? Perhaps the DQ250. Feel free to send me a PM if you’d prefer.