<![CDATA[SlotRacer Forum

<![CDATA[SlotRacer Forum - Carrera]]> https://slotracer.online/community/ Thu, 30 Apr 2026 13:07:31 +0000 MyBB <![CDATA[Nitrous. Powered by Scorpius]]> https://slotracer.online/community/showthread.php?tid=5156 Mon, 05 Jan 2026 13:39:07 +0000 https://slotracer.online/community/showthread.php?tid=5156

IMG_9876.jpeg Size: 235.66 KB Downloads: 27

]]>

IMG_9876.jpeg Size: 235.66 KB Downloads: 27

]]> <![CDATA[Nitrous track telemetry]]> https://slotracer.online/community/showthread.php?tid=5152 Sat, 03 Jan 2026 11:07:39 +0000 https://slotracer.online/community/showthread.php?tid=5152 One way is to add track telemetry.
Before I go any future I need to clarify we are starting with a Carrera native system. We are not using Nitrous dongles or Scorpius controllers, nor MPD car decoders.
Just standard system.
Seeing we already have in the pipeline to make a Carrera Lane Brain we can simply use it as the basis of a track telemetry system as opposed to a car telemetry system.

Seeing the cars are RF let’s leave car telemetry alone for a minute and go to track telemetry.
It would be nice to have pit bay location on top of pit lane location. We may as well throw in a couple of sector units which involves putting one on the start line.

How’s it work?
Each locator decoder is allocated a unique ID. It’s also given a description as follows:
Pit lane entry
Pit lane exit
Pit bay 1
Pit bay 2
Pit bay 3
Pit bay 4
Pit bay 5
Pit bay 6
Start line (Sector 1 start)
Sector 2
Sector 3

So around 11. That’s lucky and I’ll tell you why.
Because I’m not using RF for lane changer functionality I can swap to BLE which is what the Carrera CH and the SmartRace app operate with.
A bit of research shows Android and iOS both can accept BLE data from multiple sources simultaneously. Android can reliably do around 9 devices properly and iOS 15-20. Over that it gets flakey.
Don’t forget we need to factor in the CU sending data via its plug in Bluetooth dongle
as well.
We won’t know the limits until the telemetry is written and evaluated.

So another potential product I’ll nickname for now Nitrous Locator Pro.

Thanks for reading.]]> One way is to add track telemetry.
Before I go any future I need to clarify we are starting with a Carrera native system. We are not using Nitrous dongles or Scorpius controllers, nor MPD car decoders.
Just standard system.
Seeing we already have in the pipeline to make a Carrera Lane Brain we can simply use it as the basis of a track telemetry system as opposed to a car telemetry system.

Seeing the cars are RF let’s leave car telemetry alone for a minute and go to track telemetry.
It would be nice to have pit bay location on top of pit lane location. We may as well throw in a couple of sector units which involves putting one on the start line.

How’s it work?
Each locator decoder is allocated a unique ID. It’s also given a description as follows:
Pit lane entry
Pit lane exit
Pit bay 1
Pit bay 2
Pit bay 3
Pit bay 4
Pit bay 5
Pit bay 6
Start line (Sector 1 start)
Sector 2
Sector 3

So around 11. That’s lucky and I’ll tell you why.
Because I’m not using RF for lane changer functionality I can swap to BLE which is what the Carrera CH and the SmartRace app operate with.
A bit of research shows Android and iOS both can accept BLE data from multiple sources simultaneously. Android can reliably do around 9 devices properly and iOS 15-20. Over that it gets flakey.
Don’t forget we need to factor in the CU sending data via its plug in Bluetooth dongle
as well.
We won’t know the limits until the telemetry is written and evaluated.

So another potential product I’ll nickname for now Nitrous Locator Pro.

Thanks for reading.]]> <![CDATA[Scorpius MPD F1 for Carrera]]> https://slotracer.online/community/showthread.php?tid=5144 Fri, 02 Jan 2026 22:50:25 +0000 https://slotracer.online/community/showthread.php?tid=5144

