i've tried two calbes. one is elm based, is working with other software than cf, but with less details. i've also tried a kl/kkl cable only for audi,vw,seat, works good with other software than cf, and absolutely not in cf. the reason is, that it's an absolutely different type of cable, which means, protocol is in software, not like the elm in hardware.
OBD I was never really a standard, so interfacing to it is a real headache. There are stand-alone readers out there, but they're very expensive. I've never seen a module for OBD I like we're talking about for OBD II.
The OP has a 2003 Hyundai Santa Fe, so I'm pretty sure it will have OBDII, most likely the ISO version.
As far as I'm aware, the only officially supported OBDII cable is the ScanTool.com ELMscan range. Don't spend extra money on the expensive one they push on their front page that does all 3 variants of OBDII (unless you plan on changing your car regularly) get the ELMscan 3 in the correct variant for your car.
Also I can confirm that the OpenPort cable from tactrix.com does NOT work with CentraFuse, so don't get that.
It all depends on the car. My Nissan 200SX S14a has a kind of proprietry OBD1 interface called Consult. It is not fully OBD1, but non the less, certain clever peeps on the net have created an interface for it.
For those who wonder, mine came from PMSL developements, but Blatz ??? (spelling) do them also
Google Search IS your friend, and probably will be for a few hours
It took me some trial and error to find out the hard way that mine wasn't OBDII as I had been told a million times that every car sold after 1999 was OBD2 compliant by law! THIS IS NOT TRUE!!!