CF-19K mk3 Gobi Install Problem

I see many threads that talk about installing Gobi modems into the toughbooks, and the steps to take, like dip switch settings, etc. I have followed as many of those as I can find and still no luck.

My card is recognized as the Qualcomm HD-USB in device manager. WWAN is enabled in BIOS. I've tried the different settings with a battery pull, powerswitch for 30 seconds prior to powering on. When I attempt to install the drivers, the Panasonic CSA states no GOBI device found. I've tried other GOBI drivers, and actually got 1 set to install, but no luck with creating a modem device. I have gotten to the point of having a QDLoader Com Port there, but can't get any further. Maybe some else has had luck with this. I purchased it with it stating it was for the CF-19, and I have seen pictures of it in a Toughbook, with the claim it works. I have attached the pictures of the card to aid in it's identification. It states on the modem it is a J9CUNDP-1.

I have also attached the pictures of the dip switch settings, and guide. Can anyone help???

 

What OS you running?

 

XP Pro with SP2. Will want to eventually migrate to Windows 7 but waiting for a critical piece of software to support it.

 

Which country are you in?

 

Two things I can think of. First, the dip switch settings for WWAN1 should be the correct one. That is what a CF-19 Mk2 uses with Gobi. Second, make sure you have the latest version of the CSA, version 2.00.1100.01.0193 is the one I currently use. Version 1 will not work with Windows 7 plus there are added benefits of version 2. At the moment, I can't verify the Gobi card. Maybe I can later tonight or tomorrow.

 

I Definitely have the most recent csa package. Dip switches set per wwan1 was tried, shows in device manager as qualcomm hd-usb device but csa says no gobi device found. Running the manual install of the verizon package installs a port called qdloader, but no other device,and doesn't appear to load the modem firmware.

If it helps I'm in Canada. I also Have a cf19 mk4 with gobi that was factory installed and use the csa to install the at&t connection manager. Once I tell it is ok to use a non at&t sim works very well.

 

Where did you get the gobi card, make sure it is a white list card from panasonic !

 

UNDP-1 should be WWAN3 for the dip switch selection.

WWAN1 is EVDO, WWAN2 is HSDP A.

Jason

 

If you got the card from eBay, most likely it's a locked to HP or Lenovo. Most sellers say "unlocked" but that just means it's unlocked to carriers/networks, not BIOSes.

 

You may be right. I was going to say WWAN3 until I compared the switch setting to a Mk2. On a Mk2 UNDP1 is 1,on, 2,on, 3,off, 4,off which is the same as WWAN1 on a Mk3. Of course, Panasonic could have completely changed things between Mk's. Regardless, one of the settings should work.

I just compared trednie's Gobi card to mine. The IC and FCC ID are the same however, my card does not look like that. One thing different is that my card says UNDP-1 and Qualcomm on the label with the FCC ID. You may check the number on the back of the card. Mine says T77Z039.02 LF, Rev. 02L3.

 

I suggest swapping cards between the systems and see if the problem moves with the card. This is a fairly easy check to see if it is the card or something else amiss.

 

I will try swapping the cards tomorrow at work. I will also post the number from the other side of the card (as its at work) but seem to think it is T77Z039.04 not .02 but again, I will post it tomorrow.

When I purchased the card from wholesaler definitely stated for Panasonic CF-19. Is there somewhere to find a list of whitelisted vs blacklisted Panasonic WWAN cards?

Thanks, I'll let you know the results.

 

An update:

The card on the back has T77Z039.04 LF Rev 07. Does that help?

The card will work using the method described at Qualcomm Gobi WWAN Card on Windows 7 but fooling it into using it for xp. It then updates the firmware, and installs drivers for the Qualcomm HS-USB Modem 9212. However, the issue is this has to be run on every boot (I could automate that), but if I switch off the wireless, or standby the computer it won't start the device and I am back to the Qualcomm HS-USB QDLoader only. This is less than ideal on a device I intend to lock down for an end user.

I'm stumped. Not sure how to proceed. Ideally, this should have the drivers on every reboot, not having to run a background loader every time I shutdown, hibernate, standby, or touch a wireless switch. (Well, actually isn't that what the QDloader service is???) It will be unusable for the end user if this is the case, or I will spend more time on the phone providing tech support to support this Frankenstein.

Does anyone have any suggestions to try further. I have also tried this on another unit with exactly the same behavior.

Thanks everyone in advance, I would not have gotten this far without the support, hopefully only a few more steps to go.

 

The Panasonic Gobi is listed in device manager as a Qualcomm HS-USB Modem 250D, IIRC.

Google the Qualcomm HS-USB Modem 9212 and I find this post: Pocketables Forum - View Single Post - How to get 3G working on the HP Mini 1000

It looks like your Gobi card may be for an Acer laptop.

 

Have you installed the drivers for the Gobi card and tried that (notnthe CSA)?

 

Looked for many different drivers for the unit, none get beyond the initial finding the Qualcomm HS-USB QDloader. Tried the Acer and the HP, no change. Is there an .inf file I need to edit or something?

Is it that there are multiple revisions of the same card and the Panasonic is tied to a very specific revision? I know I can run the card using the other loader software, just can't figure out why there seems to be no drivers files/connection manager that supports it.

I will wipe the OS once again and try, however I doubt that will change the outcome.

 

No dice. Tried with a clean OS install. Best I can do with any driver is get the Qualcomm HS-USB QDLoader device installed, along with the qdloader service. Again, if I use the GobiLoader, I can get the card working until a power off/standby/hibernate/wireless switch change, and then have to run the gobiloader again. I may take a stab at editing the source code for gobiloader to piece together something, but this is turning out to be a lot more pain then it should be. If anyone comes up with a suggestion please let me know, I will let everyone know if I figure out another solution.

 

Give me a few minutes and I'll send you the Gobi drivers...

 

That would be great!

Thanks!!!

 

Well, I greatly appreciate the Gobi drivers package, but still no luck. I'm guessing it just isn't what I was told it was. I am contacting the company now to try and get this resolved. But I know that process may take a month or so to sort out, so if anyone else has any ideas in that time, let me know.

Thanks again for the help to this point everyone!!!!