News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

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

+-Site Stats

Members
Total Members: 16427
Latest: digilabpg
New This Month: 21
New This Week: 2
New Today: 0
Stats
Total Posts: 132342
Total Topics: 16406
Most Online Today: 126
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 1
Guests: 83
Total: 84

Vixen Events and FPP

Started by lrhorer, November 07, 2021, 02:43:24 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lrhorer

OK, I am using GPIO pins to trigger events in FPP.  This seems to be working, but not quite the way I would like.  I am not certain if perhaps it can work the way I want if I did something a little differently.

First, the steps I am following:

I create main sequences and save them as fseq files.  Then I create brief event sequences and save them as fseq files under the same profile.  I load the sequences onto the Raspberry Pi.  I set the main sequences to play at the desired times.  I also set up the FPP GPIO routine to run the desired fseq file on the leading edge trigger and to stop on the trailing edge.

This causes the event to send out its data when the pin is asserted and to stop when the pin is reset or the sequence ends.  So far, so good.  The problem is, the event blanks the rest of the lights.  This is not what I want.  What I really want is to have the event sequence override only the lights in the channels with active effects in them and continue to play all the other data from the main sequence.  I do know that Vixen can purportedly produce eseq files instead of fseq files, but I am unsure of how the results will be handled by Vixen and then subsequently by FPP.  Can anyone lend some insight?

TomsLEDs

Did you ever get this figured out? I ned to do something similar. Do you have the input pin to sense the high constatly or is it set to toggle each time a high is sent? A latching toggle would make sense.

Poporacer

Quote from: TomsLEDs on March 13, 2024, 09:54:28 AMI ned to do something similar
This is thread is over 2 years old and many things have changed since then. In the future, you might want to start a new post so that things don't get convoluted.

You might want to explain what this "similar" method is that you are trying to achieve,

But to answer the question, fseq files are global and affects all models, so if you want to affect only certain models, then you need to use eseq files and configure it accordingly. I don't know the Vixen aspect of that though.

Quote from: TomsLEDs on March 13, 2024, 09:54:28 AMDo you have the input pin to sense the high constatly or is it set to toggle each time a high is sent?
The GPIO pins in FPP are constantly monitoring the state of the pins. Each time a button is pressed/released, it is processing the appropriate triggers.

Quote from: TomsLEDs on March 13, 2024, 09:54:28 AMA latching toggle would make sense
I don't think that is how GPIO pins are inherently designed.
If to err is human, I am more human than most people.

Support FPP

+- Recent Topics

configuration by morrydavis
April 23, 2024, 04:34:20 PM

FP 7.5 Crash after approximately 440 loads of the same Playlist, memory full by CaptainMurdoch
April 23, 2024, 03:48:12 PM

F32v5 Release Date by JonD
April 23, 2024, 09:14:57 AM

MQTT with Home Assistant, model control only lights up some pixels. by CaptainMurdoch
April 22, 2024, 01:30:45 PM

Looking for a way to "fast forward" a video playlist by Jayl
April 18, 2024, 03:20:31 PM

P9-28 and P9-29 not work by windaube
April 15, 2024, 03:40:34 PM

Resetting or Removing FPP Password (with Windows) by greenreader9
April 14, 2024, 06:21:46 PM

Enclosure for Video Projectors by Scott
April 14, 2024, 12:00:50 PM

Born in the USA by Xmas!
April 13, 2024, 03:25:16 PM

1200w HP Power Supplies by MikeKrebs
April 12, 2024, 08:53:19 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod