VW: check cruise control

[sshane]

Each is only applicable in one of the two pcmCruise states, so only set when needed to be explicit.

[sshane]

@jyoung8607 how does this look assuming we find the best signal for this?

BTW I have a slight preference for this one as we: 1) already check the message, 2) others are not higher rate, 3) we already understand this signal partially. The other possible signal is unlabeled and has no counter or checksum.

[sshane]

Haven't seen any speed limiter usage in our local rlogs last 360 days. Interestingly, cruise control mode also hasn't been seen until Discord user black_guru tested it for us. @jyoung8607 I assume if the car doesn't have ACC we throw a CAN error as there's no radar?

If that's the case, we can have a follow PR to handle the missing messages and instead set nonAdaptive (since the FW itself isn't enough to stop a non-ACC car from fingerprinting) 🙂

saving graph: /home/batman/status/1000_vw_check_nonadaptive.a2e5bff9-f606-4e49-9a17-d7bec8a91820.pickle
======== summary ========
success: 63976
skipped: 0
failed: 456
pending: 0
==== error messages =====
CarState (456/64432) 0.7%
  DataBadError: Car CAN data invalid (337)
  DataBadError: Couldn't determine online CarParams (47)
  TypeError: argument of type 'NoneType' is not iterable (67)
  Exception: Non-adaptive cruise control mode not supported (5)
====== error types ======
CarState (456/64432) 0.7%
  DataBadError:  (384)
  TypeError:  (67)
  Exception:  (5)
=========================

['CarState/9d09cc205c254c4b|00000000--8e49d0191f/31',
 'CarState/9d09cc205c254c4b|00000000--8e49d0191f/1',
 'CarState/9d09cc205c254c4b|00000000--8e49d0191f/27',
 'CarState/9d09cc205c254c4b|00000000--8e49d0191f/13',
 'CarState/9d09cc205c254c4b|00000000--8e49d0191f/21']

[sshane]

process replay diff is expected, the default value for unseen messages is always 0