29th-Jul-24, 04:17 AM
Ok lights are now controllable from LC button, brake lights and headlight flash on confirmation of ID pairing complete.
We will now compare all our speed settings to those of a standard factory Carrera chip, something most other 3rd party developers have not been able to achieve. We will adjust if required to replicate the factory chip precisely.
We will also compare braking values for each step to match the factory chip precisely.
And lastly run the car in a variety of situations to see if track noise affects any data on rails which can cause a multitude of issues from loss of ID to run away cars.
We have purposely not used any online resources in regard to the Carrera car decoder protocols in order not to follow any one else’s errors. As I said previously this has not been a straight forward exercise and has been purely hard work. But 100% genuine compatibility in every area is the goal. We are very close.
So, what’s next? This is where it starts to get interesting indeed. We are about to go somewhere no development team had been with Carrera, the introduction of direct controller to car control. The main objective is to give the Carrera user 256 step throttle control rather than 12 or 15 and 256 braking steps instead of 10. And introduce throttle mapping directly into the car itself.
It is no secret Scorpius has the best throttle and braking resolution and the best refresh rate as well as real time telemetry of any wireless or non wireless system.
Carrera users will now be able to have it all. And the author of SmartRace is looking forward it as much as we are.
In order to achieve the above the Scorpius controller must be utilised. Sure the controller, the best, most functional and most reliable in the wireless market without any firmware errors since release in July 2011 (a remarkable record) will need to control the car and simultaneously send identical data to the Carrera CU to achieve lane changing without compromises or rubber bands. This also allows the Carrera Control Unit (CU) to count laps, work out fuel and send data to existing race software and apps. This is a very important requirement.
So….how to do this?
I’ll tell you soon.
Rick
We will now compare all our speed settings to those of a standard factory Carrera chip, something most other 3rd party developers have not been able to achieve. We will adjust if required to replicate the factory chip precisely.
We will also compare braking values for each step to match the factory chip precisely.
And lastly run the car in a variety of situations to see if track noise affects any data on rails which can cause a multitude of issues from loss of ID to run away cars.
We have purposely not used any online resources in regard to the Carrera car decoder protocols in order not to follow any one else’s errors. As I said previously this has not been a straight forward exercise and has been purely hard work. But 100% genuine compatibility in every area is the goal. We are very close.
So, what’s next? This is where it starts to get interesting indeed. We are about to go somewhere no development team had been with Carrera, the introduction of direct controller to car control. The main objective is to give the Carrera user 256 step throttle control rather than 12 or 15 and 256 braking steps instead of 10. And introduce throttle mapping directly into the car itself.
It is no secret Scorpius has the best throttle and braking resolution and the best refresh rate as well as real time telemetry of any wireless or non wireless system.
Carrera users will now be able to have it all. And the author of SmartRace is looking forward it as much as we are.
In order to achieve the above the Scorpius controller must be utilised. Sure the controller, the best, most functional and most reliable in the wireless market without any firmware errors since release in July 2011 (a remarkable record) will need to control the car and simultaneously send identical data to the Carrera CU to achieve lane changing without compromises or rubber bands. This also allows the Carrera Control Unit (CU) to count laps, work out fuel and send data to existing race software and apps. This is a very important requirement.
So….how to do this?
I’ll tell you soon.
Rick
![[+]](https://slotracer.online/community/images/bootbb/collapse_collapsed.png)