[Dr_C2]

Time to start the design of the anticollision algorithms.

The first version of anti-collision firmware will have the following core parameters:

L1=distance from sensor1 to sensor2

L2=distance from sensor2 to the mid-point of the lane changer zone.

Delta_L = distance from the start of the lane change mechanism to the above mid-point plus any ‘safety’ margin)

V_max = the maximum speed of travel of a vehicle for which lane changing is permitted. This is to avoid overspeed de-slots.

T_hold = actuation/hold time for solenoids

That’s five parameters.

Assuming cars don’t change speed the rest is simple maths … I hope :)

In addition to accurate measurement of speed, the pre-decision sensors (i.e. sensor1) may also provide an early signal to straighten the flipper so long as there are no cars already registered as traversing the lane changer zone. This will help avoid the risk of deslots as per the scenario described of the previous post.

So the above provide the basis for next steps in implementing version 1 of my collision avoidance endeavour.

This experimentation builds on new and fully functioning lane changer firmware which accurately reads ID and LC button status requiring only 2 ID pulse matches to do so. A standard Scalextric lane changer appears to need a minimum of 4 matching pulses. So the new firmware already has performance advantages (e.g. readability at higher vehicle speeds).

c