robert_allen
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Gallery
Posts posted by robert_allen
-
-
AndyP.
What is the revision number of your hardware (it is viewable in the APP)? 1.0.1
What version of the software are you using? 2.2.2 (33)
What revision are the digital chips you are using (likely G or H)? H
Rev G chips have a large capacitor mounted to the PCB (yellow/blue packaging), Rev H have all nice small surface mounted components (grey packaging).
Could you also upload a picture of where the powerbase is located on the track?
-
Interesting...
So it looks like three options...
1/ contact Scalextric custimer services to ask for advice quoting how temporarily lengthening the blade corrects the problem... but causes other problems...
2/ re-position the IR LED 10mm behind the blade assembly by drilling a 3mm hole and soldering the LED onto a flying lead.
3/ I wonder if a slot.it blade, perhaps a SICH10, which has a longer tail end... might solve the problem... if it fits?
C
I have sent an enquiry to Customer Service and will wait for a response. Thanks again for all your suggestions.
I'm not keen on drilling a new hole and refitting the electronics. I don't feel I should have to do this with a newley released car. Should work right out of the box after installing a chip.
-
photos will be useful... but I personally believe the black pvc tape test will nail it.
Might you give this a try too?
C
Hi. I tried the black electrical tape on the guide. I added an extra 5mm to the original length of the guide making the distance from the end of the modified guide to the LED approximately 15mm. It counted laps perfectly. No missed laps at all. The only problem now is the the tape added enough width to the guide that it now gets stuck at some sections of the track. :)
-
Could you provide us with more information please?
What is the revision number of your hardware (it is viewable in the APP)?
What version of the software are you using?
What revision are the digital chips you are using (likely G or H)?
Rev G chips have a large capacitor mounted to the PCB (yellow/blue packaging), Rev H have all nice small surface mounted components (grey packaging).
Could you also upload a picture of where the powerbase is located on the track?
There could be a combination of issues that have created a "perfect storm" here...
Thanks
I'll take some pictures tommorow.
-
OK...
Final question(s): Have you tried the chips in other cars to rule out there isn't a problem with the chips?
Have you tested the mods that Dr_C mentioned? (lengthening the guide blade with black tape)
Also, can you visually inspect if the LED is seated low in in the car? Compare it to the Protoypes that work.
It could be you got a bad batch where the LEDs are not seated properly...
1: The chips were actually the first thing I tried. Made no difference.
2: haven't tried the tape thing yet. Will try tommorow.
3: LED's are seated the same as the Protoypes.
-
Ok.
1: I just gave the cars a try in Analog mode and the cars count laps correctly.
2: The counting problem is with both Pace cars and human controlled cars in Digital mode.
-
To function correctly with the standard lap sensors fitted into the ARC PRO there is a critical distance between blade and centre line of the IR LED that is important...
The distance between the back of the blade and the centre of the IR LED needs to be less than approx 19mm.
Also, this measurement assumes the IR LED is more rear-ward than the blade.
From the photos I suspect that the Monto Carlo does not meet, or is marginal, with respect to this distance requirement. This would explain why laps are being missed.
It would be helpful if Scalextric could check compatibily of the Monto Carlos with a DPR module fitted with the ARC PRO please? If not compatible using a DPR module then drilling 3mm hole and repositioning the IR LED may be necessary...
C
I just measured the distance between the back of the guide flag to the middle of the IR LED. The distance is 22.35 mm.
Doesn't Scalextric test this kind of thing?
-
DR_C
Here's a pic of 2 cars together. The Monte Carlo is on the left and a Daytona Prototype on the right.
/media/tinymce_upload/a7aac84052889f4a8d49bb22ee625f93.JPG
-
Has anyone else had problems the new Monte Carlo's not counting laps with the Arc Air Pro? I have 4 new Monte Carlo's with 4 brand new chips in each car and they all have a problem with counting laps. I've tried several other types of cars such as GT3's and Daytona Prototypes and all other cars count correctly. For whatever reason the Monte Carlo's will skip several laps before counting a lap. It happens with the the Official App and the 3rd party app as well.
Monte Carlo's not counting laps.
in ARC - App Race Control
Posted
Ok. Quick update here.
I put one of the CH10 guides on one of the Monte's, pushed the car through the base at varying speeds as I didn't want to rewire the lead wire ends and it didn't make a difference. So I then tried Andy P's suggestion (though it took a few minutes to figure out what he was telling me..."orange" lol. ) and put a CH07 wood track guide on the Monte. The guide needed to be sanded down a little bit for a smooth ride. I then did the same thing, pushing the car through at varying speeds. At first it didn't count laps correctly but then it started to be consistent and counted laps flawlessley no matter what speed I pushed it through. Ok, great. Problem solved but the guide would still need some massaging as it was tight in the holder and wouldn't turn smoothly. I didn't feel making the modofication to the CH07 guide tonight so I decided to run some other cars just to have some fun. I ran a Revoslot Viper around the track and no problems. I ran several other Scalextric GT cars around and they all performed great. So just for fun I grabbed another Monte Carlo (with digital chip) and ran it around and low and behold, it was counting laps perfectl6y. What???? So I set up a practice race to do 50 laps and it counted every lap. I grabbed another Monte, this one was analog and it also counted 50 perfect laps.
I don't know what to tell you. 😮