Author Topic: Stuck on Black Forest project  (Read 502 times)

Cornholio

  • Diode Destroyer
  • *
  • Posts: 14
    • View Profile
Stuck on Black Forest project
« on: March 05, 2016, 11:35:20 PM »
http://tagboardeffects.blogspot.com/2014/04/black-arts-toneworks-black-forest.html

I'm on the home stretch of this one and I'm kind of lost as to how the daughter board for the rotary is wired up in relation to the main board. Would I be right in that SW A from the board goes to SW A of the rotary... then Input on the daughter board goes to the middle lug of the footswitch? Yet the graphic says "Input to SW A" which throws me for a :-\

Any help with this one is appreciated!
« Last Edit: March 06, 2016, 01:02:06 PM by Cornholio »

nocentelli

  • Diode Destroyer
  • *
  • Posts: 14
    • View Profile
Re: Stuck on Black Forest project
« Reply #1 on: March 06, 2016, 01:57:56 PM »
The input to the daughter needs to come from whichever lug you use as the "fx send" from a 3PDT true bypass footswitch: For me this would usually be the top left lug, but it depends how you wire your true bypass footswitch (there are several ways, some include grounding the fx input or output in bypass, but are essentially the same switching arrangement). The rest of the diagram makes perfect sense and is correct.
« Last Edit: March 06, 2016, 01:59:58 PM by nocentelli »

Cornholio

  • Diode Destroyer
  • *
  • Posts: 14
    • View Profile
Re: Stuck on Black Forest project
« Reply #2 on: March 08, 2016, 05:39:49 PM »
The input to the daughter needs to come from whichever lug you use as the "fx send" from a 3PDT true bypass footswitch: For me this would usually be the top left lug, but it depends how you wire your true bypass footswitch (there are several ways, some include grounding the fx input or output in bypass, but are essentially the same switching arrangement). The rest of the diagram makes perfect sense and is correct.

Thanks! I have this thing boxed and working now and the rotary switch is working perfect!! I will update the thread on that site with the fix because it seems a couple people had that problem also, thanks again! - John