<![CDATA[SlotRacer Forum - Other Systems]]>

<![CDATA[SlotRacer Forum - Other Systems]]> https://slotracer.online/community/ Thu, 22 Oct 2026 20:52:18 +0000 MyBB <![CDATA[A 2026 purchase!]]> https://slotracer.online/community/showthread.php?tid=5393 Tue, 04 Aug 2026 21:01:45 +0100 https://slotracer.online/community/showthread.php?tid=5393

IMG_2113.jpeg Size: 2.17 MB Downloads: 77

]]>

IMG_2113.jpeg Size: 2.17 MB Downloads: 77

]]> <![CDATA[Experimenting with a 12 car SSD/O2 system]]> https://slotracer.online/community/showthread.php?tid=5006 Mon, 29 Sep 2025 13:02:10 +0100 https://slotracer.online/community/showthread.php?tid=5006
System-D uses a Mark/Space timing method for lap counting and signal inversion for commanding a lane change. This is a 36 car ID detection system i.e. far too many for most of us.

But does this approach offer anything for Hornby SSD users who want more than six cars on the grid but who don’t wish to splash out on a complete Slot.it oXigen system?

Here very kindly Slot.it have provided a nice cross-compatibility option. Slot.it oXigen decoders can be set up to strobe their IR LEDs on IDs 1-6.

Meanwhile I have a version of In-car Pro firmware for Hornby SSD decoders which can be driven on any of the six Hornby throttles but which strobes its ID on System-D proprietary IDs 7-12.

This provides a potential solution for up to 12 cars.

For this 12 car solution:

Cars 1-6 are controlled by oXigen wireless and they strobe on corresponding SSD IDs 1-6.

Cars 7-12 are controlled by SSD track packets (this of course is limited to six cars) and they strobe on System-D proprietary IDs 7-12.

To protect an investment into an existing Hornby SSD six car setup, while adding oXigen decoders and throttle controller pairs as required… the following is required:

1/ All six SSD decoders need to be upgraded to a special version of ICP firmware which strobes on IDs 7-12. This is called ‘Block B variant’.

2/ A System-D Sensor Hub is required together with high speed 4-phototransistors-in-row sensors.

3/ Race management is via PC LapCounter so a user licence is required.

4/ Since the track would be running up to 12 cars and retaining the Hornby powerbase, some form of high power mod would also be required.

5/ Hornby SSD lane changers with standard firmware remain compatible with all of above.

The above is quite a technical solution and clearly not for everyone … maybe very few … but it trades skilled upgrading for minimal additional cost outlay for users who already own a six car SSD system who need to race additional cars.

This is absolutely not an off the shelf plug-and-play solution - more a discussion of the art of the possible!!!!!

c]]>
System-D uses a Mark/Space timing method for lap counting and signal inversion for commanding a lane change. This is a 36 car ID detection system i.e. far too many for most of us.

But does this approach offer anything for Hornby SSD users who want more than six cars on the grid but who don’t wish to splash out on a complete Slot.it oXigen system?

Here very kindly Slot.it have provided a nice cross-compatibility option. Slot.it oXigen decoders can be set up to strobe their IR LEDs on IDs 1-6.

Meanwhile I have a version of In-car Pro firmware for Hornby SSD decoders which can be driven on any of the six Hornby throttles but which strobes its ID on System-D proprietary IDs 7-12.

This provides a potential solution for up to 12 cars.

For this 12 car solution:

Cars 1-6 are controlled by oXigen wireless and they strobe on corresponding SSD IDs 1-6.

Cars 7-12 are controlled by SSD track packets (this of course is limited to six cars) and they strobe on System-D proprietary IDs 7-12.

To protect an investment into an existing Hornby SSD six car setup, while adding oXigen decoders and throttle controller pairs as required… the following is required:

1/ All six SSD decoders need to be upgraded to a special version of ICP firmware which strobes on IDs 7-12. This is called ‘Block B variant’.

2/ A System-D Sensor Hub is required together with high speed 4-phototransistors-in-row sensors.

3/ Race management is via PC LapCounter so a user licence is required.

4/ Since the track would be running up to 12 cars and retaining the Hornby powerbase, some form of high power mod would also be required.

5/ Hornby SSD lane changers with standard firmware remain compatible with all of above.

The above is quite a technical solution and clearly not for everyone … maybe very few … but it trades skilled upgrading for minimal additional cost outlay for users who already own a six car SSD system who need to race additional cars.

