On 5/7/2022 2:41 PM, Pete Boser via groups.io wrote:

*cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware*

If you are sure the software package you are installing IS genuine, if you trust Duncan does not want your secrets, if you got it directly from Duncan's site, on a legitimate network connection, then just say "Install darnit!"

Last week I had a new Win10 and installed Office 2003 and PSpice 1999, and a lot of other stuff Win10 never expected to see.

Windows has several errors. Files downloaded from the internet won't run without intervention; you can poke file Properties and un-check that. And program installers usually raise a warning, but you expect that.

Apple wants to protect its users AND its business, so mystery files make it upset. Specific advice for Macintosh Gatekeeper warnings/blocks:



Trend Micro is a well known antivirus shop. Their general strategy includes running A-V on any file of uncertain origin. Since you know who and where your PSUD installer came from, that seems excessive. You know the file is OK, and it is reasonable that Apple can't track (or can't remember) every program out there.

Hi Pete,

As background, the message comes up because I'm not a registered developer as this costs $$$'s per year and I don't charge for the software, or use advertising, so it's a cost I don't really want to soak up for no return.

Here's how to work round it:?

• Download the latest file from the files area?/g/duncanampspsud/files/psud2_macos
• Open the download tray and click on psud.....dmg file which will mount and open the download image
• This is the important part -?Don't click on the psud.....app file

To open the app do the following:

• Ctrl+click on the psud.....app file to open a context menu
• Select Open from the menu
• You will get the same message about the developer and offered a choice to [Open] [Eject Disk Image] or [Cancel]
• If you don't see the [Open] option first time round, click [Cancel] and go back to Ctrl+click on the psud.....app file again, it should come up

Finally, you might want to drag the psud.....app icon over to Favourites/Apps to make it a bit more permanent. Hope this all helps.

Regards,
Duncan

Hi Pete,

Can you confirm what version of MacOS you are using? I'm just upgrading to the latest version (Monterey 12.3.1) to see if that's the problem. Also can you let me know if you are having the problem running the software of if you're experiencing the problem at the installation stage.

Regards,
Duncan

Hi,
I have a new Mac after years of PC only, and when I download the Mac version from the website I get a message saying:?

“psud2_build73” cannot be opened because the developer cannot be verified.?macOS cannot verify that this app is free from malware."
I looked back in the group and it seems like folks are not having this issue.? Any suggestions?
Thanks,
Pete

Hi,

There's no IOS or Android versions, and none planned at this time. The routemap for PSUD3 encompasses Windows / MacOS and additionally Linux.

Regards,
Duncan

IS THERE A PSUD2 VERSION FOR IPAD?

?Thanks in advance.

Peace,
DrRick

I install psu designer on Linux with Playonlinux, the program starts and simulates but the graph does not appear, how did you solve?

Thanks to both Duncan and Paul, that's exactly what the sim indicates.? Well, that sure showed me for trying to take a shortcut.? I now have a CRC network which works like a charm.

Tom's MOV suggestion is a good one as well - powering the system off would present an open circuit (modulo transformer impedance) to the choke so it would return a flyback voltage.? Would a reverse-biased diode, such as used across relay coils, also work when placed between the choke input and ground?? From stored energy = LI^2/2 I get about 60 millijoules for a 60 mH choke filtering 1.4 amps, so as long as one doesn't get too energetic with the power switch a 1N400x should be capable of dealing with this, yes?

Scratch the reverse-biased diode idea: adding a tiny capacitor (10 nF) before the choke and looking at the voltage shows the choke input goes below zero by about a diode drop at the zero-crossing of line power.? Not for long, 100 or 200 microseconds each cycle, but enough to make a mess.

开云体育

---

开云体育

---

Hi,

There was a thread on something similar only a few days ago where the contributors gave some good tips on choke input supplies ->?/g/duncanampspsud/topic/90581045

Regards,
Duncan

How can avoid the rectifier PIV exceed value, changing diodes? what's? The last choke is a CMC but can't simulate.

As the current doesn't instantaneously drop to zero in real life, the voltage generated will be limited.? HOWEVER, your power line is not a perfect sine wave forever... there are inductive devices being switched elsewhere, lightning induces impulses, even without a direct hit, and of course your supply gets turned on and off. As a result, ANY solid-state rectifier used with a choke-input filter should have overvoltage protection - an MOV (between DC max and diode PIV rating) or a small value input cap will do.? In an industrial application, I saw a 1400V, 240A three-phase bridge (used on 208VAC) that would fail every few hundred on/off cycles. A .047 uF across output fixed it for good.

Tom Bavis

On 4/20/2022 7:18 AM, Duncan Munro wrote:

There are various formulae around for figuring out the correct minimum choke value

Try "Figure out the load resistance, E/I (Volts, Amps), then divide that by 1200. The result is in Henries."

In 50Hz lands use "1000".

So for 24VDC and 0.6A we have 40r, divide by 1200 is 0.034H.

Or for 50Hz, 40r, divide by 1000 is 0.040H. (40mH)

You have 0.007H. Less than 1/5th what the formula suggests for minimum.

Yes, it may kick violently.

Other tip: whenever possible! don't use "current sources". No practical component acts as a perfect current source. I suspect if you replace your I1 with a 40 Ohm you will still get kicks but not divide-by-zero spikes of a math model.

I would also simplify first. Your R1 and C2 probably have little effect on the kicking and rectifier stress.

However none of this changes the fact that 6.8mH is much too small for a 24V 0.6A load. The simplified supply shows (as Duncan says) choke current going to zero every half-cycle, which spoils the advantage of a choke-input filter, while adding the fun of "infinite" voltage kicks.

There could be a danger of damage to the rectifier; the problem is the choke value being too low.

It's essential on a choke supply for the current to be continuous through the choke without dropping to zero at any point during steady state operation. If it's doing this, you need a bigger value, and it's a good idea to monitor I(L1) to see what is happening and yield some great clues as to what will work and what won't work.

Had a look at your circuit and the current collapses to zero during the cycle due to the low choke value, this will cause the voltage to head towards infinity until something breaks down, either insulation in the transformer or more likely the rectifier breaking over with the excess voltage. This could cause excess heating in the rectifier and subsequent failure. You can increase rectifier leakage for a visibly better result, however this is just a band aid for the underlying problem.

There are various formulae around for figuring out the correct minimum choke value, but I just did some hit and miss values and got 30mH as about as low as I'd want to go. If you try this value, or higher, it will give much better results.

Have a look at I(L1) without changing anything, then look again after upping the value to 30mH and you'll see the difference it makes. Hope this helps.

Regards,
Duncan

PSUD gives me this result on a particular power supply (yes, the choke is underspecified on purpose).? Playing with rectifier leak mitigates the problem somewhat, but it still looks unnatural.? Is this a math problem or is my rectifier in actual danger of blowing up?

?

?

Is the 39 nF silver mica cap (between the HT legs) a correct value? I can only find 39 pF in Mouser catalog

Thank you Evert, I don't remember where to post the link but Duncan posted that the recommended "simulate" set is for "100ms" after a reporting delay of "0" S to see the best real ripple your PSU is doing.