This is turning on pins 0, 1 and 3 to whatever value is in OUTA for those bits.
This is probably zero thereby forcing I/O pin #3 to zero and giving you zero readings
Rayman,
Thank you, Thank you, Thank you. I changed my Fpin to 16, and now everything works. If I wanted to still use pin 11 to measure my frequency, without affecting the 3202, how should I state the DIRA in hover?
Rayman,
Da! I new it had to be something stupid I had done, but now it makes perfect sense what it was doing.
Thanks to all that spent their time to help me with this project. Another lesson learned! I have now finalized my software and need to design and build the board for the new processor.
What I meant to type was DIRA[Fpin] := 0, to set my frequency monitoring pin, Fpin, to input. Since this never caused a problem until I added the 3202 to pins 2,3,4....never thought to look at hover. Thanks again.
Comments
Fpin is 11, my 3202 is on 2,3,4. Fpin is the pin to count the freq on with, CTRA, Frqa, Phsa that follow.
Good catch. I saw that and other considered the individual pin.
@jcfjr Make sure and check out the link in Rayman's signature. I learned a lot from Rayman's site and from his forum posts.
11 in binary is %1011
This is turning on pins 0, 1 and 3 to whatever value is in OUTA for those bits.
This is probably zero thereby forcing I/O pin #3 to zero and giving you zero readings
Thank you, Thank you, Thank you. I changed my Fpin to 16, and now everything works. If I wanted to still use pin 11 to measure my frequency, without affecting the 3202, how should I state the DIRA in hover?
or dira[11]:=1
or dira[11]~~
Da! I new it had to be something stupid I had done, but now it makes perfect sense what it was doing.
Thanks to all that spent their time to help me with this project. Another lesson learned! I have now finalized my software and need to design and build the board for the new processor.