This is absolutely not an off the shelf plug-and-play solution - more a discussion of the art of the possible!!!!!

c]]> <![CDATA[Experimenting with Sensored Brushless Motors]]> https://slotracer.online/community/showthread.php?tid=4645 Mon, 09 Dec 2024 11:57:17 +0000 https://slotracer.online/community/showthread.php?tid=4645
Drifter2 has more recently carried out some interesting trials with sensored brushless motors which look impressive and highly positive as a future race option. Link below:

https://slotracer.online/community/showt...p?tid=4217

As my high speed ‘drag strip’ instrumented test track is upgraded with a large digital speed read-out display - it’s become a useful test environment for my own experimentations with sensored brushless motors.

Having used brushless motors in model aircraft for many years - their use in digital slotcars is hardly fundamental research - it’s more about optimisation as a route to assessing ‘usefulness’ as compared with the brushed motors. The latter are of course the current norm across the slotcar hobby.

Like Drifter2, I believe ‘sensored’ motors are the best starting point for brushless slotcars in order to achieve smoother low speed running. These motors have internal Hall sensors to report rotation phase. Simpler non sensored brushless motors rely on back-EMF to measure rotation phase which works best at moderate and high speeds, but poorly at low speeds.

My experimentations will use digital control only as others are busy developing and in some cases selling brushless motors for analog systems.

My plan is three stage and likely to run through 2025.

Stage 1: use commercial sensored brushless motor and electronic speed controller (ESC) in conjunction with Spektrum DSMR r/c system. This approach will pick up DC power from rails and then step down to 7.5V using a buck converter.

Stage 2: Use commercial sensored brushless motor and ESC in conjunction with an SSD decoder which has a modified output to match the input ‘servo’ pulse requirement of the commercial ESC. In this case track power will be SSD digital and a combination of bridge rectifier plus buck converter will be used to generate 7.5V DC.

Stage 3: Here the commercial ESC will be replaced with a Texas Instruments IC to provide a small footprint in-car solution. The ICs of particular interest are the DRV10970 and the newer variant, the MCT8316Z.

In my previous experiments a few years back I used sensorless brushless motors and a simple controller which could be driven by a standard digital decoder motor PWM signal. It drove but had no brakes. At that time I used a slot.it motor pod and a PCR chassis.

This time around the mechanical platform uses the NSR Z4 chassis with side-winder, angle-winder and in-line motor pod configuration options.

I hope this new thread will be of interest both to hobbyists and system developers.

Current status: the brushless motors and ESCs have arrived and the Z4 chassis are patiently waiting for they drive system install.

Apologies this post is rather long but I did want to frame correctly the upcoming project effort. Future posts on this thread will be shorter and to the point!

Meanwhile, thanks for reading - and as always, all comments and thoughts are welcome.

c]]>
Drifter2 has more recently carried out some interesting trials with sensored brushless motors which look impressive and highly positive as a future race option. Link below:

https://slotracer.online/community/showt...p?tid=4217

As my high speed ‘drag strip’ instrumented test track is upgraded with a large digital speed read-out display - it’s become a useful test environment for my own experimentations with sensored brushless motors.

Having used brushless motors in model aircraft for many years - their use in digital slotcars is hardly fundamental research - it’s more about optimisation as a route to assessing ‘usefulness’ as compared with the brushed motors. The latter are of course the current norm across the slotcar hobby.

Like Drifter2, I believe ‘sensored’ motors are the best starting point for brushless slotcars in order to achieve smoother low speed running. These motors have internal Hall sensors to report rotation phase. Simpler non sensored brushless motors rely on back-EMF to measure rotation phase which works best at moderate and high speeds, but poorly at low speeds.

My experimentations will use digital control only as others are busy developing and in some cases selling brushless motors for analog systems.

My plan is three stage and likely to run through 2025.

Stage 1: use commercial sensored brushless motor and electronic speed controller (ESC) in conjunction with Spektrum DSMR r/c system. This approach will pick up DC power from rails and then step down to 7.5V using a buck converter.

Stage 2: Use commercial sensored brushless motor and ESC in conjunction with an SSD decoder which has a modified output to match the input ‘servo’ pulse requirement of the commercial ESC. In this case track power will be SSD digital and a combination of bridge rectifier plus buck converter will be used to generate 7.5V DC.

