Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Scorpius Multi Purpose Decoder
#21

Hi Guys,
   It’s all about apps these days. In fact I’m about to use the Scorpius app to upload the latest firmware test patch. All on my phone I can download the latest firmware from my emails and save to files, then open app and upload to car in under 30 seconds. Carrera and Scalextric power bases connect to apps but Scorpius doesn’t have a power base.

So what to do?
How about we add a second radio chip to
the MPD and make it a dedicated BT chip just for phone connection? 
I think it’s a decision that if I said yes I would never regret it. Direct car to phone Comms whilst carrying out Scorpius proprietary Comms on full 2.4GHz. Imagine that? 

I must also clarify even though the MPD has the 832 chip by Nordic which is both full 2.4Ghz and Bluetooth it can only do one  or the other. Not simultaneously and hence the thought of doubling up on radio chips. 

Of course it will make the board bigger but we do have most of side B to use up and another layer would come in handy here. It that case no bigger board.
The current MPD prototype is exactjy that, a prototype. New ideas are inevitable. Another world first……assuming John gives the go ahead.  Cool


Attached Files Thumbnail(s)
   
[+] 1 member Likes ScorpiusWireless's post
Quote
#22

A while ago on another forum an enthusiast posted pics of an OLED. 0.49” screen mounted in the windscreen of a 1/32 scale slot car used to identify the cars number. I must say it looked really cool. And now that we have decided to use back EMF detection for motor speed, eliminating wires and hardware I was thinking of ditching the hall sensor, adding one more pin and make use of the available space for an OLED plug n play screen.

I think it would make a nice touch. The screen simply displays the cars ID number between 1-24. 

The twin radio proposal although not confirmed is looking good. This will also be revolutionary and a bench mark in the industry. This involves adding a second BT chip in addition to the highly regarded nRF52832 chip. This will allow the car to talk to controller and phone simultaneously.
The possibilities are full on and very exciting. (….read Bluetooth headset for example) Let’s hope we proceed with this. 

Other news: Now that the DPR JST plug is not going directly on board but rather in short flylead it makes sense to convert to Scorpius wiring pattern which suits Carrera and other brands better.
The SMD capacitor not quite big enough to keep lights on properly over dead spots so a plug n play optional cap on flylead could be an option or we simply make the onboard SMD cap bigger but this will mean a slightly larger PCB which I’m happy to do if required. 
The revolutionary plug n play accessories addition for the MPD would allow such a plug in. You could even choose the cap rating.

Next, a slight hesitation in car acceleration sees a new patch (yet to be tested) issued in the last few hours. I look forward to that.

An incompatibility between new firmware and existing Scorpius lap count software being looked at.

Lane changing coming up on telemetry but not changing lanes. This is being looked at.

DPR hatch. 2 updated 3D printed prototypes arrive Thur. No doubt one final round of changes will be required. Just need to order stainless self tapper screws.

Debugging Carrera car protocols starts.

So a number of possible hardware changes coming. Remember this chip has to (and will) last a decade without hardware changes like the last chip. Once I make the bed I have lie in it hence the need to include all required hardware for foreseen functions and new functions coming in the next decade. This philosophy worked 100% on the last version.

Pic of 0.49” OLED screen.


Attached Files Thumbnail(s)
   
[+] 3 members Like ScorpiusWireless's post
Quote
#23

Scorpius MPD in a Thunderslot Lola using 2.0 JST plugs.
Lapcounting debugged.
Onto lane change debug.
Slight hesitation has crept in to motor drive albeit rarely so a debug required there.
About 1/4 the way into Carrera car chip debug. Need to complete Scorpius debug process first.


Attached Files Thumbnail(s)
       
[+] 1 member Likes ScorpiusWireless's post
Quote
#24

Hi Guys.
   John made a nice programming jig with stainless hardware, a custom PCB made especially for this board and 3D printed board holder that holds the decoder firmly and exactly in position.
Under the chip you’ll see 4 programming pads. This will eventually be shipped to the factory along with a test program.


Attached Files Thumbnail(s)
       
[+] 3 members Like ScorpiusWireless's post
Quote
#25

This decoder in Carrera mode on its way to the USA for beta testing…….
Included on hardware are full lights. These are used to communicate different flashing patterns to indicate certain functions or confirmations. A Carrera LED and Scorpius photo sensor are also wired. All wires are silicon as standard.
More soon.


Attached Files Thumbnail(s)
   
[+] 2 members Like ScorpiusWireless's post
Quote
#26

