rodw wrote: Next step is to connect each trigger pin to a real output pin. (Remember what I said about diodes). I generally would do it like this:
Code:
net zone0 <= ddraft4x2.0.trigger-0
net zone0 => hm2_7i76e.0.7i76.0.0.output-00
I got it loaded and when I jog around the 'table' (simulated only since I have nothing connected to my Mesa card yet) the pins change as I moved from section to section. That's good stuff!
Refresh my memory, should I use some LEDs on the Mesa card to prove that the outputs are firing the same as the pins in the HAL confifuration?
Also, where does the is 'net zone' code belong? Is that the example code for zone 0 only? Should it look like this when I am finished?
Code:
net zone0 <= ddraft4x2.0.trigger-0
net zone0 => hm2_7i76e.0.7i76.0.0.output-00
net zone1 <= ddraft4x2.0.trigger-1
net zone1 => hm2_7i76e.0.7i76.0.0.output-01
net zone2 <= ddraft4x2.0.trigger-2
net zone2 => hm2_7i76e.0.7i76.0.0.output-02
net zone3 <= ddraft4x2.0.trigger-3
net zone3 => hm2_7i76e.0.7i76.0.0.output-03
net zone4 <= ddraft4x2.0.trigger-4
net zone4 => hm2_7i76e.0.7i76.0.0.output-04
net zone5 <= ddraft4x2.0.trigger-5
net zone5 => hm2_7i76e.0.7i76.0.0.output-05
net zone6 <= ddraft4x2.0.trigger-6
net zone6 => hm2_7i76e.0.7i76.0.0.output-06
net zone7 <= ddraft4x2.0.trigger-7
net zone7 => hm2_7i76e.0.7i76.0.0.output-07
