开云体育

No, we're not begging for cash (okay, that happens once a year) - it's about group members contributing data to our archive. This group is about the enthusiasm and expertise of its members, who never fail to step up and impress when there's a problem to be solved. But it's also about our wealth of user-contributed data: Software, EPROM and PLD images, user, service, and reference manuals - the invaluable basics without which using and maintaining our programmers would be impossible. So for the benefit of new members, and as a persistent reminder to longtimes ones, here are a few of the things we're always on the lookout for: 1. Wall Charts: For decades the master reference to programmable devices that owned a spot on our lab walls. Strangely, though, we haven't been able to lay our hands on the wall charts for 1979-1982. If you have any of them, PLEASE let us know and we'll arrange to have them scanned. 2. PPI Socket Adapter Netlists: There are in excess of 256 PPI socket adapters used in the UniFamily (UniSite, 2900, and 3900) programmers. They're no longer being made and sold by Data I/O, and are the only way that most modern high pin count and fine lead pitch devices can be socketed. They turn up from time to time on ebay, but they get snapped up fast and they're never the one you need anyway. So with every PPI adapter that a group member has or can get, we ask that you sit down for an hour, buzz it out, and submit the netlist in our supplied Excel spreadsheet format (we also have a worksheet that makes the job easier). With a library of netlists, rolling your own copy of an otherwise-unavailable adapter becomes possible; without it you're probably SOL. So please take a look at our archive (in the files section) and see if you have an adapter that hasn't yet been submitted. 3. UniFamily software: Over time we've done really well, but we still have only a few of the early revs, and the V6 releases are sorely underrepresented, which to date has left a big hole in a project to generate a single database of the programmer support for all known devices. So please check your floppy sets and help us out. Those are the biggies. Any others that members feel are worthy of addition to this sticky, please let me know. Thanks. Jonathan (just some stupid admin) is so

Hello, Wolfram from Germany here... I have an 3980 with all Adapters and i am wonderung, is it possible (how?) to program Pins for selfmade PCBs? Is there some kind of Pin-Editor or how can one use own Socket-PCBs? I must say, i was working with this device for >16 yrs, created Tasks, but dont know about real pin programming. regards, Wolfram.

Item 376305090741 As of the moment I looked, listed at $300 or best offer. At least two of the PPI's are the rarely-seen 64-pin and 100-pin uBGA. I can't move on this one at this time, otherwise I'd have already made an offer. Perhaps another member will get lucky...? No connection with the seller, just spotting the things, etc. -- Bruce Lane, ARS KC7GR, kyrrin@... "Quando Omni Flunkus Moritati" (Red Green)

Johnathon, I belong to another Group called Emco-CNC Users and they are having discussions about the cost of storage for their group and are considering limiting the size of files, etc on the members. Some time ago you told me to not worry about the size of some files I wanted to upload because we have tons of storage space. As I recall, I donated about $100 toward the cost of our annual fees. There was no feedback as to the total cost, but I would be curious to know. Is there a chance you could contact the owner of Emco-CNS Users (Marty in Mesa) and give him some advice on the topic. The group is very important to us Emco machine owners and I would hate so see these kinds of restrictions when our group does not appear to have the same storage restrictions. Here is a recent clip from the owner of the site...... ----------------------------------------------------------------------------------------------------------- marty_in_mesa 11:28am #9518 Thanks for the kind words and thoughts. At 1200 members we'd be close to $600 annually. While I agree with your sentiments, I'm concerned we might not muster the fee on an annual basis. Once we go full subscription, it's my understanding we can go back with a 100 member cap, meaning while members could leave, none could join. Marty ---------------------------------------------------------------------------------------------------------------- Thanks in advance Doug Wilson W6GOT

Hallo, ich ben?tige das Task Link für Windows da meine CD leider unauffindbar ist. Kann jemand helfen? Gru?, Wolfram.

I'm looking for a 351B104BD pinout cartridge for a Unipak2B. This accommodates 32-pin DIPs such as the Intel 27010. Please contact me off-list if you have one to sell. Mike Loewen mloewen@... Old Technology http://q7.neurotica.com/Oldtech/

If anyone’s interested, I have one available for sale or trade. I’m in the UK Cheers, David

