Jump to content

C-Type

Members
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    2

C-Type last won the day on February 3

C-Type had the most liked content!

Community Reputation

6 Neutral

About C-Type

  • Rank
    Kart Driver

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Many thanks SlotsNZ for the kind help posting the small decoder CAD image and, too, for the reminder to members to maintain politeness across this platform. c
  2. Apologies I have not learned how to post images on this forum.. so here is a link which shows the 7.2mm by 5mm wireless NRF52832 decoder design point. https://www.slotforum.com/forums/index.php?showtopic=197383&p=2456187 The PCBs should clear manufacturing tomorrow. The design has a 7A motor MOSFET and a 5.5A braking MOSFET. The decoder is designed to be AC/DC compatible... so all being well they should be able to drive wirelessly alongside six SSD packet controlled cars. So that could be eight wireless cars alongside six SSD cars... fourteen in total and all using IR strobe for lane-changing and lap counting... well thats the plan. And its a hobbyist endeavour so commercial guys... please be gentle! c
  3. Time to agree to disagree otherwise the forum is going to start to look unfriendly for readers. I have found this and other similar slotcar forums in general extremely friendly. Now back to 7.2mm x 5mm digital decoders... In my case the SSD-compaible version has been prototype manufactured at the PCB level and is on route to my lab for SMD assembly and test. The nRF52832 ESB-compatible version is currently in PCB prototype manufacture. Both will include the 14 car IR ID strobe for lap detection. 14 car control is another matter - I will try not to stir a hornets nest on that one. I am amazed that love of slot cars is capable of stirring up such strong messaging in some quarters. Anyway, always happy to agree to disagree... it is after all no more and no less than a hobby for big kids like us. c
  4. https://www.slotforum.com/forums/index.php?showtopic=194331&p=2329933 Here is the original discussion and description of the exploratory effort around an extended SSD-type of IR LED strobe protocol for up to 14 cars... just in case anyone wishes to retrace steps... c
  5. All fine... as you learn more about the Advance BT unit in achieving your stated goals of extending the SCX system capabilities - it might be useful to refer back to my above posts for insights into how the SCX BT unit is wired and configured. Good luck with the endeavour. c
  6. Hi aussieslotter... Your SCX-A unit and mine will be the same version. If you look closely there are two main lane lap sensors. Each drives a separate sensor input channel via a separate Schmitt trigger input circuit (nice feature to reduce effects of signal noise). Perhaps you are mistakenly assuming they are parallel wired because they take power in parallel... only one of the two main sensor boards has an on-board regulator. (I always wonder if you get the terms parallel and series mixed up as once again you mention you think the parts are in series?). The other two sensor input channels are for pit lane entry and exit. This is via the track edge connector. Again these inputs are interfaced via Schmitt triggers. So thats four sensor inputs... yours will be the same Final thought... if you replace the SCX-A decoder, the SCX-A bluetooth unit and their race app - how much of the SCX system is left? c
  7. Will the above Scorpius small circuit configured for the SCX-A system have the same number of photodetector channels as the SCX-A bluetooth module? i.e. four. Or will a full size Scorpius lane-brain be required to replicate all the functions of the SCX-A module? With the big picture in mind it would be fascinating to learn how far team Scorpius thinking has developed in the area of potential system integration with SCX products. c
  8. I see you have fairly strong opinions on the SCX-A bluetooth module so I dont think I will go there responding to your various points. That said it will be interesting to see how the system holds up in your test loop configuration. c
  9. To add to the above I now have 7.2mm x 5mm decoder designs in two versions. But to be clear, they are not yet built and tested... they are designs only at this stage. For reference my smallest fully tested decoder is SSD-compatibility only and measures 10.8mm x 5.4mm. One of the new 7.2mm x 5mm designs is for compatibility with SSD-track packets and the other one id for wireless 2.4GHz control (Nordic ESB protocol). Both are at PCB prototyping stage. These are extremely small decoders... yet both are designed using 7A motor drive MOSFETs. The SSD-compatible design uses pulsed AC power. The wireless design can run on DC or AC tracks. The latter is important as it means that SSD and wireless controlled cars can race alongside each other. Up to a total of 14 with this approach c
  10. To help keep all of us on track regarding launch dates of Nordic transmit/receive modules - I thought it might add clarity to share some dates Launch of nRF24L01: September 2005 Launch of nRF24L01+: November 2008 (dates as per Nordic website - visited 12/4/21). The plus version is an updated version of the nRF24L01. As the SCX-A bluetooth unit uses the nRF24L01+ its not quite fair to say it uses a sixteen year old nRF device. Then, thinking about the microcontrollers currently used by SCX... it would be great if someone could please identify the part used in the SCX-A bluetooth unit. I suspect it will be an ARM Cortex M0 running at 48MHz. This is what they use in their current SCX-A decoders and wireless throttles and this microcontroller is bang up to date IMHO. I wonder if it makes better sense for manufacturers to exercise a degree of caution when expressing critical opinion of other manufacturers products. Clearly this is a Scorpius thread... but by making reference to the engineering aspects of competitor products... it opens up the thread somewhat. And it seems all too easy to make accidental mistakes when doing so. c
  11. Hi Rick, I wonder if it is slightly misleading to call the nRF24L01+ a microprocessor? Technically it is a radio frequency transmit/receive module not a microprocessor/microcontroller. It then starts to make more sense that SCX are using the nRF24L01+ alongside a reasonable spec microcontroller. Its an entirely valid partitioning of a low cost digital slot car system. And of course the nRF24L01+ remains a valid and current member of the Nordic product range. Out of interest, how many Scorpius in-market products use the nRF24L01+ radio module alongside an 8bit microcontroller? It just feels like you are perhaps being a little harsh on a fairly recently launched competitor product which builds on their many years of in-market expertise. c
  12. Sounds excellent. The Carrera IR sensor arrangement will be great, too, for SCX-A. Looking forward to the cross-system comparisons at vertical-loop warp-speed. c
  13. Yes, the silicon diodes used in the C7005 are only rated at 1A... far less than a state-of-the-art Scorpius decoder. Had it not failed on the test bench - it certainly would have struggled at speed on the steep hill climbs you had in mind for it. For heavy duty SSD applications the C8515 rev H is the best route if you want to stay stock... it has 3A rated components (Schottky diodes and MOSFETs) so more-or-less on a parr with Scorpius decoders. That makes me wonder have they have ever been tested side-by-side? Top Gear style? Meanwhle... I am a huge fan of the vertical loop and the pure craftwork that has gone into its production. Its fast and, IMHO, truly awesome. c
  14. I am still trying to get my head around how that Hornby C7005 came to fail. My take, if it failed when stationery is that the motor drive MOSFET must have received prior damage leaving it permanently on or partially on. Putting it stationary on the track of course applies the brake MOSFET. So a bit like taking a real car, putting into gear and applying full brake and full throttle at the same time. I just wonder if a pinned/locked guide blade contributed to earlier driving damage to the decoder? (and especially the motor MOSFET?). With the guide blade assembly unable to rotate it may jam on XLCs and certainly would struggle on R2s and hairpins. Motor overload maybe? c
  15. New circuit boards have just arrived for my next endeavour to miniaturise SSD compatible decoders. My current smallest fully functioning design, as reported earlier on this thread is 10.8mm by 5.4mm and dating back from Nov/Dec 2020. The new design, which is not yet ready for testing, has been designed to 9mm x 5mm dimensions including castellated pads for the IR LED and 8mm x 5mm dimensions without the castellated pads. So the latter design is 31% smaller than my current smallest fully functioning design. This will be well into the so-called nanoscale decoder size range. I hope to report some more progress over the next few weeks as the new boards are populated with SMD components... fine tipped tweezers at the ready c
×
×
  • Create New...