Stage 3: Here the commercial ESC will be replaced with a Texas Instruments IC to provide a small footprint in-car solution. The ICs of particular interest are the DRV10970 and the newer variant, the MCT8316Z.

In my previous experiments a few years back I used sensorless brushless motors and a simple controller which could be driven by a standard digital decoder motor PWM signal. It drove but had no brakes. At that time I used a slot.it motor pod and a PCR chassis.

This time around the mechanical platform uses the NSR Z4 chassis with side-winder, angle-winder and in-line motor pod configuration options.

I hope this new thread will be of interest both to hobbyists and system developers.

Current status: the brushless motors and ESCs have arrived and the Z4 chassis are patiently waiting for they drive system install.

Apologies this post is rather long but I did want to frame correctly the upcoming project effort. Future posts on this thread will be shorter and to the point!

Meanwhile, thanks for reading - and as always, all comments and thoughts are welcome.

c]]> <![CDATA[Speed trap digital read-outs]]> https://slotracer.online/community/showthread.php?tid=4570 Fri, 25 Oct 2024 23:13:28 +0100 https://slotracer.online/community/showthread.php?tid=4570
This time it’s a speed trap with large digital read-outs.

The plan is a two lane system which reports car ID and transit speed as the cars pass the speed trap position.

Having worked on 0.2 inch (5mm) digital displays for 1/32 scale windscreens, it’s time to go bigger for track-side displays :)

c

IMG_7821.jpeg Size: 477.45 KB Downloads: 115

ID detection, speed detection and large display readout to follow.]]>
This time it’s a speed trap with large digital read-outs.

The plan is a two lane system which reports car ID and transit speed as the cars pass the speed trap position.

Having worked on 0.2 inch (5mm) digital displays for 1/32 scale windscreens, it’s time to go bigger for track-side displays :)

c

IMG_7821.jpeg Size: 477.45 KB Downloads: 115

ID detection, speed detection and large display readout to follow.]]> <![CDATA[Windscreen digital read-outs]]> https://slotracer.online/community/showthread.php?tid=4561 Fri, 18 Oct 2024 10:55:21 +0100 https://slotracer.online/community/showthread.php?tid=4561
Inspired by the ideas of a user by the name of Flag Slot Racer, I decided to design a two digit 7 seven segment LED display for windscreen mounting on 1/32 scale slot cars such as GT3 and GT4. The design uses 0.2 inch displays i.e. the vertical height of the numbers is approx 5mm.

The design is based on the ATtiny3226 microcontroller and can be ID programmed in a number of ways including UART, UPDI or directly from the decoder’s main microcontroller using an industry standard SPI bus.

In the first variant I plan to read the IR LED signal directly from the SSD decoder. This signal includes car ID (and whether or not the lane change button is pressed).

This approach perfectly matches the six ID method used by Scalextric Sport Digital.

As some will know, I’ve extended the SSD ID method out to ID36, so these small displays will also perfectly match this extended approach.

The benefits of using the IR LED signal to control the display are that the interface between decoder and screen display is kept very simple, and also any change in decoder ID is immediately auto updated onto the display. (BTW the decimal point within the display can be used to signal a lane change request - i.e. a useful system diagnostic.)

Here is the prototype PCB showing the location of the ATtiny3226 and the LED biasing resistors. The LED display modules are to be attached on the other side of the PCB. The board measures 14.5mm x 12.5mm.

c

IMG_7756.jpeg Size: 147.09 KB Downloads: 120

]]>
Inspired by the ideas of a user by the name of Flag Slot Racer, I decided to design a two digit 7 seven segment LED display for windscreen mounting on 1/32 scale slot cars such as GT3 and GT4. The design uses 0.2 inch displays i.e. the vertical height of the numbers is approx 5mm.

The design is based on the ATtiny3226 microcontroller and can be ID programmed in a number of ways including UART, UPDI or directly from the decoder’s main microcontroller using an industry standard SPI bus.

In the first variant I plan to read the IR LED signal directly from the SSD decoder. This signal includes car ID (and whether or not the lane change button is pressed).

This approach perfectly matches the six ID method used by Scalextric Sport Digital.

As some will know, I’ve extended the SSD ID method out to ID36, so these small displays will also perfectly match this extended approach.

The benefits of using the IR LED signal to control the display are that the interface between decoder and screen display is kept very simple, and also any change in decoder ID is immediately auto updated onto the display. (BTW the decimal point within the display can be used to signal a lane change request - i.e. a useful system diagnostic.)

