LATEST RELEASE:  FPP 6.1 - Download from here -



Welcome, Guest.
Please login or register.
Forgot your password?

+-Site Stats

Total Members: 15476
Latest: mergeink
New This Month: 98
New This Week: 13
New Today: 8
Total Posts: 126888
Total Topics: 15559
Most Online Today: 105
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 7
Guests: 59
Total: 66

LedTriks/Vixen/Xlights Nutcracker/fseq question

Started by beatlerat, April 13, 2014, 05:41:17 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.




Thanks for posting and sharing Chris.  Hope to see you back in the hobby at some point.



After a bit of playing around today I managed to get LTC (the crude but effective windows program that drives a triksc/Ledtriks display) ported across to the Pi.

(Turns out there is now a freebasic compiler for ARM/Raspian....)

There are a couple of additional dependencies that have to be loaded to get the compiled code to run (it needs a couple of extra libraries) - and I'm not sure whether the overhead of running this on the Pi will get in the way of FPP. But with some minor changes to the LTC code I now have a stock Pi talking via a usb-422 convertor to my Ledtriks setup. So far so good (without a long test!)

Biggest problem at present is the FTDI USB adaptor - it seems to work fine on the stock image but creates an instant lockup as soon as its opened on the FPP image. Looking at the RPi forums it looks like there's been a bit of trouble with the USB interface over time - But I'm a newbie to Linux and I don't know whether there are missing bits in the FPP build that have since been cleaned up on the stock image.... or if its something else I don't understand!

So the bottom line is : promising start - but not quite there yet!



Quote from: TimW on May 11, 2014, 08:39:42 AM
Biggest problem at present is the FTDI USB adaptor - it seems to work fine on the stock image but creates an instant lockup as soon as its opened on the FPP image.

Sounds like you are making good progress... :)

If you are running the stock v0.2.0 FPP SD image then there is an issue with the USB kernel driver in that version.  The new v0.3.0 image that will be coming out has a newer kernel and works fine with the USB serial adapters I have connected to it so far.  If you want to test on your v0.2.0 image, you can run an update to get the newer kernel to test, but it will break rasclock support if you have a rasclock.  The new FPP SD image will include the rasclock module for the newer kernel.

It sounds like what you are working on would make a great 'plugin' using the new system that Materdaddy wrote which will be in v0.3.0 to implement the FMT212R support he has worked on.  I have an old LED sign that uses the AlphaSign protocol that I wrote a Perl module for which I plan on creating a plugin for as well, but that will be after v0.3.0.  I think there are lots of things we can do with plugins now that the framework is in place, we could look at firing plugins to display RDS information gleaned from ID3 tag info, running plugin code as part of a playlist or event, etc..


Thanks Captain

I updated the kernel - USB is back!

Will keep testing and await 0.3.0....



Evening Tim. Great news. Thanks.

Sent from my SM-N9005 using Tapatalk

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod