cool - please do so!

Das war genau der Hinweis den ich suchte. Läuft alles, Danke!

Looks very similar. But a huge price difference. What is the technical difference?

Finally, I've got it working using the map-block from Easy I/O in UIFlow (by chance I found it!), which is just

def slider_Motor_callback(slider_value):
motion.set_motor_speed(2, map_value(slider_value, 0, 100, -127, 127))

without any translation. Works fine with Remote+

Thank you. Don't understand what you suggest, but finally I got it working like this:

Maybe you have better idea!

Putty, the walking robot can go forward or backwards. When walking, I cannot stop or switch direction using a remote switch, because I cannot interrupt the flow. An interrupt routine is needed I guess. I found examples for a H/W pin interrupt, but not for S/W. Can anyone please help me?

@robalstona

with this definition the motors shows absolutely no movement.

I also tried this - but with no success. Seems that mapping or translating might not work in combination with REMOTE. Thanks for your help!

Thank you. I tried this:

...
def slider_Motor_callback(slider_value):
global inMin, inMax, outMin, outMax, tof_0
motion = Motion()
inMin = 0
inMax = 100
outMin = -127
outMax = 127
def translate(slider_value, inMin, inMax, outMin, outMax):
return (slider_value - inMin) * (outMax - outMin) / (inMax - inMin) + outMin
motion.set_motor_speed(1, slider_value)
...

But this doesn't work. What might be wrong?

you are probably right. But I cannot see any similarity with the maps-function of other IDE's. Great would be a mathematical function like this from MakeCode:
"map 'speed' from low '0' high '100' to low '-127' high '127'" (or vice versa)
Using arrays is very compicated, too much for me.

I like the REMOTE+ - feature. Works fine, but... The slider range starts at 0 and ends with 100. Most motors are controlled in the range of -127 to +127. Has anyone an idea of how to manage this?

I can measure +- 4,2V when connected to USB