IMG_9337.jpeg Size: 1.16 MB Downloads: 21

Here’s an MPD F1 installed in the same Carrera F1 car. 351sq.mm. Around 35% smaller.
Top view.

IMG_9835.jpeg Size: 1.48 MB Downloads: 23

Side view:

IMG_9833.jpeg Size: 965.43 KB Downloads: 19

IMG_9834.jpeg Size: 1.48 MB Downloads: 19

]]>

IMG_9337.jpeg Size: 1.16 MB Downloads: 21

Here’s an MPD F1 installed in the same Carrera F1 car. 351sq.mm. Around 35% smaller.
Top view.

IMG_9835.jpeg Size: 1.48 MB Downloads: 23

Side view:

IMG_9833.jpeg Size: 965.43 KB Downloads: 19

IMG_9834.jpeg Size: 1.48 MB Downloads: 19

]]> <![CDATA[Scorpius Controller]]> https://slotracer.online/community/showthread.php?tid=5139 Thu, 01 Jan 2026 08:39:06 +0000 https://slotracer.online/community/showthread.php?tid=5139 The Carrera car chip has only 15 throttle steps. We can add two extra steps in between existing steps to give 45 but the graph I'm using just has the 15 steps to keep it simple.
The graph shows a black line which is the factory throttle map, a single linear line.
I designed the purple, green, blue and red maps as examples. The orange lines show the difference on motor speed for the original linear line compared to the purple map.
The throttle position is around 73/100. On the Carrera line its a level 11 motor speed. On the Scorpius purple map its a 12. This shows how you can vary the original set up to anything you like. No other system offers this type of set up. It drastically improves the driver experience. It makes it easier to race. Consequently, lap times are reduced considerably, and that's the entire goal. And yes you can store 10 throttle maps on the Scorpius controller. You can recall each one on the fly without having to stress simply by rotating the sensitivity knob. A game changer for Carrera users.

Throttle mapping template 4 ideas ttt.jpg Size: 193.64 KB Downloads: 38

]]> The Carrera car chip has only 15 throttle steps. We can add two extra steps in between existing steps to give 45 but the graph I'm using just has the 15 steps to keep it simple.
The graph shows a black line which is the factory throttle map, a single linear line.
I designed the purple, green, blue and red maps as examples. The orange lines show the difference on motor speed for the original linear line compared to the purple map.
The throttle position is around 73/100. On the Carrera line its a level 11 motor speed. On the Scorpius purple map its a 12. This shows how you can vary the original set up to anything you like. No other system offers this type of set up. It drastically improves the driver experience. It makes it easier to race. Consequently, lap times are reduced considerably, and that's the entire goal. And yes you can store 10 throttle maps on the Scorpius controller. You can recall each one on the fly without having to stress simply by rotating the sensitivity knob. A game changer for Carrera users.

Throttle mapping template 4 ideas ttt.jpg Size: 193.64 KB Downloads: 38

]]> <![CDATA[Scorpius RF and CU BT to SmartRace using Wifi]]> https://slotracer.online/community/showthread.php?tid=5053 Fri, 31 Oct 2025 12:18:22 +0000 https://slotracer.online/community/showthread.php?tid=5053
Firstly a smart device can talk to 7 devices but can only listen to one at a time when using BT. But they are good at processing wifi and BT simultaneously.
So let’s make a converter. An MPD straight into an ESP32 (hardwired), battery powered. Stand alone, no cables. Now into a nice enclosure.
The MPD listens on channel 25 and passes it to the ESP32 using SPI. Here the MPD is able to be used as a dongle as USB is not required and we can use the data port.

After speaking to Marc at SmartRace this is definitely doable.

Obviously the app receives basic race info from the Carrera CU using their BT dongle.
But the opportunity exists to take any or all of the possible Scorpius data. So what’s available?

We have 3 sites of telemetry.
1. Controller.
2. Track.
3. Car.

1. Controller: The car reads the track beacons and processes controller data simultaneously. In the controller we gather and use this data:
Controller ID
Controller PIN
Lane change status yes/no?
Throttle speed
Brake sensitivity
Driver name.