See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. **** Exception Text **** System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details. The error is: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: startIndex ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: startIndex at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos) at System.Convert.ToInt32(String value, Int32 fromBase) at PL2260B_Plus.frmHexEdit..ctor() --- End of inner exception stack trace --- at PL2260B_Plus.My.MyProject.MyForms.Create__Instance__[T](T Instance) at PL2260B_Plus.My.MyProject.MyForms.get_frmHexEdit() at PL2260B_Plus.GetSaveSettings.GetSettings() at PL2260B_Plus.frmMainMenu.btnGetSettings_Click(Object sender, EventArgs e) at PL2260B_Plus.frmMainMenu.frmMainMenu_Load(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) **** Loaded Assemblies **** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9179 (WinRelRS6.050727-9100) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- PL2260_Plus_B Assembly Version: 1.3.2.64 Win32 Version: 1.3.2.64 CodeBase: file:///C:/Users/amonra/AppData/Local/Apps/2.0/99OQJ2X8.YRN/ETVH0W1W.P81/pl22..tion_10702aceb1db4be8_0001.0003_e6895e224b2115b7/PL2260_Plus_B.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.9157 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9176 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9176 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- System.DirectoryServices Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll ---------------------------------------- **** JIT Debugging **** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to

Does anyone haven LCC base for a 3900 (39BASE-0203) but wants a 29BASE-0203 for their 2900? If so, I’d like to arrange a swap. Cheers, David

On 5/24/25 17:00, georgel via groups.io wrote: > With such attitude your PLnnnn software is doomed to be of low quality > and plagued by many bugs and exceptions forever. Without desire for > perfection and exploration of all algorhythmic branches the result will > be like it is now. And unlike some other universal programmers' software > that handles not olny the man-machine interface, but the programming > process itself, because some programmers are without CPUs (many HiLo > for example), your software has a very modest task -- to be a > specialized serial terminal software, a front-end to the programmer's > firmware with some small lookup tables for devices family codes. You are > automating a task that some 40 years ago as meant to be manually done. > And you fail to properly cope with that, putting at risk some rare no > longer manufartured OTP devices I plan to program with the DataIO. Just > a few starts of PLnnnn and it was obvious. George, others have spoken up about this, but I was too busy yesterday to jump all over you for this post. So I will do it now. :) I myself have not run Mike's software, as it's a Windows program and I don't do Windows. However, I've followed the effort with interest and have been impressed with both the capabilities of the program (as I see from the development process) and Mike's skill set. Your assertion that it's "specialized serial terminal software" with a "modest task" is wholly incorrect and demonstrates a complete lack of understanding of both what this software actually does and how these programmers are actually controlled remotely. Not knowing something is not a bad thing; we all start somewhere. But taking a stand and being a dick based on a lack of knowledge IS a bad thing. You are of course entitled to your opinions. But you are not entitled to trash peoples' work or otherwise insult people here. Further, insulting someone's work in a public forum is a shitty thing to do no matter the details. Unless they really deserve it, of course. But Mike's work does not. Putting on my list moderator hat, I will state this clearly and concisely, and I will not repeat it: Straighten up and drop the dick attitude or I will unsubscribe you from this list and ban you. Plain and simple, no ifs, ands, or buts, and the only response I expect from you on this is silence or "ok". I will stop short of insisting that you offer Mike a public apology to be allowed to remain here, but only because I'm in a good mood today, and I hope you were raised well enough to apologize on your own. -Dave, list moderator -- Dave McGuire, AK4HZ New Kensington, PA

I have a use case for the 512k ROMS that I use for a telescope controller. The controller can use e.g.: AMD 27C040 or ST 27C4001 or Motorola M27C4001 or other compatible ROMS. If I have a mixed batch on EPROMS to burn (as I often do), the ability to load the image into RAM once and select the device type as necessary would be most useful. Cheers, David

The following items have been added to the Files area of the [email protected] group. /Data IO/Systems 17 & 19/System 17/Sys17_memorymap.txt By: Alan Bain <alan.bain@...> Description: Memory map for System 17

Just received the boards for the PPI PLCC68 adapters and tested one with an ALTERA EP1810JC-35. My 3980 detected the PPI card as the correct one for the EP1810. Then I erased the part (UV eraser) , loaded it to RAM, edited the fuse map, and programmed the part. My edits were successfully programmed into the part. While this does not confirm every connection on the board, it is a good start.. ed

CRC32B figures are sometimes used to confirm or identify Memory IC devices by comparing to known tables of CRC32 figures. I would like to know if CRC32 figures are also used in much the same way for Logic ICs. Although PL2260+ includes a calculation of CRC32 for Memory ICs, it does not include it for Logic ICs. So, if you know that CRC32 is also used for logic ICs, please let me know. And, in such case, I would very much appreciate getting one or more representative JED file(s) along with the known CRC figure(s) for testing purposes. Thanks, Mike D.

The following items have been added to the Files area of the [email protected] group. /Data IO/UniFamily/2900 & 3900/Firmware/Data IO 3900 V9.3 Firmware Backups.zip By: Rhine Labs <aircraftdelivery.net@...> Description: V9.3 Firmware For 3900 See Board Image In Zip File For Locations 3900 V9.3 28F010 1065 L.BIN (Left By the Edge) 3900 V9.3 28F010 3733 R.BIN (Right By the Pal)