Data IO 29b - Troubleshooting

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
Chaps,

To summarise, I imported a Data IO 29B from the US complete with UniPak2B.

It did not come with serial cable, so I constructed it from the retroclinic website.

Using PromLink 6.2 (Macro's patched version), I have been try to get the 29B to work remotely.

I have yet to get it to work, PromLink constantly complains it cannot contact the 29B.

I think I have pretty much tried everything, and now need someone who has a 29B to eliminate where the problem may lie. Perhaps they could send me their unit.

Quite desperate now to get this damn thing working.
 

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
Ok - I have had no response so thought I would add more information;

I have been using an old Toshiba M300 laptop (with docking station which houses the integrated 9 pin RS232 Serial Port) loaded with XP SP3, which has a serial port which I know works just fine (I tested it with an EEPROM programmer which has software that runs in native XP).

I have managed to find the patched PL.EXE file (for XP, by macro/Mike) and have been trying to use that.

I put the 29B into Remote Mode by hitting SELECT, F1, START, START, and then fire up PromLink 6.2 (patched for XP). It runs fine, but when I try to communicate with the programmer, I get a red dialogue box popping up in the Dos Shell window saying the programmer cannot be reached. At this point, strangely, the LEDs on the UniPak2B for 6 & 7 Zif Sockets start to flash??

I built the Serial Cable using the Retroclinic directions here;

http://www.retroclinic.com/leopardcats/dio/dataioserial.htm

My settings for the Programmer and my Serial Port (COM1) are 9600, N, 8, 1

I have tried different variations of serial cable builds, none have worked including an off the shelf NULL Modem cable.

In order to eliminate the laptop as the potential problem, I went into my loft to dig out an old XP PC I had shoved up there a few years back. It was an old Athlon 1.7 Mhz PC with a motherboard sporting integrated Serial and Parallel Ports.

I booted it up, and fired up PromLink connected to my 29B, and was frustrated to see that I had the exact same problem. Red box complaining of no connection and LEDs 6/7 on the UniPak2B flashing.

The only thing I will add, is that I found another chap on KLOV who had the 'exact' same problem as myself. He had built the cable on the retroclinic website but never got it to work. In the end, a standard Serial Modem cable and a Null Modem Adaptor solved his problem.

See below pics of my custom cable I built using the instructions on the retroclinic website. Note that I had stupidly soldered one of the wires to pin 19 on the DB25 connector when it should have gone to pin 20. I should add that correcting this made absolute no difference.

DB9_side_zpsaea80c21.jpg~original


DB25_side_zpse711819b.jpg~original


I would really appreciate it if someone could just confirm that my cable is good or rubbish.

I also tried DOSBOX on the laptop, defined the Serial Port as COM1 realport in the configuration (so DOS can access it), mounted the PromLink folder and ran PL.EXE. Unfortunately the results were the same, the Red Dialogue box complaining of no connection and LED's 6 & 7 flashing on the UniPak2B.

I also ran PromLink 3.1 & 3.4 from DOSBOX, and again I was not able to communicate with the 29B.

To say the whole troubleshooting process has been frustrating is an understatement.

Having exhausted all avenues, I decided to dismantle the 29B. At this point, I decided to upgrade the firmware from V04 to V06 - which I did successfully.

I stripped the 29B right down to the motherboard. I have to say it was well put together and easy to dismantle. I also discovered I have the 128k RAM board.

I located the MC1488 and MC1489 ICs used in push/pull configuration to drive the RS232 port right next to the DB25 Serial Port. I desoldered them both from the PCB and was only able to test the MC1489 (tested good) as the MC1488 used non-TTL voltages and my tester did not support it. Therefore, I socketed the board and replaced the MC1488 with a fresh IC.

As you can see, it's not as though I've not tried to resolve this myself.

remote_mode_zps9183621e.jpg


red_error_screen_zpsaa97cfcb.jpg


promlink_setup_zps388b7e3c.jpg


29B_dips_zps30b53ebd.jpg


29B_baud_zps50195072.jpg


Ben (Purity) also took the unit away to have a play, as I had my fill of it, and sometimes a second pair of trained eyes helps.

He used Hyper Terminal successfully with the unit, but still could not get PromLink to talk to the 29B.
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Are you sure you're not over complicating all of this? I don't remember the details but I KNOW I used to just use a USB to serial cable as at one point I started writing some Mac software to control it !

I have a feeling it was a USB to serial adapter and a Retroclinic cable mind as I bought my Data I/O off of Mark!!

Have you thought about contacting Mark (RetroClinic) and asking if you can buy a tested working cable from him? I'm sure he'd sell you one provided he still has the means to test it. May not be the cheapest option but I can assure you, his cables are damn good quality!
 

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
Martin - I'm not sure I am over-complicating it, these are just the things I have done in order to try and get the damn thing to work.

My laptop has integrated RS232, so no need for a USB to Serial cable.

I never thought of contacting Mark to build me a cable, good idea. However, seems pointless if Mark is just going to give me another cable built to the same spec as I have already built.

Ideally, I think I need to get someone to test it that already has a 29B.

Shame you sold yours :)