2. Track:
Sector or LB ID number.
Lane number
Start finish line.

Each lane changer broadcasts a message continuously from the track LED we call a beacon. The car gathers this info and uses it for various functions.

So far we have 2 lots of important data. But about car data?

3. Car:
Car specific telemetry.
Throttle speed after being mapped.
Firmware version number.
Tacho reading.
Hall sensor.
Accelerometer X axis.
Accelerometer Y axis.
Accelerometer Z axis.
Sound preference.

So around 16 lots of data within the telemetry stream. Some of this data is useless and others look promising.
Like having your automatically entered into the app ala Scorpius RMS.
Collision detection between any amount of cars. From what direction. And how much for.
So now we can detect who shunted who, who caused a collision at any lane changer, detect deslots, detect roll overs.
Tacho for tuning and testing. Even fuel usage.
More accurate throttle readings more often for working out fuel useage. Same with brakes using brake telemetry.
Of our transmission window we dedicate around 30% for telemetry so that’s around 30 transmissions per second which equates to a maximum 10 complete packages per second. This gives a true and accurate picture to pass to to the software/appware guys.

Welcome to the new era.

IMG_9172.png Size: 462.75 KB Downloads: 44

]]>
Firstly a smart device can talk to 7 devices but can only listen to one at a time when using BT. But they are good at processing wifi and BT simultaneously.
So let’s make a converter. An MPD straight into an ESP32 (hardwired), battery powered. Stand alone, no cables. Now into a nice enclosure.
The MPD listens on channel 25 and passes it to the ESP32 using SPI. Here the MPD is able to be used as a dongle as USB is not required and we can use the data port.

After speaking to Marc at SmartRace this is definitely doable.

Obviously the app receives basic race info from the Carrera CU using their BT dongle.
But the opportunity exists to take any or all of the possible Scorpius data. So what’s available?

We have 3 sites of telemetry.
1. Controller.
2. Track.
3. Car.

1. Controller: The car reads the track beacons and processes controller data simultaneously. In the controller we gather and use this data:
Controller ID
Controller PIN
Lane change status yes/no?
Throttle speed
Brake sensitivity
Driver name.

2. Track:
Sector or LB ID number.
Lane number
Start finish line.

Each lane changer broadcasts a message continuously from the track LED we call a beacon. The car gathers this info and uses it for various functions.

So far we have 2 lots of important data. But about car data?

3. Car:
Car specific telemetry.
Throttle speed after being mapped.
Firmware version number.
Tacho reading.
Hall sensor.
Accelerometer X axis.
Accelerometer Y axis.
Accelerometer Z axis.
Sound preference.

So around 16 lots of data within the telemetry stream. Some of this data is useless and others look promising.
Like having your automatically entered into the app ala Scorpius RMS.
Collision detection between any amount of cars. From what direction. And how much for.
So now we can detect who shunted who, who caused a collision at any lane changer, detect deslots, detect roll overs.
Tacho for tuning and testing. Even fuel usage.
More accurate throttle readings more often for working out fuel useage. Same with brakes using brake telemetry.
Of our transmission window we dedicate around 30% for telemetry so that’s around 30 transmissions per second which equates to a maximum 10 complete packages per second. This gives a true and accurate picture to pass to to the software/appware guys.

Welcome to the new era.

IMG_9172.png Size: 462.75 KB Downloads: 44

]]> <![CDATA[Scorpius MPD Mini for Carrera]]> https://slotracer.online/community/showthread.php?tid=4981 Mon, 08 Sep 2025 23:10:15 +0100 https://slotracer.online/community/showthread.php?tid=4981
It’s just 24.8x14.0x1.7
347.2 sq.mm. It’s the second smallest decoder in terms of area on the market and the smallest decoder in terms of volume at 590.2 cubic mm compared to the next 1735 cubic mm.
Native compatible or use with Scorpius controller and Nitrous dongle.

It comes with power and motor wires and the IR LED. That’s it.
Simple yet deadly.

