When simulating a center-tap full-wave rectifier circuit, the transformer current is high by a factor of 1.414 (should be same as diode current) and waveform shows positive and negative pulses (should be positive only). Both occur only with latest version. And the table formatting is awful - need to resize every column each time I use it.
I've been using version 2.0.04 and will continue to... it works fine in Win10. I'd tell the author if I could find a contact.
I've been using version 2.0.04 and will continue to... it works fine in Win10. I'd tell the author if I could find a contact.
Let me take a look at this. I can check the code changes between the two versions, I'm not aware of anything that would cause this as changes have been minor of late, but will take a look....
When simulating a center-tap full-wave rectifier circuit, the transformer current is high by a factor of 1.414 (should be same as diode current) and waveform shows positive and negative pulses (should be positive only). Both occur only with latest version. And the table formatting is awful - need to resize every column each time I use it.
I've been using version 2.0.04 and will continue to... it works fine in Win10. I'd tell the author if I could find a contact.
Thanks for the feedback, I've had a quick look at some of this stuff.
Transformer current high: Did some checks and I'm getting I(T1) = I(D1) for the conducting cycle which is what I would expect. Can you PM me the .psu file that is causing this and I can look in more detail?
Waveform +/-: This isn't a new bug that was introduced, it was the older version that is the bug 🙂 The current will go in one direction on one half-cycle, and the other direction on the next, so this I believe is now the correct behaviour for I(T1), or current in the transformer secondary windings. The I(D1) should conduct on half cycles only and when conducting should show the same as I(T1).
Table formatting: Something isn't quite right with the auto sizing. It looks like the underlying component has changed between 2.0 and 2.20 so I need to fix this. More news soon...
BTW, I've set up a support group in advance of PSUD3. Haven't advertised it yet but it will be the default contact method for the new version. I'll monitor it ongoing if people want to start using it to report issues/feedback for PSUD2 as I don't visit here very frequently duncanampspsud@groups.io | Home
And the table formatting is awful - need to resize every column each time I use it.
Under "Options" you can enable the "auto table width" option and that seems to address this.
...
Waveform +/-: This isn't a new bug that was introduced, it was the older version that is the bug 🙂 The current will go in one direction on one half-cycle, and the other direction on the next, so this I believe is now the correct behaviour for I(T1), or current in the transformer secondary windings. The I(D1) should conduct on half cycles only and when conducting should show the same as I(T1)
....
In a center-tapped fullwave circuit, the current will go in one direction on one half-cycle IN ONE HALF-WINDING, and the other direction on the next IN THE OTHER HALF-WNDING.
No par of the winding has current going in both directions. This may be the cause of the error in "transformer current".
Look at diode current waveform and transformer current waveform (for center-tap rectifier). First is one direction only, second has both. Yet they're in series, and MUST be the same. The RMS current shown is incorrect for rating the transformer.
Duncan,Let me take a look at this. I can check the code changes between the two versions, I'm not aware of anything that would cause this as changes have been minor of late, but will take a look....
just a quick note to see if you can comment on the likely efficacy of the stepped load function in PSUD2 to predict transient response of the power supply. For some reason I can't seem to send you a PM so apologies for approaching you this way!
This is the thread, and as you can see I am a fan of PSUD2 so far and have been looking for some guidance beyond Voltage achieved and output ripple.
https://www.diyaudio.com/community/...-could-use-some-second-opinions.391379/page-3
Great!
@tonescout
I notice that Duncan wrote this, and has been active there since last being seen here.
I notice that Duncan wrote this, and has been active there since last being seen here.
I've set up a support group in advance of PSUD3. Haven't advertised it yet but it will be the default contact method for the new version. I'll monitor it ongoing if people want to start using it to report issues/feedback for PSUD2 as I don't visit here very frequently duncanampspsud@groups.io | Home
thanks for the advice, much appreciated!@tonescout
I notice that Duncan wrote this, and has been active there since last being seen here.
Member
Joined 2009
Paid Member
It works on the Mac now? wow, that's great 🙂Here you go, he's on diyAudio frequently.
PSUD2 for Mac released
that's what I have been using it on - and it seems fault free so far 🙂It works on the Mac now? wow, that's great 🙂
Member
Joined 2009
Paid Member
where can I download it from, for Mac ?
I have been to here: http://www.duncanamps.com/psud2/download.html
and here: https://groups.io/g/duncanampspsud
and other places, seems to go around in circles.
...but colour me stupid, where is the download link ???????
I have been to here: http://www.duncanamps.com/psud2/download.html
and here: https://groups.io/g/duncanampspsud
and other places, seems to go around in circles.
...but colour me stupid, where is the download link ???????
It seems to have disappeared. IIRC, Duncan said earlier that he would be more available at groups.io
Member
Joined 2009
Paid Member
Mac version is still available. You need to jump through some hoops to find it. You also need to register with the site to access the files section. https://groups.io/g/duncanampspsud/files
- Home
- Amplifiers
- Tubes / Valves
- Bug in latest PSUD 2.20.0