Crystal Focus X (v10) specs, demo and discussion

[Scorpion]

thankyou

[TechoMancer]

@erv ...HELP!  :(

Stats: CFX MK3, v10.008A fw.

So I've been struggling with this for two days now.  I don't know what else to try.

I have two other boards working perfectly with v10.007F.  What I'm trying to say is that I've been successful setting up two boards (with ACCENT PIXELS) to work exactly how I want.

In short, I can't get LS2 to drive my ACCENT PIXELS in the expected manner.  Based on everything I've tried and the weird behavior I'm getting, it's like the extra\PIXIES\[content folder] isn't being accessed.  Maybe I'm setting it up wrong, based on the new firmware.

It's weird: In IDLE, the ACCENT PIXELS are just OFF. When I turn the blade on, the ACCENT PIXELS connected to LS2 light up, indicating the pixels are not defective and seemingly power and data are being transmitted via LS2.  But it's like they are part of the main (LS1) blade and they "flicker", "clash", etc. in the manner the main blade on LS1 is set up, but do not behave in the manner expected based on the contents of extra\PIXIES\0-GREEN (the folder name that works fine on my other two sabers).

As an experiment, I changed the number of ACCENT PIXELS in the config to see if the data line is transmitting correctly, and indeed, the correct number of ACCENT PIXELS light up based on the config.  I also tried several combinations of numbers between auxstrip and accentstrip (just in case) with no results.

When I turn the saber OFF, the IDLE sequence is not engaged...the pixels just turn off.


I'm using the config that came with v10.008A, with only the following alterations:

vol=90
menuvol=90

ledstrip=132 (length of my blade)
auxstrip=0 (unchanged)
tridentstrip=0 (unchanged)
accentstrip=-11 (total of my accent pixels, using a negative number to designate LS2, as I understand it)

[profile=0]
pname=green_profile

style_accents=0 (not changed, just showing in case this causing a problem)
style_pixies=0 (index in extra\PIXIES\)
style_grafx1=-1 (not changed, just showing in case this causing a problem)
style_grafx2=-1 (not changed, just showing in case this causing a problem)
style_grafx3=-1 (not changed, just showing in case this causing a problem)

Everything else in the config is unchanged.  So if it's one of the parameters not listed that's causing the problem, please let me know which one(s).

Can't figure out if I'm doing something wrong or the board is defective.

[erv]

thanks you for the super detailed (and useful) explanation and config. Please PM me a SD card zip archive (we transfer or else) so I can test that with 8A and see if I can replicate, thanks. You don't need to include every font just a few of those, along with the rest of the package. Configuration looks correct to me. Idle has been tested too on LS2 as well as other sequences.

have you enabled / included the [IDLE] in your grafx / pixies file ? have you looked at the log of the board in debug mode to see which files / sequences are triggered and where ? (index folders)

[TechoMancer]

@erv

Your quick replies are always greatly appreciated.

I totally spaced debug mode. I'll try that tonight before I trouble you with my sd package.

I'm embarrassed to say that I'm not exactly sure what you mean by "enabled" the [IDLE] in your grafx / pixies file. The [IDLE] element in the pixels.txt file is NOT commented out. The "accents" parameter is configured for 11 pixels and "many" is set to "1" for all the elements as I only have one sequence for each. The "stop" is set to "0". Everything else I left alone.

I haven't touched the GRAFX folder as all style_grafx(N) are set to "-1" in the blade profile.

Is that what you mean?

[TechoMancer]

OK, so, I'm a colossal idiot.

I went into RICE to check the debug log and noticed that the firmware that I "updated" in Crystal FX, did not take. The fw was still 10.006E.  Crystal FX has worked flawlessly for me, so I have to assume I did something wrong in the update process and it was not Crystal FX's fault.

Anyway, I updated the fw manually and everything is working fine, up to this point.

Thanx @erv

[erv]

that makes it very "logical" at the end then. I tend to prone **monitored** fw update with a log of the output thru the USB serial terminal (can be done in RICE) to see if everything went well. Depending on the fw you're upgrading from, the automatic fw update could work too including with an audio notification of the result (from a UI wav file).
Also, fw version can be obtained, like you said, via RICE or with the serial command version.
Fw update leaves a version file on the SD card too after updating, so you know what you're on. Finally, version=1 prints it and stores the version on version.txt too like the fw update does