In the target interface, press System button >
F1 (Setting) > F5 (Hardcopy) button and rotate
the scroll wheel (Encode) to locate the target
interface followed by pressing Enter key to
save screenshot. A confirm voice will sound
when successful.Did your screen had a screen protector? (mine didn't)Not 100% sure, but I don't think so.
Utilizing Hardware to Realize Over Voltage Protection / Over Current Protection / Over Temperature Protection(Technically this quote is always correct though)
The firmware version 1.16 (15 July 2020) replacing 1.12 (17 March 2020) is now available to download from their website.I got change log also when i asked GW why there is no new FW at their website.
I'm still waiting for a response from GW-instek about the error message during firmware update to 1.12, the failure to take screenshots, some reaction about the OVP/OCP in there documents is less than 50ms, not 100ms+ and calibration/build date info.
Press the F4 (Recall) button and start to upgrade
The procedure is done when the message, upgrading successful, shows up.
import socket
from time import sleep
ip_address_DMM = "192.168.0.211"
s_DMM = socket.socket()
s_DMM.connect((ip_address_DMM, 5025))
ip_address_GPP3323 = "192.168.0.183"
s_PS = socket.socket()
s_PS.connect((ip_address_GPP3323, 1026))
sleep(1)
Channel = "1"
Voltage = 0.0
s_PS.send(("VSET" + Channel + ":" + str(Voltage) + "\r\n").encode()) # set voltage
s_PS.send((":OUTPut"+ Channel + ":STATe ON\r\n").encode()) # turn channel on
sleep(5) # discharge without load (via 500ohm internal load)
RBValues=[]
Stepsize = 10 # 'mV'
for mVoltage in range(0, 32000, Stepsize):
s_PS.send(("VSET" + Channel + ":" + str(mVoltage/1000) + "\r\n").encode()) # set voltage
sleep(0.5)
s_PS.send((":MEASure" + Channel + ":VOLTage?\r\n").encode()) #VOUT1? includes 'V'
RBVoltage = float(s_PS.recv(30).decode())
RBValues.append([mVoltage/1000, RBVoltage])
print(mVoltage/1000, RBVoltage)
s_DMM.send("dmm.measure.read()\r\n".encode())
sleep(0.4)
with open('GPP-3323Readings.txt', 'w') as f:
for item in RBValues:
f.write("%s\n" % item)"We are checking your inquiry to our engineers.The engineer did say that the firmware update errors weren't supposed to be there but I guess that was a given...
We'll keep you updated if we receive the engineers' feedback."
Nice, you will see the graph you have on DMM6500 is really useful compared to the graph view in the GPP-X323I took some measurements for all 4 channels, see .csv files in the attached zip. I noticed that the script doesn't hit the final voltage value, fixed it for channels 3 and 4 but too late for 1 and 2 (and didn't want to run it again). Take a look at channel 3 in particular - I think I know my favourite for accurate output/readback voltage! Probably should test the current setting too (I don't expect it to be quite as good), but it will need to wait for another day.
For the measurement I did set it to 1PLC and a filter of 5 averages.
Put it on manual trigger and clear the buffer, first time you run it will give an error since it wasn't in remote control, second time you run it will be fine. (maybe I make the script better but it's not like I need it much)
And indeed the zero offset is a bit strange to see.
I don't mind the Voltage offset as much as Current Offset, you can't even tel if something is taking current or not.
There is some leak current through the shunt because the higher the voltage set (without anything connected) the higher the current offset is, not sure if they forgot to compensate for that or just said it's within spec...
P.S. I'm also thinking about setting the PS voltage with an DMM6500 app (touchscreen input) as experiment but I haven't tried the connection yet. (would allow some correction on the setting to get the right output)
I dont get it, the 4323 is +€20,-There is even a promotion, for 3 months:
Maybe it was sold out ?
The 3 channel has some easy USB powered specs compared to the 4 channel so it's not like you get the 3 channel version with an extra channel. (so your USB powered DUT can be powered on at the same time as the other channels)
The USB connection on the GPP4323 is there to put your USB stick, not for power delivery.Nevertheless it is really handy to power an active probe or something similar. Many non-brand specific active probes are USB powered nowadays.
Agreed, hence the "4323 USB port can run low power 5V items (I assume up to the 500mA USB spec, though I've not tested that high)" comment - I have used a Micsig DP10013 on it.The USB connection on the GPP4323 is there to put your USB stick, not for power delivery.Nevertheless it is really handy to power an active probe or something similar. Many non-brand specific active probes are USB powered nowadays.
I've certainly already found it handy for circuits with 3-4 power rails.
I,m telling you i run out of channels already with my first project.This is why I also have a triple channel supply (3rd channel only 3.3/5V), a 400V capable single channel supply and a SMU on the bench 8)
So handy, 12v 6v 5v 3,3v now i need more, 2,5v and 4,66 volt.
Seems you can stack em very easy.
I connected my phone to both USB connections both gave about 500mANo. That is precisely according to the USB charging specs! A standard host port is specified to deliver 500mA maximum. Only charging ports deliver more current but the way this happens depends on whether it is charge-only or a combined host / charging port.
It's strange that the USB power connection (up to 3A) only gives 500mA If you know that if I connect my phone to an USB power plug it takes 1A.
- There isn't 1 standard about how the device should recognize the power port so maybe this device doesn't recognize it correctly, other devices may recognize it...Very much this. USB charging has been a mess for
- There isn't 1 standard about how the device should recognize the power port so maybe this device doesn't recognize it correctly, other devices may recognize it...Actually there is a very detailed standard. Check the USB2.0 charging standard from usb.org .
It wouldn't be convenient if all USB devices are limited to 0.5A, why wouldn't they identify it as charging port, if they didn't it seems like a design mistake to me.You can always put a circuit in between to make the USB power output port identify itself as a dedicated charger or a charging downstream port. But that also requires to set the PSU accordingly (voltage / current limit). Having this circuitry inside the PSU limits the number of scenarios you can test.