Here is the prototype PCB showing the location of the ATtiny3226 and the LED biasing resistors. The LED display modules are to be attached on the other side of the PCB. The board measures 14.5mm x 12.5mm.

c

IMG_7756.jpeg Size: 147.09 KB Downloads: 120

]]> <![CDATA[Wiring Smart LEDs onto Slot.it O201 decoders]]> https://slotracer.online/community/showthread.php?tid=4305 Sat, 20 Apr 2024 20:41:47 +0100 https://slotracer.online/community/showthread.php?tid=4305
https://slotracer.online/community/showt...2#pid35942

One application is to add additional IR car strobe IDs. For example IDs 7-10 to expand the SSD system. Another example is to provide an alternative method for oXigen lap counting based on an extension of the SSD six car method.

I with a group of amazing and supportive friends are exploring both of these options and others too ;)

In this post I will focus on how to wire a Smart LED onto each of the three recent/present versions of oXigen wireless decoder.

In each case the Smart LED requires connection to four points on the decoder:

RED: +3.3 Volts
YELLOW: LED+ (or LED Anode)
WHITE: LED- (or LED Cathode)
BLACK: Zero Volts

Equipped with a fine tipped soldering iron the correct wiring points are shown below for each of the recent/present oXigen decoders. As you will see, the external LED attachment points are used in each case plus two further connect points for power.

c

Smart_LED_201c1_OK 2.png Size: 642.89 KB Downloads: 160

Smart_LED_201b2_OK 2.png Size: 519.53 KB Downloads: 126

Smart_LED_201b1_OK 3.png Size: 261.73 KB Downloads: 126

]]>
https://slotracer.online/community/showt...2#pid35942

One application is to add additional IR car strobe IDs. For example IDs 7-10 to expand the SSD system. Another example is to provide an alternative method for oXigen lap counting based on an extension of the SSD six car method.

I with a group of amazing and supportive friends are exploring both of these options and others too ;)

In this post I will focus on how to wire a Smart LED onto each of the three recent/present versions of oXigen wireless decoder.

In each case the Smart LED requires connection to four points on the decoder:

RED: +3.3 Volts
YELLOW: LED+ (or LED Anode)
WHITE: LED- (or LED Cathode)
BLACK: Zero Volts

Equipped with a fine tipped soldering iron the correct wiring points are shown below for each of the recent/present oXigen decoders. As you will see, the external LED attachment points are used in each case plus two further connect points for power.

c

Smart_LED_201c1_OK 2.png Size: 642.89 KB Downloads: 160

Smart_LED_201b2_OK 2.png Size: 519.53 KB Downloads: 126

Smart_LED_201b1_OK 3.png Size: 261.73 KB Downloads: 126

]]> <![CDATA[Ninco lane changers]]> https://slotracer.online/community/showthread.php?tid=4248 Sat, 09 Mar 2024 18:21:05 +0000 https://slotracer.online/community/showthread.php?tid=4248
So I acquired some Ninco XLCs and some Ninco pit lanes.

As we know there are several lane changer mechanics in market:

1/ Scalextrix push-pull dual solenoid.
2/ Carrera single solenoid with blade actuated mechanical auto return.
3/ SCX which is purely mechanical.
4/ Ninco which is single solenoid and spring loaded return.

Then there are currently announced plans from Policar/Slot.it and ScaleAuto - both of course exciting.

So with Ninco lane changers in use by a number of enthusiast communities I thought I would take a closer look.

I plan to explore two questions:

1/ Could lane changer electronics use two solenoid current options - an initial high current to enable fast actuation - then a reduced current for solenoid ‘hold’ to maintain position against the spring tension?

2/ Could lane changer electronics use a second sensor (post-lane change mechanism) which then releases the solenoid? This would prevent early release for slower moving cars.

I plan to explore both of above.

Any thoughts from like-minded enthusiasts?

c]]>
So I acquired some Ninco XLCs and some Ninco pit lanes.

As we know there are several lane changer mechanics in market:

1/ Scalextrix push-pull dual solenoid.
2/ Carrera single solenoid with blade actuated mechanical auto return.
3/ SCX which is purely mechanical.
4/ Ninco which is single solenoid and spring loaded return.

Then there are currently announced plans from Policar/Slot.it and ScaleAuto - both of course exciting.

So with Ninco lane changers in use by a number of enthusiast communities I thought I would take a closer look.

