TrackerGuy19 i think this is a kind of common issue using CAN. I'd suggest you to follow some of our hints to get it resolved.
In your link, the first way is to set lower bound. In this case (according to picture) the bound cannot be determined because the drop is nevertheless there even when I set the lower bound very high. On the other hand, the lower bound cannot be higher than the minimal value and basically ... car tank min value is 0.1
The alternative solution worked where there was identical new virtual fuel level sensor made with calculation table which returns values 0 or 1.
Then the real sensor uses that information with not-null check validator.
At the moment, the graph is looking better, but there are also drops like real level -> 0(L) -> 7 -> 0 -> 54 -> real level and the graph show data as
real level -> 7L -> 54 -> real level and there is nothing to do about that.
Thank you for the link.