Hi there oXygen fans and criticasters,
Yesterday ran we an extensive test program using only the SCP 1.0 with the radio cartridges and the car chips.
We used Proslot III powered 1/28 P & n chassis with a Mazda 787B we normally use for analogue races and testing.
What we tested
Programming the SCP-1.0 / Carchip ID's using the the SCP-1.0 itself > Worked flawlessly
Car response on trigger movement compared to 2 other controller types (PWM controller and NPN transistor (Not a darlington with HFE of 100) using a voltage bridge (wiper) of approx 200 ohms
Various settings of the dipswitches (35%, 45%, 55% 60%) in conjunction with the mainly the curve knob.
Results
Car response is beyond what our club ciriticasters expected it to be! Which means response is really good
Braking power (very important for the heavier 1/28 1/24 scale) is much better. This is due to the fact that the braking current of the engine does NOT have to flow through the whole track > back to the controller and then to (-) of the powerbase.
Compared to our NPN transistor (just like the difalco, stealth, nezih controllers) the brake response (not brake power) is slightly less. I normal terms. The time it takes before the car starts braking after you release the trigger is very little higher then a direct shortcut brake. This behaviour is by the way normal for every PWM based controller and has nothing to do with the SCP 1.0 or oXygen system. An ACD controller suffers form the same problem.
Question
As said, reprogramming the car worked flawlessly but:
What happens if I use the documented procedure and I put 2 cars on the powered track and try to program them on the same time? In other words: How does the carchip know it's is "him" who needs to set it's internal ID? In other words part II: How does the carchip which should NOT be programmed know this?
For the rest: Tomorrow I receive the dongle (probably firmware 1.0) so I got some reflashing to do......
Keep you posted...
Willem
Yesterday ran we an extensive test program using only the SCP 1.0 with the radio cartridges and the car chips.
We used Proslot III powered 1/28 P & n chassis with a Mazda 787B we normally use for analogue races and testing.
What we tested
Programming the SCP-1.0 / Carchip ID's using the the SCP-1.0 itself > Worked flawlessly
Car response on trigger movement compared to 2 other controller types (PWM controller and NPN transistor (Not a darlington with HFE of 100) using a voltage bridge (wiper) of approx 200 ohms
Various settings of the dipswitches (35%, 45%, 55% 60%) in conjunction with the mainly the curve knob.
Results
Car response is beyond what our club ciriticasters expected it to be! Which means response is really good
Braking power (very important for the heavier 1/28 1/24 scale) is much better. This is due to the fact that the braking current of the engine does NOT have to flow through the whole track > back to the controller and then to (-) of the powerbase.
Compared to our NPN transistor (just like the difalco, stealth, nezih controllers) the brake response (not brake power) is slightly less. I normal terms. The time it takes before the car starts braking after you release the trigger is very little higher then a direct shortcut brake. This behaviour is by the way normal for every PWM based controller and has nothing to do with the SCP 1.0 or oXygen system. An ACD controller suffers form the same problem.
Question
As said, reprogramming the car worked flawlessly but:
What happens if I use the documented procedure and I put 2 cars on the powered track and try to program them on the same time? In other words: How does the carchip know it's is "him" who needs to set it's internal ID? In other words part II: How does the carchip which should NOT be programmed know this?
For the rest: Tomorrow I receive the dongle (probably firmware 1.0) so I got some reflashing to do......
Keep you posted...
Willem