I should add that Ben (Purity) also gave it a shot with no success, and his PC interfacing skills are better than mine.Equites2014-04-28 00:38:46
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
I sold mine to DanP - I think he still has it
smiley1.gif


The other thing is that if you were to get a cable from Mark and it didn't work then you'd probably get some assistance to work it out, and it's likely Mark still has a Data I/O as well?

Ah. Unless of course I bought his only one!

guddler2014-04-28 02:07:10
 

Purity

The Oracle
vacBacker
Feedback
17 (100%)
Credits
2,999CR
Equites said:
He used Hyper Terminal successfully with the unit, but still could not get PromLink to talk to the 29B.

Just to clarify that I can get some of the LED's on the unipack to flash using Hyper Terminal when pressing return, to indicate there is some kind of communication going on, but could not fully get it to work in it.
 

DanP

Administrator
Staff member
vacBacker
Feedback
5 (100%)
Credits
2,232CR
I do still have mine from Gudd but have never even fired it up cos I never had the room. I've just finished my workshop build and am in the process of getting everything in place. I know it has a homemade cable that looks from the outside much like yours, once I get a bit of time I'll see if I can have a play. I was planning to use an old XP laptop which I keep for any old serial comms applications. I'll probably use this topic as a starting point to getting it up and running
smiley2.gif


Dan
 

david_orton_2000

Green Mario
vacBacker
Feedback
8 (100%)
Credits
344CR
Hey all,

I also had a the exact same issue with my 29B, in the end shelved it as a very large pain in the ass, with the only reason I kept it was for 2708 burning, which to be honest, I would now rather convert a pcb to take 2716 or larger Eeprom... It in fact smoked (caps on psu section) when I turned it on 6mths ago...it just keeps moving down the "to be repaired" pile, as I suspect a number of people have too! :)

Still, I would like to fix it and I love comms, RS232 in particular and managed to get tones of devices communciating when everyone (not here, many years ago) said "it could not be done".

Well, I tried all sorts as Equites did, still 0.
-I will repair it at some point, maybe we should have a "Data I/O Arcade party" to trouble-shoot the lot of them and help each other? As more than enough brain-power on this forum for that. :)

Cheers,
DaveO.
 

david_orton_2000

Green Mario
vacBacker
Feedback
8 (100%)
Credits
344CR
Martin - smoke was dried out caps, as unit was not turned on for years.
After turning it on since then, no issues, however the 3-4 caps are bulging and need replacing..

Anyway, the comms part is what's need to be working in any case, else I will probably sell/through it as it is big and useless right now.. :-(
 

PaulSwan

ZZZ
Feedback
1 (100%)
Credits
1,118CR
I didn't make my own cable for the UniSite - I just bought a 25-way to 9-way off Amazon, a Belkin F2L088-06 DB9 female to DB25 male modem cable. I use it with an old Dell desktop that has a built in RS232 port running Windows XP SP3 and Hyper Terminal.
Paul.
 

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
I heard from Mike (macro) who said he had two of these.

One would communicate fine with PromLink, the other he never got to work.

Does not fill me with confidence.

I wonder if the Baud Rate switch is the weakness here? It is socketed for a DIL socket (16 pin I think), and easily lifted if not careful.
 

Purity

The Oracle
vacBacker
Feedback
17 (100%)
Credits
2,999CR
If the baud rate switch was broken would it not just be stuck on a baud rate, rather than cause connection issues?

Even if the baud rate was stuck at 14400 as an example, you could still connect at 9600.

If the baud rate was at 2400 and you connected at 9600, then you'd only get 2400.
 

Purity

The Oracle
vacBacker
Feedback
17 (100%)
Credits
2,999CR
PaulSwan said:
Heh, Purity, RS232 doesn't quite work like that ;) The host and target must be set to the same rate for it to work properly.

Paul.

Ok cheers Paul.

I just didn't remember it like that in the modem days, but maybe there was some other auto negotiation going on?
 

Macro

Active member
vacBacker
Feedback
4 (100%)
Credits
2,016CR
modems would auto-negotiate the best rate, but the link between the PC and modem was fixed - usually at 19,200 (if you had a US Robotics)
 
Top