I plan to explore two questions:

1/ Could lane changer electronics use two solenoid current options - an initial high current to enable fast actuation - then a reduced current for solenoid ‘hold’ to maintain position against the spring tension?

2/ Could lane changer electronics use a second sensor (post-lane change mechanism) which then releases the solenoid? This would prevent early release for slower moving cars.

I plan to explore both of above.

Any thoughts from like-minded enthusiasts?

c]]> <![CDATA[Brushless 1/32 Slot Car]]> https://slotracer.online/community/showthread.php?tid=4217 Tue, 20 Feb 2024 08:39:36 +0000 https://slotracer.online/community/showthread.php?tid=4217 I’ve done some more on my ESC project for a brushless 1/32 slot car.
The commercial ESC I have, now has an ATmega 328 microcontroller, it came with an ATmega 8 so I replaced it for a decent spec variant. Writing code for brushless commutation is very challenging and interesting.
I now have the ESC functioning fairly well on the bench, powering a Rockstar sensor-less 3500kv in-runner 2s (8.4v) motor. (From a mini z R/C car).
I’ve also just purchased an outrunner 3/4s 2750 Kv, so it will be interesting to see how that works. I found an old worn out chassis to "experiment" with.

BrushlessRocket.jpg Size: 126.42 KB Downloads: 286

happymotor.jpg Size: 106.04 KB Downloads: 267

]]> I’ve done some more on my ESC project for a brushless 1/32 slot car.
The commercial ESC I have, now has an ATmega 328 microcontroller, it came with an ATmega 8 so I replaced it for a decent spec variant. Writing code for brushless commutation is very challenging and interesting.
I now have the ESC functioning fairly well on the bench, powering a Rockstar sensor-less 3500kv in-runner 2s (8.4v) motor. (From a mini z R/C car).
I’ve also just purchased an outrunner 3/4s 2750 Kv, so it will be interesting to see how that works. I found an old worn out chassis to "experiment" with.

BrushlessRocket.jpg Size: 126.42 KB Downloads: 286

happymotor.jpg Size: 106.04 KB Downloads: 267

]]> <![CDATA[Lap counting and Control - for up to 12, 24 or 36 cars]]> https://slotracer.online/community/showthread.php?tid=4165 Mon, 22 Jan 2024 19:03:35 +0000 https://slotracer.online/community/showthread.php?tid=4165
I’m exploring potential control options and am interested to focus on options which are distinct from current in-market systems. That said, I am keen to retain compatibility with the major brands wherever possible.

One option is to better compress data to achieve twelve car control via track packets i.e. the SSD and D132/124 approach but extended from six to twelve cars. Big thanks to drifter2 for helping to explore this potential approach.

The second option is of course to go wireless and here I am looking into 2.4GHz broadcast methods where a single broadcast message commands up to twelve cars.

The thinking here is that twelve cars is more than enough for at least 99.9% of the world’s 1/32 slot car tracks. But for racers who desire up to 24 or 36 cars in their races then either two or three broadcast modules could be operated side-by-side with one as the primary device. The broadcast method offers the opportunity for higher power levels and hence better suppression of in-channel noise.

So that’s the plan for 2024… to build both approaches then test and compare their performance.

c]]>
I’m exploring potential control options and am interested to focus on options which are distinct from current in-market systems. That said, I am keen to retain compatibility with the major brands wherever possible.

One option is to better compress data to achieve twelve car control via track packets i.e. the SSD and D132/124 approach but extended from six to twelve cars. Big thanks to drifter2 for helping to explore this potential approach.

The second option is of course to go wireless and here I am looking into 2.4GHz broadcast methods where a single broadcast message commands up to twelve cars.

The thinking here is that twelve cars is more than enough for at least 99.9% of the world’s 1/32 slot car tracks. But for racers who desire up to 24 or 36 cars in their races then either two or three broadcast modules could be operated side-by-side with one as the primary device. The broadcast method offers the opportunity for higher power levels and hence better suppression of in-channel noise.

So that’s the plan for 2024… to build both approaches then test and compare their performance.

c]]> <![CDATA[Experimenting with Smart IR LEDs]]> https://slotracer.online/community/showthread.php?tid=4069 Mon, 11 Dec 2023 10:29:46 +0000 https://slotracer.online/community/showthread.php?tid=4069
The result is a small circuit board which measures 9mm x 10.5mm and which connects directly onto a standard 3mm LED and which is controlled via a 4 wire input. The device is known as a Smart IR LED.