We’ve had issues with car stuttering and we’ve discovered the accelerometer algorithm needed tweaking. As the car drove around the track it would interpret bumps as the tap tap tap on car with finger function to put into boot mode.
Tap detection now calculates the 3D vector magnitude of acceleration after subtracting the instantaneous acc in each direction from a filtered value for that axis. John has set the threshold for tap detection at ~0.3g and there is a 3 sec delay from powerup to when it will start detecting taps to allow the filters to settle. Upshot is that the car can be tapped from any direction and the pcb doesn't need to be horizontally mounted.
Also we’ve added a auto version numbering to our firmware updates and will keep a strict record of changes so we can refer to them in months or years to come if required.
Pic below of a Scorpius MPD SSD DPR decoder being built up to test with the 3mm infrared LED soldered in place.


Attached Files Thumbnail(s)
   
[+] 3 members Like ScorpiusWireless's post
Quote
#27

MPD Specification/Functionality V2.0

Hi Lads,
   In the last few weeks around 10 hardware changes have decided on. This is because we doubled up in radio chips, deleted the hall sensor, added an OLED display driver just to name a few.
The OLED could be used to input or read data on the MPD. The OLED is 0.5x0.5” and is placed in the top of windscreen on side opposite to driver. Now use the Scorpius controller knob to quickly scroll through the following: Car number # or ID, fuel, brake pad and tyre levels, fuel burn rate, damage level, tyre type, max CG force, engine tacho, brake setting, throttle map.
Fair Dinkum can you imagine scrolling to tacho, lifting the rear wheels off the track and revving it to see your real time engine speed in the windscreen of your favourite car? Jeeeez. Checkeredflag

Can you think of any more? 

We also upped the 10uF SMD capacitor to 100, separated data outputs in each of the SSD drivers, also Carrera drivers. This creates another 2 light 5V channels. And the ability to be a 2 lane analogue lap counter as it was one data circuit previously. 
Length will still be under the original target of 26mm at just 25 currently 22.0mm

Size: 25.0x13.3x3.0
Layers:2
Sides used: 2
Radio/Microprocessor 1: Nordic nRF 52832 6x6mm.
Radio/Microprocessor 2: Nordic nRF 52805 WLCSP 2.48x2.46mm.
Data rates for both: 1MB/sec
Range: 50m
Motor Drive 1: 10A
Motor Drive 2: 10A
Brake Drive: 8.8A
Power in:8.5-18V AC/D
Scorpius photo sensor inputs: 2 (1 mounted on board, 1 on lead).
Carrera IR LED outputs: 2 (1 mounted on board, 1 on lead) *
Scalextric Sport Digital LED outputs: 2 (1 mounted on board, 1 on lead) *
*Can be configured as lights.
Light outputs**: Headlights and tail/brake lights.
**All lights and IR LED outputs can be configured as:
Tail/brake, headlight, flashing light, exhaust flame simulator.
Accelerometer: 3 axis
OLED display driver: Yes
Tacho: Via Back EMF detection
Main capacitor:100uF, surface mounted.
Motor PWM steps: 256
Brake PWM steps: 256
Compatibility: Scorpius, Carre/.kra, Scalextric Sport digital, Ninco*, SCX*
*Scorpius controller required.

Pic of some of our MPD loaded ThunderSlot Lola chassis test cars with 21.5k motor.
   
[+] 1 member Likes ScorpiusWireless's post
Quote
#28

Hi Guys,
V2.0 schematic designed today.

We upgraded the 3 pin hall connection to 4 pin so we can now accomodate BLDC (Brushless DC driver), OLED, Hall sensor, and COMMs (UART connection), this allows hardwired connections to piggy back to various hardware for future projects.

We also added 3x 47uF caps in place of the 10uF (so 14 times more capacity) and added 2 pins for a super cap for lights to stay on long time whilst crossing dead spots.  We also reconfigured the power in/out to suit Carrera. It will still be DPR (Scalextric) compatible.
LED drivers are upgraded to mosfet type rather than transistors. 
John was able to do all this and yet still maintain the same size of just 22.3x13.3mm! Unbelievable.

Next stage is to re-design the actual board. 
Stay tuned Thumbup


Attached Files Thumbnail(s)
   

www.scorpiuswireless.com
Quote
#29

Next task….to add the second radio chip that will be dedicated to talking to your phone. Checkeredflag

www.scorpiuswireless.com
Quote
#30

No go on the second radio chip.
Closer investigation reveals a 6 layer board is required, or expensive micro vias, increased board size, a complete redesign, more components and the cost greatly increased, and the real chance both chips will be clashing with each other adding to room traffic. So the decision not to go ahead with a second radio chip has been made.

So, how to get data to the app?
An RF to BT converter has been designed and will be trialled once V2 MPD chips arrive.

www.scorpiuswireless.com
Quote


Possibly Related Threads...
Thread / Author Replies Views Last Post

Forum Jump:


Users browsing this thread: 1 Guest(s)