Some of those.Is this circuit pie in the sky, to simple or just plain daft?
But XMM2 is measuring the current for you. Are these XMMs some sort of "probes" that livewire uses to tell you what voltages and currents are in the circuit - or are they real physical things you are going to use?For current, you normally put a small resistor in series with the load - easier on the low side - and measure the voltage across it (PICAXE ADC, maybe) and turn it into current with some maths in your program
Current monitoring is of interest for charging, fault or motor stall detection, bench power supplies etc. But not so much value for purposes of battery health monitoring I would think? Simple voltage monitor would suffice for that purpose, I'm sure.i have been toying with adding a battery level monitor to my macro rail .... but adding the sense resistor in could be tricky.
Might be a misunderstanding there; 2.5Ah is the capacity, the size of the bucket. You can pour the content out fast - 5A - or slow - 0.5A - but only for so long in either case; half hour or five hours respectively. There is no 'more' to be had from the bucket.it only rated for 2.5Ah, but persume it could deliver more if needed
Martin, far from it, I have considered it and if I had a spare £20+ I would use them, but I haven't and so I would like to explore a simple method of measuring the output voltage and load of a PSU currently being constructed. I have several 16X2 LCD units and thought it would be a neat idea to use them as the 18M2 used to drive them has 3 spare pins. Once I have got the dividers set up correctly, the next step is to make sure what you have said doesn't happen, there is no point in building something the first time you switch it on and use it, the magic smoke escapes. The terms high side and low side does confuse me slightly so off to google it and cram some more info in the old grey matter.............but that suggestion seems to have fallen on stony ground
Yes, that's much more what I would call a Bench/Laboratory Power Supply design. However, the schematic diagram doesn't have any component values marked, so it's not immediately obvious exactly how (or how well) it works. It would take a considerable time to analyse the full design from the Parts List (and ideally build it) to determine whether it is just a "competent" design or a "good/excellent" one.I came across this PSU, it seems a bit more advanced than the one I have built, any advice on this one?
Don't trust any circuit diagram that labels a mains transformer as TransistorWe could go really over the top and construct this one..........................
View attachment 16319
Would be nice though?
#PICAXE 18M2
symbol lcddata = pinsB
symbol rs = C.7
symbol enable = C.6
setfreq m16
symbol loopcounter = b20
symbol volts = w0
INIT:
setfreq m16
dirsB = 255
low rs
output enable
lcddata = %00111011 : pulsout enable,16
lcddata = %00000001 : pulsout enable,608
lcddata = %00001100 : pulsout enable,608
lcddata = %00000110 : pulsout enable,16
SETSCREEN:
low rs
lcddata = 128 : pulsout enable,1
high rs
for loopcounter = 0 to 15
lookup loopcounter,("VOLTS = . "), lcddata
pulsout enable,1
next loopcounter
low rs
lcddata = 192 : pulsout enable,1
high rs
for loopcounter = 0 to 15
lookup loopcounter,("AMPS = . "), lcddata
pulsout enable,1
next loopcounter
low rs
MAIN:
do
readadc10 C.2,volts
Volts = Volts **64064
Volts = Volts *30
volts = volts / 10
low rs
lcddata = 136 : pulsout enable,1
high rs
for loopcounter = 0 to 1
BinToAscii w0,b10,b11,b12,b13,b14
lookup loopcounter,(b11,b12), lcddata
pulsout enable,1
next loopcounter
low rs
lcddata = 139 : pulsout enable,1
high rs
for loopcounter = 0 to 1
BinToAscii w0,b10,b11,b12,b13,b14
lookup loopcounter,(b13,b14), lcddata
pulsout enable,1
next loopcounter
low rs
loop
Check the number of program bytes in my version compared with yours.Code:Volts = Volts **64064 Volts = Volts *30 volts = volts / 10 [/QUOTE] Hmm, a little complicated. The **64064 is basically a "calibration" stage, multiplying by about 0.977 (i.e. 64064 / 65536). It allows a very high resolution, but only up to * 0.99998 (i.e. 65535 / 65536), it won't work if you need to calibrate any higher. So I would normally use 32032 and multiply by 2 somewhere else in the calculation. Your next two lines are just multiplying by 3, so your final resolution must increase also in steps of 3 . It's where I would put in that extra *2 , i.e. volts = volts * 6 . For the "printing" part, I'd use something like the following (not fully tested as I don't have any hardware set up at the moment): [code] Volts = Volts ** 32032 ; Adjust up or down for final calibration Volts = Volts * 6 ; "Magic number" related to the voltage divider and calibration factor, etc. :) ; Set (or leave) the cursor at the start of the numeric field. (##.##) High rs BinToAscii Volts,b10,b10,b11,b13,b14 ; Note the exact sequence of byte variables b12 = "." for bptr = 10 to 14 ; Point to variables b10 to b14 in sequence lcddata = @bptr ; Read the ASCII character pulsout enable,1 next bptr
Cheers, Alan.
Volts = Volts * 60 ; And Optionally, + 30 to "round up" the original integer value
BinToAscii Volts,b10,b11,b13,b14,b12 ; b12 (millivolts, but not accurate) will be overwritten by the "."