MorganS:
Or it is possible that the fault is in the wiring and it just cant "hear" the buttons.
Yes it could, and I was thinking of connect my laptop and send on and off signal to the board, same as the signal that the button does. But then Ill problably need the sourcecode to see what the button does, or what do you think?
john121212:
Sorry for that, no its highly prioritized for me.
Right now, from your recomendations, I´ve cut a hole in the metal under the car in to the trunk, where I can look in, and see the board and the connections. From what I can see, not from the best angle, the board have 3 lights, red, green and yellow.
Now that you have a hole why not save yourself a lot of trouble by poking something in to open the lock. Wire coat hangers are great for that sort of thing.
Update on my case.
So, I got the box out, managed to get the backseat out. It seems the board is ok. But better, I got in touch with the builder, and he will come and look at it during next week. Let you guys know if we can locate the problem.
Ok, so it´s finaly solved.
It was never a problem with the actual arduino board or the connections. When I got the box out(see image attached) we could follow the wires and see that there were 6 switches that should be pushed down by the trunk cover and the cab. When those switches were pushed, or not pushed, the arduino would open or close the trunk depend on the case. The problem was, that one of the switches had slipped 2 cm(!), so when the cover was closed, it never pushed the switch..
I got the USB from the developer, that should have contained the source code, but it was acctuallty empty
Now I have to build the construction a bit more failsafe.