It was indeed that - I remember finding it when I first started using BladeID. It was one of the things that led me to start experimenting with manual array switching, as it meant you wouldn’t need to leave BLADEID_SCAN_MILLIS running all the time. Though as you say, a define to shut it off is another solution.
This was the thread where I know it came up, but there might be others as well:
OK, I’ve been running some tests, and with a nudge from PeaceKeepersArmoury to confirm I’m on the right track (thanks PKA), I think I’ve got it working apart from one small bug, though I think that bug can be coded around with a blade style if needs be. More on that shortly.
The OS used is the Github Master.
But I’ll run through the MO…
The config was built with three blade arrays which were, in config order:
Complete Hilt
Chassis Only
Complete Hilt with Charge Plug
The config I used is below, and the hilt was wired, and config set with the
#define BLADE_ID_CLASS BridgedPullupBladeID<bladeIdentifyPin, 9>
and Data 1 bridged to TX.
The blade connector in the chassis does NOT have a resistor between Data and Negative, but DOES have the Blade Detect pin wired to Aux2,Button3 which has been added to the config. The Blade connector in the main blade emitter also does NOT have a data/neg resistor. The only resistor used in the whole shebang is the charge plug which has a 22k resistor between data and neg.
With the board connected to a computer but powered by the battery, I got the following scanid numbers:
Complete Hilt 666750.56
Chassis Only 1000671744.00
Complete Hilt with Charge Plug 22642.32
For ease of determining which array I was on, I set the accent LEDs as follows:
Complete Hilt Blinking White (though looks blue reflecting on the tape on the video)
Chassis Only Blinking Red/Green
Complete Hilt with Charge Plug Single green pip every five seconds
The video below shows it all as it stands.
You can see that essentially it all works. The only bug is the fact that the crystal and plasma gate seem to pip, presumably in time with the constant Blade ID monitoring. Since I’m using the BlackPower add on for the charge plug, I’m guessing it might be possible to code it so those FETs stay powered but don’t display anything, which I have a hunch might fix it. But I haven’t got as far as making that work yet, and it does feel like a workaround rather than a fix.
I thought it might be caused by having the crystal blade style use InOutHelper, but removing that style didn’t make any difference.
Anyway here’s the video:
[IMG 7182]
And here’s the config:
Hope they’re useful.
2 Likes