The Openaccess 3.0 shield is kinda old, but it’s actually pretty good. I have quite a bit of experience using it so I think I’ll talk about some of the oddities in it here today. I’m going to start with a silkscreen nit pick and segway into some other things. You may think I spelled ‘segue’ wrong, but what you can’t see is that I’m balanced on two wheels right now.
Ignoring, for the moment, the unpopulated relays and screw terminals take a look at R47, 71, 72, and 73. Those all appear correct and well tacked down. I will also not that nowhere on this board do silkscreen deliniators for components reside at a 90* angle from the components themselves. Nowhere except here. The yellow and black wires connect to the battery voltage input of this board. The entire row there is for alarm sensors (which also go into analog pins) but the last one is set up with a voltage divider so it can be connected to the battery the OpenAccess runs on (if you run it off a battery that is). For the longest time I couldn’t make the simplest part of this board work, the battery sensor. Eventually I traced the circuit to see that it didn’t do anything. Checking the board layout (which isn’t provided in pdf or anything so you need eagle to read it) I found that two of those resistors were in sideways.
I stand by how I assembled that board and will insist that the error lies with the board design. With that identified and repaired I finally got a good read!
There, now it reads correctly. The only thing is there’s no reason I can tell to have that separate from the input voltage. This has a nice switching regulator onboard and runs happily right on lead acid batteries. I decided to jumper the input to the voltage divider so that I could read the voltage that was feeding the board power.
The further modifications I made are these:
That covers the modifications I made to the board. Let’s go over the rest of the hardware:
This is the power section for protecting the rest of the board from a flaky power supply
So, admittedly this is heavy on pictures and light on explanation. Most of the explanation will be in the article that describes the code. At some point I’ll tie all these articles together.