Hi Erv - many thanks for the answer on qon/qoff - sounds perfect
Received my first 2 CFX’s and I’ve got a quick upgrade install done as it was on the bench ready to go. Before starting I wanted to say thanks - the card is fantastic
I had some issues that I thought it was worth asking about to see if they are just me being stupid (entirely possible!). Apologies in advance if I’ve missed something obvious in the manual. If you would prefer to get these via email then please let me know - but thought it might help others to see the answers here.
The first saber I have installed is an upgrade from a PRIZMv5.1 with an RGB Tri-Cree. This saber has a latching activation switch rather than a momentary one, and I wanted to keep it that way. Install went fine, and I set ‘switch=1’ (which from the manual looks right, and it worked with the PRIZM). The saber acted really weird:
The saber would not ignite unless I treated the latching activation like a momentary switch (and clicked it on and then straight off again), and then it would power down straight away (with the power off sound etc.). The behaviour wasn’t entirely consistent though - occasionally by clicking the switch on and off rapidly the saber would stay ignited - weird! With the latching switch ‘on’ the aux switch would not take the saber to the menu, but with it ‘off’ it would - so in that way it was acting correctly (apart from the fact that the blade was not ignited with the switch in the ‘on’ position - you had to move it back to ‘off’ before it would ignite and then power down). Power on force etc. are all disabled - the settings and fonts are otherwise as in the default package on the website.
I got to a workaround on this:
* I tried setting the switch=0 just in case, but that didn’t fix it.
* I thought that the ground for the power switch may not be soldered correctly. Removed and re-soldered the ground. When this didn’t work I also re-soldered the activation switch wire.
* Second thought was that this could be as a result of the induction effect from the HP LED wires - the switch wires are all nicely braided, but they do run near the LED ones. I re-wired slightly (and ensured good braiding) to give some separation when I re-soldered just in case.
* Finally I set switch=2 (momentary) - and suddenly the saber works as expected if I just treat it like a momentary switch (i.e. switch it on and then off again quickly). No glitches, no random poweroff’s, it just works fine (other than the switch having to be treated like a momentary one). If I set the parameter back to 1 then it goes back to the weird behaviour. So I have a workaround, but wondering if there is something else I’m doing wrong/missing/could try to make it behave correctly as a latching switch?
I also noticed that in some fonts the saber didn’t seem to be playing the boot sounds, and was un-responsive to some aux switch presses for blasters sporadically. I tracked this down and solved it: in the affected fonts I had alternate sound versions re-named - so for example I had a blaster.wav and a blaster_default.wav (with the old blaster sound in it - left there in case I wanted to switch back). This seemed to mean that neither of those sounds were recognised by the board - so blasters didn’t play at all (making it appear like it was not responding), neither did boot sounds. I have done no editing ‘in place’ on the card - it was all done with re-formatting and copying the entire contents. Deleting the ‘_default’ versions fixed this entirely - maybe this is an issue with the config file parsing?
Lastly I set some blade setups with a qon/qoff and it does not act like previous boards. This is an in-hilt LED setup rather than a strip, so I was expecting it to fade in for the duration (set in ms on this board). Instead the LED seems to flash on brightly, and then fade in - is it supposed to do this?
Having great fun playing with the new features, and the board is otherwise amazing so far - once again many thanks for taking the time to create this great new card, and all your amazing support in answering questions