Just a question to help me understand, i have motor blade using CH1LED but what does this mean does the number related to led number/ data pad?
They’re somewhat confusingly named.
They correspond to the Red, Green, and Blue channels. ProffieOS has a somewhat in-depth way of defining “LEDs” for the purposes of driving them, and CH1LED, CH2LED, and CH3LED serve as basic/“pure” definitions for being triggered by the respective aforementioned color channels.
What this means in practice is that a bladestyle that uses red as its primary color will active CH1LED “perfectly” (100% color means 100% power, as you’d expect for simple/ideal LED setups and useful for driving simple things like motors). Contrast this with the other LED definitions which impose limits on drive strength depending on the configuration, as well as respond to the colors differently.
You may be interested in this page:
Thanks i will have a read
When my motor is set to ch1led it generates constant clash type effects when on
But if i set it to ch3led ot behaves normally
Any logic to this?
That’ll just depend on your bladestyles. I’m not sure what normal means to you/how you’re using the motor.
If you’re using a motor this way, you should pick a channel, and then make it so you only use the color for that channel in the bladestyle (Red, Green, Blue) or White (which will trigger all channels equally, which is a little more generic, and functionally identical). The behavior you describe means there’s multiple colors in play or a color that uses multiple channels (e.g. Purple)
Perhaps post the bladestyle you’re using and we can see what’s going on. (As well as describing your intent).
Will post it tomorrow
By normal i mean the motor spins without generating constant clash type sound effects.
If i set to ch1led when the motor is spinning there is constant clash type sound effects being generated
If I had to guess that means the bladestyle is driving the motor (more?) erratically (perhaps because of a flickering style made for leds) on that channel (if the color being used drives red more intense than blue), and that’s causing the board to detect that motor movement as false clashes. Kind of a feedback loop sort of situation.
That’d still most probably be a bladestyle issue. I’ll defer suggestions about adjusting clash threshold until the bladestyle is sorted.
Heres the style code for motor
StylePtr<InOutHelper<White,50,50>>(),
Blade config
SimpleBladePtr<CH1LED, NoLED, NoLED, NoLED, bladePowerPin6, -1, -1, -1>()
This produces constant clash effects
SimpleBladePtr<CH3LED, NoLED, NoLED, NoLED, bladePowerPin6, -1, -1, -1>()
This doesnt, it spins silent
Hmm, well in theory that shouldn’t make a difference, but it’s possible my knowledge is lacking.
I would need @profezzorn to comment. If the wiring’s not changing at all that doesn’t seem like it should make a difference… (and of course, the bladestyle looks perfectly fine…)
That makes no sense, as CH1LED and CH3LED should produce exactly the same output for White.
You can use ‘monitor pwm’ in the serial monitor to see what output values it is actually computing for your motor. (Note that the monitor command is not available if you have the DISABLE_DIAGNOSTIC_COMMANDS define.)