hmmm, good idea but didn't work.

That was it, from my side. Sorry, that I couldn't help any further.

I hope you can find a way to fix it.

Thank you so much. I already am talking to Matt. Maybe it finds a solution. If so, I will post it here.

Hi,

This issue was caused by having old FTDI console drivers installed on the system.

The latest versions of Lightworks no longer require additional drivers to be installed for the console, so the fact they were present on the system was causing the console to not be recognised.

JanGoossen successfully removed the old FTDI drivers from his system and the console pinged back to life.

I hope this helps other users but I suspect this is a very niche issue.

Matt

Indeed,
Thanks Matt for reminding me to report the way I solved the issue was solved.
I looked for a file with FTDI in its name and found FTDIKext.kext
After removing the file and a reboot (I don't know if it was needed, but did it anyway) The console just got back again to its normal behavior.
All of this thanks to the magnificent help I got from Lightworks. Thank you so much.