Of course you can solder any accessory on that you like as the firmware will be identical to its big brother decoder with JSTs.

Again the MPD comes to the front.
Hardware complete.
Firmware complete.
Vapourware delete.
Wavegreen

*Soldering skills required.

IMG_8671.jpeg Size: 1.6 MB Downloads: 44

]]>
It’s just 24.8x14.0x1.7
347.2 sq.mm. It’s the second smallest decoder in terms of area on the market and the smallest decoder in terms of volume at 590.2 cubic mm compared to the next 1735 cubic mm.
Native compatible or use with Scorpius controller and Nitrous dongle.

It comes with power and motor wires and the IR LED. That’s it.
Simple yet deadly.

Of course you can solder any accessory on that you like as the firmware will be identical to its big brother decoder with JSTs.

Again the MPD comes to the front.
Hardware complete.
Firmware complete.
Vapourware delete.
Wavegreen

*Soldering skills required.

IMG_8671.jpeg Size: 1.6 MB Downloads: 44

]]> <![CDATA[Carrera Digital D132 D124 Wireless+ Handle Accessory]]> https://slotracer.online/community/showthread.php?tid=4830 Wed, 21 May 2025 23:46:51 +0100 https://slotracer.online/community/showthread.php?tid=4830 Turn your plunger controller into a trigger controller!
NO HARDWARE REQUIRED! NO DAMAGE TO THE CONTROLLER!

IMG20250521064031.jpg Size: 619.76 KB Downloads: 66

https://www.printables.com/model/1303295]]> Turn your plunger controller into a trigger controller!
NO HARDWARE REQUIRED! NO DAMAGE TO THE CONTROLLER!

IMG20250521064031.jpg Size: 619.76 KB Downloads: 66

https://www.printables.com/model/1303295]]> <![CDATA[Improving Carrera protocols using Nitrous]]> https://slotracer.online/community/showthread.php?tid=4687 Tue, 07 Jan 2025 14:31:42 +0000 https://slotracer.online/community/showthread.php?tid=4687 The Controller is where it all begins. The Scorpius controller has a long list of goodies but how useable is that on a Carrera system.

A quick look at the Carrera controller sees only a trigger and a button as opposed to a trigger, 3 buttons and 3 knobs on a Scorpius controller.
The Carrera controller puts out 16 control steps compared to 256 on Scorpius. It has 10 braking steps set in the Control Unit not the controller compared to 256 on the Scorpius controller. And a plunger type controller versus trigger type on the Scorpius controller.

I can think of a few ways to get better lap times.
Let's start with throttle mapping.
We cant change how many steps the Carrera controller puts out. It will always be limited to 16. But we can take those steps and change the power output in the MPD Nitrous decoder.
This has never been attempted before. How ever it is simply a variation of the Scorpius Throttle Set Up program.
Instead of using this configuration program to upload to the Scorpius controller it is uploaded to the MPD Nitrous decoder.

In the diagram shown we compare a Carrera linear map to a customised one. The amount of possible maps that can be written is almost infinite.
We can set brakes 0-100, a minimum, a maximum, a choke set up, add a driver name (used in RMS functions), select ID, select a PIN, we could even implement traction control. But I'll go into those later.

The map could be recalled, re-edited and re-uploaded to the Nitrous car decoder.
As you could imagine this proposed software and firmware opens up an entire new world for Carrera users.

Throttle mapping.jpg Size: 179.33 KB Downloads: 85

]]> The Controller is where it all begins. The Scorpius controller has a long list of goodies but how useable is that on a Carrera system.

A quick look at the Carrera controller sees only a trigger and a button as opposed to a trigger, 3 buttons and 3 knobs on a Scorpius controller.
The Carrera controller puts out 16 control steps compared to 256 on Scorpius. It has 10 braking steps set in the Control Unit not the controller compared to 256 on the Scorpius controller. And a plunger type controller versus trigger type on the Scorpius controller.

I can think of a few ways to get better lap times.
Let's start with throttle mapping.
We cant change how many steps the Carrera controller puts out. It will always be limited to 16. But we can take those steps and change the power output in the MPD Nitrous decoder.
This has never been attempted before. How ever it is simply a variation of the Scorpius Throttle Set Up program.
Instead of using this configuration program to upload to the Scorpius controller it is uploaded to the MPD Nitrous decoder.

In the diagram shown we compare a Carrera linear map to a customised one. The amount of possible maps that can be written is almost infinite.
We can set brakes 0-100, a minimum, a maximum, a choke set up, add a driver name (used in RMS functions), select ID, select a PIN, we could even implement traction control. But I'll go into those later.

The map could be recalled, re-edited and re-uploaded to the Nitrous car decoder.
As you could imagine this proposed software and firmware opens up an entire new world for Carrera users.

Throttle mapping.jpg Size: 179.33 KB Downloads: 85

]]> <![CDATA[Scorpius MPD Nitrous Lane Brain for Carrera.]]> https://slotracer.online/community/showthread.php?tid=4480 Wed, 21 Aug 2024 08:57:40 +0100 https://slotracer.online/community/showthread.php?tid=4480 As you may know the MPD decoder will be configured to 13 separate products hence the name Multi Protocol Decoder.

Here’s the MPD configured as a lane change controller for Carrera. The decoder can receive data via wireless or via the power in wire pair. The decoder has 2 photo transistor circuits. One for lane changing and one for anti collision.
The MPD can run a single or double lane changer. In both circumstances anti collision is possible.
So it’s perfect for a Carrera Lane Changer.

Advantages:
1. Anti Collision function.
2. Track telemetry. Each Lane Brain is given a unique ID. Perfect for pit lane, pit bay and sector timing.
3. Ability to upgrade from 6 cars to 24 cars. Requires Nitrous car decoder.
4. Perfect for Carrera timber tracks.

Pic 1 MPD installed
Pic 2 Anti Collision Photo sensor

0771922A-271D-426D-A4EE-629955A130C6.jpeg Size: 1.22 MB Downloads: 98

BAAB1D21-E488-41F1-8E38-BFBFD89F8984.jpeg Size: 3.57 MB Downloads: 92

]]> As you may know the MPD decoder will be configured to 13 separate products hence the name Multi Protocol Decoder.

Here’s the MPD configured as a lane change controller for Carrera. The decoder can receive data via wireless or via the power in wire pair. The decoder has 2 photo transistor circuits. One for lane changing and one for anti collision.
The MPD can run a single or double lane changer. In both circumstances anti collision is possible.
So it’s perfect for a Carrera Lane Changer.

Advantages:
1. Anti Collision function.
2. Track telemetry. Each Lane Brain is given a unique ID. Perfect for pit lane, pit bay and sector timing.
3. Ability to upgrade from 6 cars to 24 cars. Requires Nitrous car decoder.
4. Perfect for Carrera timber tracks.

Pic 1 MPD installed
Pic 2 Anti Collision Photo sensor

0771922A-271D-426D-A4EE-629955A130C6.jpeg Size: 1.22 MB Downloads: 98

BAAB1D21-E488-41F1-8E38-BFBFD89F8984.jpeg Size: 3.57 MB Downloads: 92

]]> <![CDATA[Scorpius to Carrera Dongle]]> https://slotracer.online/community/showthread.php?tid=4435 Wed, 31 Jul 2024 22:00:34 +0100 https://slotracer.online/community/showthread.php?tid=4435 The SCX Solenoid driver and pins has been replaced by a Digital to Analogue Converter chip or DAC.
Our OLED driver connects to a 0.49" OLED screen to select channels.
We have utilised the two Photo Transistor analogue input pins to connect a set switch.
As usual the MPD is used as the mother board.
The board is powered off the 5V supply from the CU.
The DAC chip connects to the CU via the RJ12 telephone plug.
The Scorpius Controller to MPD data is complete.
And work is underway in the next few weeks to implement Carrera Controller protocols to the CU.
So as you can see the MPD really is a Multi Protocol Decoder capable of almost anything.
In fact the Controller, USB Dongle and MPD can do every single function required for any brand. Very cool indeed.
The MPD boasts digital in/outs and now Analogue in/outs.
Along with the TX/RX in/outs added and the OLED driver this is going to be a killer product. Checkeredflag

