Issue with “id” command in the current ProffieOS

[ShtokyD]

“id” command is not printing out response to serial. Only prints out the ID value to USB.

[NoSloppy]

id has been deprecated. Use scanid instead.

[ShtokyD]

Does it also give a correct ID value?

[baldusi]

May I suggest this thread. Will probably do some testing on 8.1 during the weekend on a V3.9.
But I’ve found weird readings when the MOSFETs are shared, even on different datalines. But I want to test again for that case. Again, in that thread used an ECO V2, which prevents any good BladeID, and then a V3 in V4 configuration with a V2.2 with a 33k resistor between Data 1 and 3.3V. So now I would like to test on a V3.9 because it has two pins jumped, and thus I don’t know how accurate it is.
On a totally different note, love your new 69 pixel plugs. As soon as I solve some issues with work I will contact to acquire a couple.

ProffieOS 7.5 Beta Testing Blade ID

Ok, I’m gonna go with the first hilt: A Proffie v2.2 with a 22k pullup resistor between Data 1 and 3.3V. It has a Shtok ECO V2. So it shared the Data1 with the illuminated PCB which mirror the blade data. Test1: #define BLADE_ID_CLASS ExternalPullupBladeID<bladeIdentifyPin, 22000> #define ENABLE_POWER_FOR_ID PowerPINS<bladePowerPin2, bladePowerPin3> #define BLADE_ID_SCAN_MILLIS 3000 #define BLADE_ID_TIMES 1 8 scans of No Blade. 8 scans of a 47k bladeplug 8 scans of a 6.8k blade 8 scans of No Blade with the Blade turned on 8 scans of the 47k bladeplug with the blade turned on. Ohms No Blade No Blade 47k 47k 6.8k 8.3k Blade turned off on turned off on turned off turned off Average 11,671.22 11,953.67 9,332.42 9,547.05 4,394.86 5,062.49 STDDEV 37.66 121.44 23.29 71.47 16.53 23.63 11,674.14 11,876.69 9,332.41 9,551.82 4,379.39 5,044.42 11,623.88 11,825.83 9,332.41 9,684.95 4,410.32 5,076.92 11,674.14 11,825.83 9,332.41 9,463.69 4,410.32 5,044.42 11,674.14 11,876.69 9,288.89 9,463.69 4,410.32 5,044.42 11,674.14 11,876.69 9,376.04 9,507.69 4,379.39 5,109.51 11,724.55 11,978.88 9,332.41 9,551.82 4,410.32 5,044.42 11,674.14 12,081.70 9,332.41 9,507.69 4,379.39 5,076.92 11,674.14 11,927.71 9,332.41 9,596.07 4,379.39 5,044.42 11,623.88 12,133.33 9,596.07 5,076.92 11,674.14 12,133.33 11,623.88 11,674.14 11,674.14 11,674.14 11,674.14 11,623.88 11,775.11 Test2: #define BLADE_ID_CLASS ExternalPullupBladeID<bladeIdentifyPin, 22000> #define ENABLE_POWER_FOR_ID PowerPINS<bladePowerPin2, bladePowerPin3> #define BLADE_ID_SCAN_MILLIS 3000 #define BLADE_ID_TIMES 20 8 scans of No Blade. 8 scans of a 47k bladeplug 8 scans of a 6.8k blade 8 scans of No Blade with the Blade turned on 8 scans of the 47k bladeplug with the blade turned on. Ohms No Blade 47k 6.8k 8.3k Blade turned off on turned off on turned off turned off Average 11,732.90 11,961.90 9,364.59 9,506.36 4,400.85 5,043.82 STDDEV 16.46 103.75 5.31 22.05 3.55 4.24 11742.25 11813.19 9369.5 9468.13 4405.68 5044.43 11757.43 11833.54 9369.51 9536.54 4396.41 5037.94 11752.37 11881.88 9362.95 9490.21 4405.7 5041.19 11739.72 11920.18 9371.68 9494.68 4397.95 5039.57 11752.36 11915.27 9365.14 9510.02 4397.95 5049.31 11744.77 11958.66 9360.78 9501.15 4402.59 5042.8 11752.36 11966.48 9356.41 9499.04 4401.05 5046.06 11737.2 11989.39 9360.77 9532.08 4399.5 5049.29 11729.63 1…

[profezzorn]

This is very confusing, for several reasons:

• Like NoSloppy pointed out, use “scanid” instead of “id”.
• Output is normally directed to the terminal that issued the command, so if you run “scanid” in SerialMonitor, you should see the ID there. If you run it from a serial connection, the output should come out there.
• Asynchronous output, like the battery monitor is normally printed to the USB Serial monitor, and not printed to the serial port. You can change which terminal receives the async messages with the “make_default_console” command.
• There is currently no command to turn off the battery level that is printed out by the battery monitor every 20 (other than modifying the code of course).

[NoSloppy]

@profezzorn

Like NoSloppy pointed out, use “scanid” instead of “id”.

@ShtokyD

Different ID number after “id” and “scanid” commands

I should probably just remove the “id” command. I added that early on for debugging and it doesn’t really do anything helpful. Basically it tries to do the blade id() without making sure that the blade is in the right state (powered, but off) which doesn’t really work. “scanid” does all of this correctly by turning the saber off, undoing all the current blade setup, powering the blade and then calculating the ID. After that, it sets everything up again, just like a blade detect event does.

[ShtokyD]

So this is the scanid command, but I don’t see the ID value in response here:

scanid
-+=BEGIN_OUTPUT=+-
blade = 0
WS2811 Blade with 136 leds.
WS2811 Blade with 5 leds.
Simple Blade
Scanning sound font: Ahsoka 20 test done
Activating polyphonic font.
Activating SmoothSwing V2
Accent Swings Enabled.
Polyphonic swings: 16
Monophonic swings: 0
Accent Slashes NOT Detected: 
-+=END_OUTPUT=+-

[ShtokyD]

“scanid” command doesn’t print anything to the serial bluetooth.

[profezzorn]

What version of ProffieOS? I think this might already be fixed in 8.x (unless your log level is too low.)

[ShtokyD]

ProffieOS v7.15

[profezzorn]

Please try 8.x and see if it fixes the problem.

[ShtokyD]

nope, same as before:

scanid
-+=BEGIN_OUTPUT=+-
WS2811 Blade with 16 leds.
WS2811 Blade with 5 leds.
Simple Blade
Scanning sound font: 6
 done
Activating polyphonic font.
Activating SmoothSwing V2
Accent Swings Enabled.
Polyphonic swings: 16
Monophonic swings: 0
Accent Slashes NOT Detected: 
-+=END_OUTPUT=+-

[NoSloppy]

Maybe because the printout was moved to STATUS level?

profezzorn/ProffieOS/blob/14647a342bee30b84f0384884d106fad8fadf2cb/props/prop_base.h#L548

Does that need to use STDOUT instead?
STDOUT << "BLADE ID: " << ret << "\n";

[profezzorn]

@NoSloppy

Maybe because the printout was moved to STATUS level?

ProffieOS/props/prop_base.h at 14647a342bee30b84f0384884d106fad8fadf2cb · profezzorn/ProffieOS · GitHub

Yes, that is the reason. PVLOG is not really meant for essential output, and is always printed to the “default output”, which is usually USB serial, not Serial3 (where BT usually connects).

I guess the question is: Is this essential output? @ShtokyD what are you using this value for?

[ShtokyD]

I have a function in my Forcesync bluetooth app to show the current Blade ID value, it’s useful for users.

[ShtokyD]

Yes, changing it to STDOUT fixed this issue and now blade ID prints to bluetooth serial