Planning for Prop-1 FC-4 AP-8 and COW/300

[condolaw]

I am attempting to PLAN a project, and am asking for suggestions or comments BEFORE I attempt any code. . .  could you review the "PLAN" and let me know of potential problems . . . [attached pdf]
Thanks for any comments good or bad!
John

[BigRez]

I like the format of your plan but I think it could use a couple of other columns/items.  Perhaps duration and another would be audio file name.

How does the AP-8 get triggered?  Does it connect to the prop-1?

One thing that isn't clear to me... Looks like you have more than eight sounds being played.  The AP-8 says it can play eight sounds totaling 60 seconds.  (The AP-8 also is currently out-of-stock, so not sure if this is also an issue.)

[condolaw]

OOPS  :-\ . . . Sorry. .  I should have given an "Overview" . . .
PLEASE don't take my comments as "fact" . . . I'm workin' through this. . .

This is a basic 4-bar prop where a pneumatic cylinder lifts a witch out-and-up-and-above the TOTs with a group of munchkins around the witch.  At the end, a second cylinder lifts the arm and broom.
My goal is to time actions to the song/music loosely based on "Defying Gravity" from Wicked.
I have made ONE single song that is less than 60 seconds - so taking up all the AP-8 segments as one "segment" (I have an available AP-8 . . thanks for that note :-*)
I planned for the Prop-1 to trigger the AP-8 and the COW.
The highlighted phrases are where I want the "actions", so I understand that I'll have to put in appropriately timed "pauses" (duration) to have each action occur timely with the song

I am using the COW board just for the eyes at this time (no room left on the prop-1 - and I have a COW on hand) but **IF** time would permit, I would love to use the COW board to add jaw movement, though I would need another AP-8 for the jaw since the AP-8 output is mono . (?).

Thanks for looking at it and your questions!

[JonnyMac]

We always suggest using P7 for EFX-TEK serial devices -- this makes hardware connections easier.

Also, are you using the FC-4 in digital mode or are you planning fades in the program?

[BigRez]

Certainly sounds like it'll be an awsome prop.

I don't see where the FC-4 and ap-8 connect to the prop-1.  Assume the FC-4 and AP-8 would be daisy-chained, as Jon suggests it should connect at pin7.  You may be able to combine things, like the fan and back-light to free up a prop-1 pin.  (looks like the fan and backlight come on together - but then you'd need to get a 110vac fan).

[condolaw]

DOH! . .  I should know better than to do things from (what used to be) memory!
I should have had the PIR/Trigger on 6
and the AP8 & FC4 on 7 (serial) (THANK YOU)
bigrez. . . THANKS. . . looks like I'll have to combine the fan (AC110) with backlight on FC-4-3
JON: plan originally was that FC-4 would be digital on 1,2&4 and a fade on 3. . .  but because of my lack of ability to count. . . will move the fan to FC4#3 with the backlight and therefore all will be digital . .

SO looks like it should be:
Prop-1 -
0   Relay or Pin/BroomLights
1   Fogger
2   Solenoid-Raise
3   Cowlacious Board
4   Solenoid-Broom
5   LED-FACELIGHT/PIN
6   PIR (TRIGGER)
7   AP-8 & FC-4 (serial chain)

FC-4
1   Lights1
2   Lights2
3   BackLight & Fan
4   RopeLight

------
at this point. . .  does it appear that my connections and plan should be enough to attempt a program? (please don't offer one yet . . . I want some trial and error on my part, first - unless you have cautions. . .)

any COMMENTS / SUGGESTIONS are welcome . . .
THANKS

[JonnyMac]

I like putting "smart" accessory devices at the upper end of the outputs:

Prop-1 -
0   Relay or Pin/BroomLights
1   LED-FACELIGHT/PIN
2   Fogger
3   Solenoid-Raise
4   Solenoid-Broom
5   PIR (TRIGGER)
6   Cowlacious Board
7   AP-8 & FC-4 (serial chain)

Start writing code -- that's where the fun is!  Of course, if you get stuck we're happy to help.

[condolaw]

Let the fun begin!  -  THANK YOU  :-* !!

[condolaw]

This Prop-1 "FUN" has turned to theoretical . . . frustration hasn't hit (yet).

After several "DOH" moments and researching the online dox and forum (that part is ALWAYS fun :)) . . . I still have several "EEPROM fulls" and "Limit of 16 GOSUBs EXCEEDED" (the EXCEEDED gosubs are my fault, I tried to save space, but still couldn't count! ::) ). . .  and I still have "principal" actions to include . . .  I know the "coffee" cup is full, but am trying to get the flavor more robust! (reference to http://www.efx-tek.com/php/smf/index.php?topic=301.0).

I have read the controlling prop-1s at http://www.efx-tek.com/php/smf/index.php?topic=120.msg446;topicseen#msg446 but can't see how I will save EEPROM space for this app. . .  ???

ERGO the QUESTION:  Can TWO prop-1's be configured to control a single FC-4?  (either hard-wired or by serial communication)?  If hardwired - the prop-1s would not be sending competing signals. . .  eg. .  after the MASTER prop-1 is "full" (or exceeded gosubs) the slave would "continue" with the program . . . my ignorant thinking is that the MASTER prop-1 would turn simply turn ON (OUTx) the SLAVE prop-1 (by power - NOT serial comm) and the slave would have a timed "PAUSE" before continuing the program . . .

Am I simply a stingy idiot for not getting a Prop-SX or are two Prop-1s a possibility (since I have an available Prop-1)?   ???

ANY comments are welcome . . . no offense taken. .

[JonnyMac]

Okay, technically, since we use an "open" output mode you could connect two Prop-1s to the same FC-4, but one could stomp on the other's transmission and whack the communications to the FC-4.  You'd have to be very careful about program timing and making sure that both Prop-1s are in sync.

If you're going to do a pass-off from one Prop-1 to the other I suggest using a pin on the first (P5 in output mode) to send an active-high signal to the second (using P6 in input mode) -- will look just like a trigger input.

The Prop-1 is a small controller: small IO count, small memory -- sometimes our goals exceed the IO or the program space and we have to bump up.  This is why we make the Prop-2 and Prop-SX.

[livinlowe]

Try posting your code, perhaps we can see something that you can't.