And all this in 22.00x13.3mm.
Thankyou Johnny you are a legend!

Nitrous 8.jpg Size: 64.9 KB Downloads: 106

Rick]]> The SCX Solenoid driver and pins has been replaced by a Digital to Analogue Converter chip or DAC.
Our OLED driver connects to a 0.49" OLED screen to select channels.
We have utilised the two Photo Transistor analogue input pins to connect a set switch.
As usual the MPD is used as the mother board.
The board is powered off the 5V supply from the CU.
The DAC chip connects to the CU via the RJ12 telephone plug.
The Scorpius Controller to MPD data is complete.
And work is underway in the next few weeks to implement Carrera Controller protocols to the CU.
So as you can see the MPD really is a Multi Protocol Decoder capable of almost anything.
In fact the Controller, USB Dongle and MPD can do every single function required for any brand. Very cool indeed.
The MPD boasts digital in/outs and now Analogue in/outs.
Along with the TX/RX in/outs added and the OLED driver this is going to be a killer product. Checkeredflag

And all this in 22.00x13.3mm.
Thankyou Johnny you are a legend!

Nitrous 8.jpg Size: 64.9 KB Downloads: 106

Rick]]> <![CDATA[Scorpius/Carrera Nitrous System]]> https://slotracer.online/community/showthread.php?tid=4433 Wed, 31 Jul 2024 11:50:15 +0100 https://slotracer.online/community/showthread.php?tid=4433
Level 1: MPD car decoder in Carrera native mode.
Level 2: Controller: Use Controller and Scorpius to Carrera Bluetooth Dongle (hardwire from unit to CU) for use with Carrera native system and enhanced Nitrous system.
Level 3: Add in MPD Car Decoder using Scorpius protocols for full Nitrous system.
Level 4: Add in Nitrous RF to Bluetooth converter to enable MPD to/from App.
Level 5: Add in MPD Lane Brain in Carrera mode for track comms for pit lane detection, pit bay detection 1-6, programmable race line, sector timing and lane changing for Carrera timber track builders.

Nitrous 5.jpg Size: 218.45 KB Downloads: 142

Click to enlarge]]>
Level 1: MPD car decoder in Carrera native mode.
Level 2: Controller: Use Controller and Scorpius to Carrera Bluetooth Dongle (hardwire from unit to CU) for use with Carrera native system and enhanced Nitrous system.
Level 3: Add in MPD Car Decoder using Scorpius protocols for full Nitrous system.
Level 4: Add in Nitrous RF to Bluetooth converter to enable MPD to/from App.
Level 5: Add in MPD Lane Brain in Carrera mode for track comms for pit lane detection, pit bay detection 1-6, programmable race line, sector timing and lane changing for Carrera timber track builders.

Nitrous 5.jpg Size: 218.45 KB Downloads: 142

Click to enlarge]]> <![CDATA[Carrera Startlight brightness]]> https://slotracer.online/community/showthread.php?tid=4359 Sat, 01 Jun 2024 13:38:18 +0100 https://slotracer.online/community/showthread.php?tid=4359 Does anyone know the instructions for adjusting the brightness level of the red light on top of the startlight please?
I swear that I have done this vefore but can't remember where I found out how to do it.....?

Regards,

Mark V]]> Does anyone know the instructions for adjusting the brightness level of the red light on top of the startlight please?
I swear that I have done this vefore but can't remember where I found out how to do it.....?

Regards,

