I am wrapping up the OSX version of the new GUI very soon and the other OSs soon after. I have one question to ask that I believe I know thew answer to but I would like to have your opinions. Sometimes when you are working on something like this certain features might seem to fit or might make sense while developing that don't really do anything for the real end-user. So, I recently decided to make room for more technical features by removing the settings menu page and removing the code and strings section of the chip information screen. It will now show the info as soon as you select the chip and you simply need to click button 2 to test once on that screen.

You will still be able to control everything in the settings from the new GUI app. So, the features will still be there they just won't be hogging up Vetus' display menu. 

How does everyone feel about that? My assumption in that no one ever uses anything from the settings more than maybe once or twice and the benefits from doing it this way far exceed whatever downsides there are (if any). I'd love to hear your opinions. 

Thanks

-Kelvin 

I have five 30 pin SIMM prototype boards that are built and I'm not going to sell because the new version will actually show up as being connected in Vetus Pars. The five I have won't do that. It will only show up as unknown or the like. However, it will still function exactly the same. So if you'd like one you can have one just pay for shipping. I only have five though so first come first served. E-mail me at kelvin@retrotroniks.com. I'll look up the cost to ship for ya. Have a good weekend.

So: is the VDD that Vetus drives onto the ZIF a fixed value, or can it be selected per chip (e.g. 5 V vs 3.3 V)? If it's fixed, what's the nominal target, and is ~3.6 V expected under load? And are the digital I/O high levels driven from that same rail, or from a separate (e.g. 3.3 V) logic supply? Trying to figure out whether I should be testing this part at a lower VDD on purpose.

Thanks!

Would you consider sharing a technical drawing of the mainboard with measurements and placements of the screw holes, switch, toggle buttons and usb socket.

This way it would be much faster to quickly design case for it so that one doesn't have to pull out the calipers  😉 

May seems to have been a very slow month on the forums and pretty much every other place. That being said, I just want to know if anyone has any issues, questions, concerns, praise? Haha, anyway, I’d love to hear how you guys are liking Vetus Pars and what you’ve done with it and if there are any improvements you’d like to see. Any special chips you’d like a board for? Anything at all.
I’m still working daily on improvements and new addons. The new GUIs and first add-ons are coming soon. Hang in there 

upcoming in the next several weeks should be at least the OSX version of the GUI with the others following soon after and the 30 pin SIMM tester board. 

-Kelvin

When I REFRESH to pull the current list, there is a blank file at the bottom of the list in VetusGUI. If I load that from the hardware into VetusGUI, I will get either the correct Code, Chip Name, Num Pins, Chip Type, and Image fields but the String# fields will all be empty or have invalid characters in them - OR - I will get nothing.

A full reboot of the hardware, close/open of VetusGUI and doing a direct SAVE TO results in the same type of behavior. 

I'm on Windows 11, I have updated the hardware to 1.0.3. I have other much smaller test chip files that saved and run without issue.

Next I deleted some of the pre-installed tests that came on my Vetus and attempted to load them from the website (ex 6502-cj.chip, 4164.chip).  From the GUI I can save the file and do get confirmation that the file saved, although repeating the above steps still shows a blank entry. 

I've tried to backdate the firmware to 1.0.2, but got the same results.

I've tried to reinstall the firmware to 1.0.3, but also got the same results.

Is it possible the internal memory has become corrupted?  and is it possible to factory reset this?

System - Windows 11.

Firmware - 1.0.3

The order is:  Port (select a com port), Add (add a chip file), Highlight the file, Click Load, Select USB Mode from the Vetus Pars.  Any deviation of this and the GUI does not see the Vetus Pars.

Is there a driver that I may need to install.  I have tried this on USB 2, USB 3 ports, and multiple USB cables.  All produce the same result. 

Thanks

Just received my unit and put together. Super please with build quality.

Did my first test on a 4464 DRAM chip. Takes a while but the chip passed.

A little bit later ran the test on a second 4464 chip. Does a column count to 255 and then goes to the next section of the test and the DRAM fails. I tried this with a number of chip and get the same issue. I tried the first chip that did pass and now it's failing.

Using the VU GUI on my Mac, I can't actually see the unit connected although it did show up previously.

Any suggestions on how to resolve this issue?

Thanks

macsonny