C7042 versus Arc Pro. A developers thoughts.

C7042 versus Arc Pro. A developers thoughts. - Printable Version

+- SlotRacer Forum (https://slotracer.online/community)
+-- Forum: Digital (https://slotracer.online/community/forumdisplay.php?fid=12)
+--- Forum: Scalextric (https://slotracer.online/community/forumdisplay.php?fid=13)
+--- Thread: C7042 versus Arc Pro. A developers thoughts. (/showthread.php?tid=4014)

C7042 versus Arc Pro. A developers thoughts. - ScorpiusWireless - 17th-Nov-23

Hi Guys.
So we have the C7042, released in 2011. It featured the ability to run the track protocols via a computer and 3rd party race software.
Developers loved it because they could manipulate the track data to switch lights, add simulations and more. It is however long gone. Dead. And so too all 3rd party software packages aa well as the after market firmware upgrade known as ICP. And pretty much everything that could be done has been. So from a developers aspect there is nothing to be gained for the developer or the enthusiasts.

Fast forward to late 2017 and Hornby replaces the C7042 with their new Arc Pro with wireless throttles and an app. However it is already 6 years old, no throttle protocol has been released to 3rd party developers. The app although great for basic racing but lacks compared to the previous C7042.

What can be done to improve the system?

Powerbase. It seems to have enough power do power modifications are not really required like previous SSD offerings. Could the entire firmware be re-written? Yes. But it has no LCD screen so would require a device to configure it. The lap counting has an unacceptable 1.8 second delay which is both annoying and confusing. It is limited to 6 car IDs and wheats will be. Even if I could increase the number of cars it would no longer be compatible, it would no longer be Scalextric Sport Digital and it would essentially be a stand alone system, which would fail miserably. And who would put effort into a 6 year old product probably nearing the end of its life.

Throttles. The Arc Pro throttle is very basic. You can operate 64 throttle steps, change lanes and operate a button for braking (non adjustable). It is also wireless. Replacing just the throttle with a deluxe controller would offer little if any benefit.

Car decoder. Here the amount of functions that can be added is huge. An after market controller could essentially add many cool and deep functions. But how to implement and access is the question. Here the right team could offer the community long awaited improvements and added functionality.

Lane changer. Here also many cool and deep functions can be added. This also has so much potential it’s mind blowing.

So there we have one developers thoughts of where the Arc Pro is at today and what is what are the obvious avenues of improvement.

So yeah, the car and lane change decoders are where it’s at for real and worthwhile developments.

Over the next 12 months I’ll be building and introducing car and lane change decoders with much added and needed functionality. We won’t fantasise about more than 6 car IDs as it simply won’t be compatible to the Scalextric protocol. But we can add many very cool abd advanced functions to spice up the lives of Hornby enthusiasts. Stay tuned as we progress.

Our first added function is simply lights using our new MPD SSD car decoder working with standard Arc Pro powerbase and controllers. But how to switch lights using a standard Arc Pro system upgraded by adding just the Scorpius MPD car decoder?

So how does a 2023 highly advanced slot car product interact with a 17 year old system using 40 year old DCC protocols?
I know. I’ll tell you soon. Rofl

Rick

RE: C7042 versus Arc Pro. A developers thoughts. - ScorpiusWireless - 18th-Nov-23

So how?
The chip had Bluetooth both in and out.
It also has wireless Comms in and out
And it can receive track packets.

Now let’s look at the Arc Pro controller. It sends wirelessly but does not receive any wireless data. There is no Bluetooth but there is a lane change button and a brake button.

So we have 3 ways of sending messages to the Scorpius MPD decoder. The throttle signal, brake button signal and the lane change signal.
Pressing the lane change button is for lane changing but if the throttle isn’t being used we could use the lane change button.
Once we get the command the MPD we can activate or use some nice functions using Scorpius protocols. Ie turn on lights, turn off lights and flash high beam.
The trigger itself could be used to signal the MPD chip or in conjunction with the lane change button.
The preferred method will be via the brake button. Why? Because as nice as the brake button is the reality is 99% of enthusiasts use dynamic braking. The brake button can now be called the Auxiliary button and sending dots and dashes to the MPD chip via the rails to trigger functions. Example the MOD chip has flashing lights. These could be operated via a unique basic code.
Example you could have it so by pushing LC and brake button simultaneously whilst the motor is off triggers flashing lights to start or stop.
Brake button is used as a high beam flasher.
There’s quite a few ways to send commands.

Development continues……