Mark V]]> <![CDATA[PWM frequency]]> https://slotracer.online/community/showthread.php?tid=4260 Sun, 17 Mar 2024 09:59:10 +0000 https://slotracer.online/community/showthread.php?tid=4260 TIA]]> TIA]]> <![CDATA[Brushless Carrera Digital]]> https://slotracer.online/community/showthread.php?tid=4186 Fri, 02 Feb 2024 00:12:33 +0000 https://slotracer.online/community/showthread.php?tid=4186
]]>
]]> <![CDATA[Scorpius MPD for Carrera]]> https://slotracer.online/community/showthread.php?tid=4143 Mon, 08 Jan 2024 19:00:17 +0000 https://slotracer.online/community/showthread.php?tid=4143 Ok so all the foundation work for the MPD was completed yesterday. Things like RTOS, bootloader, DFU, parameter library and Scorpius protocol have been completed and debugged.
As some of you might know the MPD prototype has been designed and built to run on Carrera, Scalextric, Ninco and SCX systems.
Yesterday I received an email from John our engineer with the latest firmware release V13.0. It contains amongst other things the Carrera motor drive completed. We are glad to say we were able to implement this quickly and without any debug required. So our Carrera commitment has started there is no turning back. Next will be implementing the lane change code.

There is much planned for Carrera users. The plan is to make all the Scorpius protocols or as much as possible available to the Carrera community.

Some of the things coming are:

Worlds first 2.4ghz wireless car chip to be 100% Carrera compatible.

A 2.4 GHz controller based on the Scorpius controller using 100% Carrera protocol.

A new revolutionary highly functional dual Comms system called Nitrous where the Scorpius controller will talk to both the Carrera CU and MPD chipped car simultaneously. This allows all existing CU and RMS functions to operate as per normal and allows us to get a lane change command to the lane changer via rails as per the true Carrera protocol without using rubber bands and work arounds.
The possibilities here for the Carrera community are mind blowing. Imagine telemetry, accelerator and Back EMF based functions like our new virtual Dyno, Scorpius and SSD compatibility and more for Carrera users? Wavegreen

The project continues……

Rick]]> Ok so all the foundation work for the MPD was completed yesterday. Things like RTOS, bootloader, DFU, parameter library and Scorpius protocol have been completed and debugged.
As some of you might know the MPD prototype has been designed and built to run on Carrera, Scalextric, Ninco and SCX systems.
Yesterday I received an email from John our engineer with the latest firmware release V13.0. It contains amongst other things the Carrera motor drive completed. We are glad to say we were able to implement this quickly and without any debug required. So our Carrera commitment has started there is no turning back. Next will be implementing the lane change code.

There is much planned for Carrera users. The plan is to make all the Scorpius protocols or as much as possible available to the Carrera community.

Some of the things coming are:

Worlds first 2.4ghz wireless car chip to be 100% Carrera compatible.

A 2.4 GHz controller based on the Scorpius controller using 100% Carrera protocol.

A new revolutionary highly functional dual Comms system called Nitrous where the Scorpius controller will talk to both the Carrera CU and MPD chipped car simultaneously. This allows all existing CU and RMS functions to operate as per normal and allows us to get a lane change command to the lane changer via rails as per the true Carrera protocol without using rubber bands and work arounds.
The possibilities here for the Carrera community are mind blowing. Imagine telemetry, accelerator and Back EMF based functions like our new virtual Dyno, Scorpius and SSD compatibility and more for Carrera users? Wavegreen

The project continues……

Rick]]> <![CDATA[Oxigen or Scorpius-- can I get some guidance?]]> https://slotracer.online/community/showthread.php?tid=3881 Sun, 03 Sep 2023 00:54:32 +0100 https://slotracer.online/community/showthread.php?tid=3881
I have been looking at Oxigen and Scorpius for later down the road as options for a more robust home setup and am wondering if any of you have opinions on which system would be a better investment. What interests me is ghost cars, pit lane speeds-- which system is more robust and will give me the least amount of headaches?

An additional question I have: I don't really want to invest in Carrera wireless controllers because I plan on eventually incorporating one of these systems. From this angle, it seems like it's a better option to go wired and add the wireless receiver when I'm ready to buy into either the Oxigen or Scorpius.

