Yes Busby that is correct, works as power on to the LM386.Pin 6 of the LM386 ( Vs ) is connected to C.0 on the schematic.
Is that correct ?
Sorry Dippy, thats just me, I did it that way thinking it would leave less confusion if I labelled up everything going to where it goes, I thought it was OK? Never mind will re do it so it reads easier.I'll have to leave this to people more PICAXE-savvy than me.
In standard schematics when you give a wire a label it is joined (in netlist) to any other wire with the same label.
Hence my confusion and that there is no obvious schematic connection to the PICAXE pins.
You should bring out stubs from the Micro with the appropriate labels attached.
You've done it with the power lines but not on B.1 etc.
What CAD are you using?
I could understand it if it was just pins A.0 to A.3 going wrong. All solenoids have back EMF protection using IN4001 diodes and driven using IRF510 FET'sMultiple pin failures to match multiple solenoids?
How are you driving the solenoids?
Do you have reverse EMF protection?
symbol SOUND_ON = C.0
symbol SOUND_IN = C.2
symbol PG_ON = C.1
symbol LIGHT_IN = C.3
symbol LIGHT_ON = C.4
symbol FLASH = C.5
symbol CAMERA = C.6
symbol PG_IN = C.7
symbol SOL1 = A.0
symbol SOL2 = A.1
symbol SOL3 = A.2
symbol SOL4 = A.3
symbol COL2 = pinB.0
symbol ROW1 = B.1
symbol COL1 = pinB.2
symbol ROW4 = B.3
symbol COL3 = pinB.4
symbol ROW3 = B.5
symbol ROW2 = B.6
GKP:
Do
Gosub GTKP ' Wait until no key pressed
Loop Until key_value = 0
Do
Gosub GTKP ' Wait until key pressed
Loop Until key_value <> 0
If key_value = 11 Then
key_value = 0
End If
Return
GTKP: ;Keypad scan coding
key_pos = 0
key_value = 0
High ROW1 : gosub ScanCol : low ROW1
High ROW2 : gosub ScanCol : low ROW2
High ROW3 : gosub ScanCol : low ROW3
High ROW4 : gosub ScanCol : low ROW4
Return
ScanCol:
if COL1 = 1 then : key_value = key_pos + 1 : endif
if COL2 = 1 then : key_value = key_pos + 2 : endif
if COL3 = 1 then : key_value = key_pos + 3 : endif
key_pos = key_pos + 3
return
It does seem odd. Though B.x pins could produce shorts between output high and low depending on buttons pushed, that should not affect the A.x pins, and not just one.I could understand it if it was just pins A.0 to A.3 going wrong.
Do
dirsB = $FF
b1 = 1
For b0 = 0 To 7
b2 = b0 + 1
For b3 = 1 To b2
pinsB = b1 : Pause 250
pinsB = 0 : Pause 250
Next
b1 = b1 * 2
Next
Loop
Sorry that should read 'using dirsA, dirsB and dirsC'.Same results hippy on dirsA, dirsB and DirsC............?
I certainly have Buzby.Have you got an oscilloscope ?.
Hi Stewart,So, any ideas how and why this has happened please?
Those are your output pins driving the keypad matrix. Sitting at 2.5V suggests a short somewhere, 0V fighting 5V.Pin B.3 oscillates between 2.5v and 5v
Pin B.5 sits at 2.5v
Pin B.6 sits at 2.5v
Hi Stewart,Sitting at 2.5V suggests a short somewhere, 0V fighting 5V.
Windows Vista or later also has a program built in called 'Snipping Tool'.For grabbing screen images I use this : http://bluefive.pair.com/snapshot.htm
So get your PCBs on your screen, individual ones as big as you can, then callup up Snapshot, then save as .png.