Crystal Focus X (v10) specs, demo and discussion

[erv]

not there yet, in testing

[TechoMancer]

not there yet, in testing

Cool.  Thanx for the quick reply.

There's a YT vid from late october showing the accent sequencing.  Is that in one of these FWs?

[erv]

yes, changelog of 6F. But things change rapidly. Coming soon

[TechoMancer]

yes, changelog of 6F. But things change rapidly. Coming soon

Erv, man, I want to thank you so much for all your hard work.

I suffer from a health condition that limits my ability to leave the house.  This saber building hobby, and tinkering with the CF board, brings a level of distraction that alleviates my boredom. 

[TechoMancer]

POSTED IN WRONG THREAD.

SOLVED.

[TechoMancer]

Hello fellow smiths.

Yesterday I upgraded the firmware from 6B to 7D via the Crystal FX desktop program (as I've done several times in the past).  However, after completing the upgrade and rebooting the board, I could not connect to Crystal FX again.  Upon going to the Device Manager, I see that the board is now reading "TinyUSB Serial" with a driver issue.

I tried disabling Driver Signature, but that's not helping.

The saber works fine; it's not bricked.  But what happened to the drivers?

This is on a Win7 x64 laptop (yes Erv, still...  ).  Any help would be appreciated.

[TechoMancer]

Well, I think that now I DID brink the board.

I went to my Win10 Gaming PC and the board was recognized immediately.

I was using Crystal FX desktop program to update the boot loader.  I was watching the YouTube video by CrystalFocus and following the instructions step by step.

I used the serial command UNLOCK and everything seemed to be going fine, but when the update started, it hung.  The last console message was "Do not in" (I'm assuming it was going to say "Do not interrupt power" or something like that).  I let it go for like 30 mins and I got no other messages.  The video showed the update taking like 1 second, so obviously, something went wrong.  The battery on the saber was at 97%. 

I know the instructions say something like "You'll have to send it in to have it reprogramed", but am I supposed to unsolder everything to send it in?

I have a couple of programmers.  Can I reload the bootloader myself?   

Thanx

[erv]

check if you can still go in bootloader mode with the switches.
you can't reflash the bootloader yourself
as for the driver itself, I don't know. The USB stack changed since like 6.X (would need the changelog to find out when exactly) but it's still a CDC serial port so win 10 should have no issues with that

for your bootloader crash, do you have a OLED and did you have the screen savers enabled ?

[TechoMancer]

check if you can still go in bootloader mode with the switches.
you can't reflash the bootloader yourself
as for the driver itself, I don't know. The USB stack changed since like 6.X (would need the changelog to find out when exactly) but it's still a CDC serial port so win 10 should have no issues with that

for your bootloader crash, do you have a OLED and did you have the screen savers enabled ?

Thanx for the quick reply Erv.  Don't worry about the drivers.  I'm just gonna use my desktop from now on.  It has Win10 and gives me no issues.

I do have an OLED connected and, yes, I had screensaver enabled.

I didn't try going to bootloader with the switches.  I wanted to get some help/instructions to see if the board was still "salvageable" before trying things and making matters worse.

I'm going to hold off on trying to get to the bootloader with the switches until you reply to my situation with having the screensaver enabled, in case there's something else I need to do, before proceeding.

Thanx

[erv]

keep me posted, the bootloader might have been wiped out. I'm going to add that you should disable screen savers and actually sleep / deep sleep as well, good points

[TechoMancer]

Unfortunately, I think it's bricked.  I power the board and nothing happens; not even blinking led.  Can't get it to boot with the switches and Windows does not recognize the board.

I tried:

disabled the screen saver...nothing.
a fresh SD card with only the default package (screen saver disabled)...nothing. 
putting the fw.dat file on the SD card...nothing. 
JUST IN CASE, I renamed it to update_fw.dat and tried booting...nothing. 
I put the boot.dat on the SD card with both fw.dat and update_fw.dat...nothing.

Did I miss anything?

[erv]

go in bootloader mode with the switches, see if it mounts on the USB port, and do a monitored (serial port) update of the fw as described in the manual

[TechoMancer]

So, I haven't put much thought into this, so it might a bad idea or not even be possible (I know it would cause extra battery drain):

Could there be an option to play, or not play, a sound while the board is in idle mode?  Possibly at a selectable interval, e.g. ever X seconds?

I think it would be cool for the saber to give off sounds while some lights are flashing or something (e.g., MB chassis with the cycling lights).

[Scorpion]

So didn’t even know my cfx saber had drag fx
But apparently it does,
Unless I’m doing something wrong what exactly is the gesture for it?

[erv]

It does. For like 2 years. The quick interaction guide will tell you pretty much everything

https://www.plecterlabs.com/shop/article_info.php?articles_id=125

So didn’t even know my cfx saber had drag fx
But apparently it does,
Unless I’m doing something wrong what exactly is the gesture for it?