In my code I try to map the value of delta (which is time interval based on millis() ), usually in the range of 400-800 ms, to a byte (400 = 0, 800 = 255, values outside the range are clipped to the border values). I have this code:
axis is int, delta is unsigned long. When I output the values, delta behaves exactly as it should. axis, however, takes rather strange values, even negative ones, although those should be ruled out completely.
I suppose this is a case of mismatched types. I guess that when I get the axis value right, it would still be sent incorrectly to Wire (as it should be a byte)?
I could hack it somehow, I suppose, but I would prefer to understand the underlying principles and see a more elegant solution...
When I output the values, delta behaves exactly as it should. axis, however, takes rather strange values, even negative ones, although those should be ruled out completely.
This depends on how you output the value.
In my code I try to map the value of delta (which is time interval based on millis() ), usually in the range of 400-800 ms, to a byte (400 = 0, 800 = 255, values outside the range are clipped to the border values). I have this code:
There are map() and constrain() functions to do this. Why not use them?
Finally, just because the value in axis could fit in a byte, Wire.send() will not send it as a byte, because it isn't a byte. If you need Wire.send() to send a single byte, you need to store the value to be sent in a byte variable, and pass that variable to the Wire.send() function.
PaulS:
Shouldn't the to range be 0 to 255? Otherwise, yes.
Oh, sorry, this is for non-programmatic reasons - in short, I want to use a training bike to emulate pedals attached to a computer driving wheel. In some games it is useful to have it "idling" a bit, but of course in some cases it will be zero.