9EE9BD19-BE7C-44A3-A4E7-A30AD09790D7.jpeg Size: 147.58 KB Downloads: 162

The inputs come straight from the car’s digital decoder and consist of the following four signals:

+3.3V
Decoder +LED signal
Decoder -LED signal
0V

To use this new system component, instead of wiring an external IR LED to the decoder in the usual way, in this case the two LED signal wires are connected to the Smart IR LED together with two additional connections for power i.e. +3.3V and 0V. Power is taken direct from the decoder.

The Smart IR LED can take as input the standard lane change signals from various digital decoder manufacturers (e.g. Slot.it/oXigen, SCX-A or Scorpius) and it converts these signals to a mark-space-ratio strobe (with Lane change signal inversion) that follows the Scalextric protocol and therefore which functions with SSD lane changers.

Key points:

1/ The Smart IR LED can be programmed to any ID in the range 1-36. This means up to 36 cars can race together.

2/ The Lane Change function can be activated either by an incoming SSD signal with any mark-space-ratio (therefore oXigen and Scorpius decoders could be used) or with a simple high/low input signal as available from SCX-A decoders.

3/ This approach is compatible with standard SSD lane changers for IDs 1-14. It is further compatible with all IDs 1-36 when used with the ATtiny processor upgrade for SSD lane changers which I have shown elsewhere on this Forum.

4/ This approach, hopefully, will enable oXigen, SCX-A and Scorpius wireless systems to run alongside each other. And, as above, each will trigger SSD lane changers (either standard versions for 14 cars or ATtiny upgraded versions for up to 36 cars).

5/ The approach avoids any requirement to reverse engineer the products from Slot.it/oXigen, SCX or Scorpius - this is simply a ‘piggy-back’ approach.

6/ The Smart IR LED is used for car identification and lane change signalling. It is not a solution for vehicle control - this relies of track packets and/or 2.4GHz packets.

7/ I should add, this is an experimental approach and not a commercial product at this stage.

The experimentation and fun continue…

c]]> <![CDATA[Digital and multi-system compatibility]]> https://slotracer.online/community/showthread.php?tid=4036 Sun, 26 Nov 2023 15:53:55 +0000 https://slotracer.online/community/showthread.php?tid=4036
The question is can we replicate this mix in the 1/32 world of digital slot car racing?

In the past the answer has been NO because we were locked into one company’s digital system be-it SSD, D132, SCX-A or O2 or Scorpius.

However, as O2 and Scorpius bring increasing levels of compatibility with SSD/D132 this is changing. While I believe their main motivation is backwards compatibility with mass market products, a new opportunity is also emerging…

If we can identify a ‘transponder technology’ equivalent to what Rolex are doing for F1, then we can have brands such as SSD, SCX, O2 and Scorpius racing side-by-side.

In this case the winners are likely to be those with the best combination of excellent driver skills, excellent digital tech and a certain amount of good fortune. Sound familiar?

So is this possible?

Over the past six months I, with my collaborators, have been developing and testing the necessary transponders and lap sensors to achieve this aim and it’s all looking very promising.

Already, cars with SSD decoders can race against cars with SCX-A decoders and also against cars with O2 decoders. Adding Scorpius into the mix should be straight forward.

The necessary lap sensing and pit lane sensing is already undergoing field trials.

So to summarise, the necessary transponders, track sensors and suitable rms are all at an advanced stage of development.

So 2024 should be a lot of fun!

c]]>
The question is can we replicate this mix in the 1/32 world of digital slot car racing?

In the past the answer has been NO because we were locked into one company’s digital system be-it SSD, D132, SCX-A or O2 or Scorpius.

However, as O2 and Scorpius bring increasing levels of compatibility with SSD/D132 this is changing. While I believe their main motivation is backwards compatibility with mass market products, a new opportunity is also emerging…

If we can identify a ‘transponder technology’ equivalent to what Rolex are doing for F1, then we can have brands such as SSD, SCX, O2 and Scorpius racing side-by-side.

In this case the winners are likely to be those with the best combination of excellent driver skills, excellent digital tech and a certain amount of good fortune. Sound familiar?

So is this possible?

Over the past six months I, with my collaborators, have been developing and testing the necessary transponders and lap sensors to achieve this aim and it’s all looking very promising.

