When I log in to myAnalog I see several past filter designs under "My Resources". When I click on any of them I get a message "Unable to load design, please contact ADI." Same behavior in Firefox46, Edge & IE11. Suggestions?
Thanks for the writing in about this bug. I apologize for the time you had to spend messing with this. The good news is, that as of about an hour ago, it should now be fixed. You should be able to load previously saved design files now.
Cause of the bug: We introduced this bug two weeks ago. We inadvertently changed the save/load path to another directory, so anything saved before May 17th wasn't accessible. Anything saved after May 17th was, because it was in the new location.
With the fix, we are now saving and loading with the original directory structure. We also moved the designs saved in the last two weeks to where they should have been saved in the first place. However if you run into any issues with a design saved between May 17th and May 31st, please let us know.
Our apologies for the bug.
Thanks for the fast resolution! It’s a great tool with a great GUI I use often in my DAQ designs.
I do have one tweak request perhaps you could forward. I often want to adjust values to observe the noise effect or select in-stock capacitor values. That works great and is a very useful feature. But whenever I return from Final Results to Component Selection, at least one of my previous selections via the Capacitor/Resistor size slider are lost.
Example: On a 4-pole Butterworth, I move the R-C size slider to use a 1% precision capacitor I already stock, say 1 nF, from a default value of say 3.3 nF. But if I return to the Component Selection page from the Final Results page to try another variant, the slider is returned to the 3.3 nF default. In the 4-pole case, it appears that Stage B reverts but the Stage A setting is retained. It would be an even greater tool if the prior selections were all retained.
Thanks and regards,
Thanks Gary. We didn't know about the R-C size slider resetting issue. That shouldn't be happening. We'll get this in our queue to get fixed.
Retrieving data ...