Can any of you seasoned hobbyists weigh in? What's the most cost-effective way of doing this? I hope my questions make sense and am eager to hear your insight.]]>
I have been looking at Oxigen and Scorpius for later down the road as options for a more robust home setup and am wondering if any of you have opinions on which system would be a better investment. What interests me is ghost cars, pit lane speeds-- which system is more robust and will give me the least amount of headaches?

An additional question I have: I don't really want to invest in Carrera wireless controllers because I plan on eventually incorporating one of these systems. From this angle, it seems like it's a better option to go wired and add the wireless receiver when I'm ready to buy into either the Oxigen or Scorpius.

Can any of you seasoned hobbyists weigh in? What's the most cost-effective way of doing this? I hope my questions make sense and am eager to hear your insight.]]> <![CDATA[Slot car beginner with a question]]> https://slotracer.online/community/showthread.php?tid=3696 Sun, 23 Apr 2023 04:12:21 +0100 https://slotracer.online/community/showthread.php?tid=3696 <![CDATA[Carrera track repair]]> https://slotracer.online/community/showthread.php?tid=2220 Sun, 30 May 2021 07:28:01 +0100 https://slotracer.online/community/showthread.php?tid=2220

20210529_211732.jpg Size: 4.25 MB Downloads: 287

20210529_211757.jpg Size: 3.81 MB Downloads: 265

I think this turned out pretty well.

I also learned something that I probably should have known already about Carrera track. The little spring clips that connect the rails to one another are a separate piece from the actual rail. The reason I now know this is in the process of snapping the tabs off it also loosened the clips in the rails. So I printed up a 3.5mm x 3.5mm x 15mm piece to install in the clip to tighten them up. With them installed when the track pieces are assembled the rail connections are nice and sung and should have a very good connection. I will be trying these in the spots on the track where I have been having issues and am to lazy to add a power tap. If it works in those spots I might start installing them in all of the track as I have a reason to take it apart. The pieces I installed in the rails can be seen in the above pics.

Hope everyone has a great weekend!

Kevin]]>

20210529_211732.jpg Size: 4.25 MB Downloads: 287

20210529_211757.jpg Size: 3.81 MB Downloads: 265

connections.jpg Size: 329.86 KB Downloads: 156

]]>
Thanks!

connections.jpg Size: 329.86 KB Downloads: 156

]]> <![CDATA[Carrera Digital Track call button]]> https://slotracer.online/community/showthread.php?tid=2071 Fri, 02 Apr 2021 16:44:04 +0100 https://slotracer.online/community/showthread.php?tid=2071
I will preface this by saying if your Control unit is still in warranty, this will void the warranty!

I took apart my control unit and soldered a wire to both sides of the start switch contacts and ran it out of the bottom of the track connected to the control unit. I added a male JST 2 pin connector to it so I could easily connect and disconnect to the external switches. From here I ran to a distribution block where all of the switches will connect.

20210402_092952.jpg Size: 4.11 MB Downloads: 174

20210402_093002.jpg Size: 5.21 MB Downloads: 221

20210402_093226.jpg Size: 5.82 MB Downloads: 152

My distribution block has 4 wire connections because I will be adding a ATX power supply to my panel to use the 3.3 volt power for back lighting the switches with SMD LEDs. (Future Project) From the distribution block I run to each individual switch.

20210402_092256.jpg Size: 5.53 MB Downloads: 204

20210402_092306 rs.jpg Size: 4.58 MB Downloads: 177

20210402_103853.jpg Size: 5.12 MB Downloads: 179

The switch is based on how Carrera does the switches for the control unit as a matter of fact the switches are from a blown up control unit. I added 6 switches, one for each driver. This now allows any driver to pause and restart the race when they crash. While this might not be for everybody, I find it very useful for racing with my kids.

Happy racing,
Kevin]]>
I will preface this by saying if your Control unit is still in warranty, this will void the warranty!

I took apart my control unit and soldered a wire to both sides of the start switch contacts and ran it out of the bottom of the track connected to the control unit. I added a male JST 2 pin connector to it so I could easily connect and disconnect to the external switches. From here I ran to a distribution block where all of the switches will connect.