Already, cars with SSD decoders can race against cars with SCX-A decoders and also against cars with O2 decoders. Adding Scorpius into the mix should be straight forward.

The necessary lap sensing and pit lane sensing is already undergoing field trials.

So to summarise, the necessary transponders, track sensors and suitable rms are all at an advanced stage of development.

So 2024 should be a lot of fun!

c]]> <![CDATA[Designing decoder hardware and firmware]]> https://slotracer.online/community/showthread.php?tid=4028 Wed, 22 Nov 2023 18:44:51 +0000 https://slotracer.online/community/showthread.php?tid=4028
The Rover SD1s have the DPR track packet variant.

Sorry the photos are rotated - room for editorial improvement!

c

EB28044F-2D66-4C7D-B2EF-8F99AF260B1C.jpeg Size: 240.06 KB Downloads: 133

A7F51A22-36B9-4825-8818-078C82F433C5.jpeg Size: 282.24 KB Downloads: 135

0EC1CF3C-D28C-4A20-8E9D-761A18EE4DD1.jpeg Size: 275.65 KB Downloads: 160

69FBC855-F812-42E8-A639-546075349C27.jpeg Size: 2.27 MB Downloads: 98

0F0223DB-526F-454F-8920-D99FA897A467.jpeg Size: 2.85 MB Downloads: 110

3DE21DCF-54F9-46D1-9C99-00588DC386F1.jpeg Size: 230.18 KB Downloads: 111

]]>
The Rover SD1s have the DPR track packet variant.

Sorry the photos are rotated - room for editorial improvement!

c

EB28044F-2D66-4C7D-B2EF-8F99AF260B1C.jpeg Size: 240.06 KB Downloads: 133

A7F51A22-36B9-4825-8818-078C82F433C5.jpeg Size: 282.24 KB Downloads: 135

0EC1CF3C-D28C-4A20-8E9D-761A18EE4DD1.jpeg Size: 275.65 KB Downloads: 160

69FBC855-F812-42E8-A639-546075349C27.jpeg Size: 2.27 MB Downloads: 98

0F0223DB-526F-454F-8920-D99FA897A467.jpeg Size: 2.85 MB Downloads: 110

3DE21DCF-54F9-46D1-9C99-00588DC386F1.jpeg Size: 230.18 KB Downloads: 111

]]> <![CDATA[Experimenting with 2-part decoders]]> https://slotracer.online/community/showthread.php?tid=3959 Fri, 20 Oct 2023 12:37:23 +0100 https://slotracer.online/community/showthread.php?tid=3959
My main motivation for this project is to fit a high spec decoder into a slim F1 chassis. The decoder in the photo is equipped with 18A motor/brake MOSFETs. Perfect for 50k evo king motors on a heavily mag’ed drag strip setup :)

c

4BC986DA-FADF-4947-A67F-8F0737E67648.jpeg Size: 2.1 MB Downloads: 131

]]>
My main motivation for this project is to fit a high spec decoder into a slim F1 chassis. The decoder in the photo is equipped with 18A motor/brake MOSFETs. Perfect for 50k evo king motors on a heavily mag’ed drag strip setup :)

c

4BC986DA-FADF-4947-A67F-8F0737E67648.jpeg Size: 2.1 MB Downloads: 131

]]> <![CDATA[ninco digital chip]]> https://slotracer.online/community/showthread.php?tid=1775 Mon, 14 Dec 2020 16:04:03 +0000 https://slotracer.online/community/showthread.php?tid=1775 zie dat er handige mensen zijn.

iemand heeft ook een universele chip gemaakt.
die ook op ninco digital kan worden gebruikt.]]> zie dat er handige mensen zijn.

iemand heeft ook een universele chip gemaakt.
die ook op ninco digital kan worden gebruikt.]]> <![CDATA[scx advance]]> https://slotracer.online/community/showthread.php?tid=1645 Tue, 20 Oct 2020 10:24:26 +0100 https://slotracer.online/community/showthread.php?tid=1645 <![CDATA[SCX/Scalextric Advance]]> https://slotracer.online/community/showthread.php?tid=1627 Thu, 15 Oct 2020 13:12:11 +0100 https://slotracer.online/community/showthread.php?tid=1627
Leo

SCX Advance and Compact sets.png Size: 2.9 MB Downloads: 294

]]>
Leo

SCX Advance and Compact sets.png Size: 2.9 MB Downloads: 294

]]>