Another "No remotes found" problem

Sam · Post by **Sam** » Mon Dec 14, 2015 7:05 am

I've searched and read several threads about this and I still can't get it to work and need some help please.

I've been using RM/RMIR off and on for years on my XP machine but I just can't seem to get it to work on 2 other PC's I now regularly use, Win 8.1 and Win 7 machines. Both PC's are 64 bit. I prefer it to only be on my 8.1 PC. Also, no other versions of RM/RMIR have ever been installed on either of these newer PC's.

I've tried both and get the same problem. I've d/l'd the latest v2.03 build 12 and the drivers from FTDI. I'm using the USB cable to program ATLAS 1056B01 remotes and this combo still works fine on my XP 32 bit PC.

I can get the yellow triangle and "!" to go away in device manager and it says this device is working properly but still I get "No Remotes Found" in RMIR.

Any advice or step by step post or link would sure help me please.

Thanks !

Post by **The Robman** » Mon Dec 14, 2015 7:48 am

Last time the solution was to install the right driver. You didn't mention what drivers you have installed.

Sam · Post by **Sam** » Mon Dec 14, 2015 8:57 am

I wanted to post screen captures but doesn't look like that's possible so here are the drivers listed in "Driver File Details"

C:\Windows\system32\drivers\ftser2k.sys
C:\Windows\system32\DRIVERS\serenum.sys
C:\Windows\system32\ftcserco.dll
C:\Windows\system32\ftserui2.dll

And in Device Manager...

Ports (COM&LPT)-
USB Serial Port (COM3)

That is all that is under Ports in DM.

Let me know if I can provide any other info and I'll do so immediately

Thanks

mdavej · Post by **mdavej** » Mon Dec 14, 2015 9:16 am

Win 8 and Win 7 have the correct drivers built in already, so the driver install was unnecessary.

Strange that the drivers are in system32 for your 64 bit machines.

In any case, post your rmaster.err file.

Sam · Post by **Sam** » Mon Dec 14, 2015 9:26 am

OK, just uploaded that to the diagnosis area...

http://www.hifi-remote.com/forums/dload ... e_id=13771

Post by **The Robman** » Mon Dec 14, 2015 10:03 am

Sam wrote:I wanted to post screen captures but doesn't look like that's possible ...

http://www.hifi-remote.com/forums/viewtopic.php?t=6557

mdavej wrote:Win 8 and Win 7 have the correct drivers built in already, so the driver install was unnecessary.

Ideally, that's true, but as you recall from last time with Steve Kovacs, it turned out to be a driver issue.

Sam · Post by **Sam** » Mon Dec 14, 2015 10:10 am

I didn't think about imageshack, was trying to see if I could do direct from my PC, thanks, I'll do that in the future.

The Kovacs post was the last one I read before posting. I just don't get it, I've uninstalled and reinstalled the driver at least 10 times and no good.

Not sure if it matters, but when I uninstall, including deleting drivers, then rescan for hardware changes, windows never successfully installs the drivers on it's own. I then do update driver, have disk and select the ftdibus and or ftdiport files. ???

Also, I'm doing all this on a Win7 64 right now.

mdavej · Post by **mdavej** » Mon Dec 14, 2015 10:30 am

The Robman wrote:
mdavej wrote:Win 8 and Win 7 have the correct drivers built in already, so the driver install was unnecessary.
Ideally, that's true, but as you recall from last time with Steve Kovacs, it turned out to be a driver issue.

I think Steve was a very special case. Remember, his entire install "got deleted", and he never saved any files whatsoever. Who knows how his system got to such a state.

Anyway, I see that Sam's file shows no JP1.X port and tries to connect via JPS (I've forgotten which interface JPS is). Driver details look correct.

File looks as if cable isn't plugged in or is oriented wrong.

mdavej · Post by **mdavej** » Mon Dec 14, 2015 10:33 am

Just saw your last post.

Maybe you are installing the driver wrong. Unzip the driver files to a folder, then point just to that folder, don't select any files. I just tested a fresh 64-bit Windows install, and that worked for me.

You should be using this driver:
http://www.ftdichip.com/Drivers/CDM/CDM ... tified.zip

Sam · Post by **Sam** » Mon Dec 14, 2015 10:33 am

Sorry, I think I had selected jps last. But usually I have autodetect selected.

I'm plugging in the cable the same as I do on my XP machine and I have pin 1 identified on my plug.

Sam · Post by **Sam** » Mon Dec 14, 2015 10:34 am

We posted at the exact same time I think. OK, I'll do as you say right now.

Sam · Post by **Sam** » Mon Dec 14, 2015 10:45 am

OK, I unzipped the file you specified into a new folder on my desktop I named RM. I then uninstalled including deleting drivers. Rescanned for hardware changes, Windows attempts to install on it's own but does not complete successfully.

I then update driver, select the RM folder on my desktop and it auto fills in the file without me selecting it (ftdibus.inf)

I went ahead and selected open... and again, no remotes found !

EDIT: I just re-uploaded a new rmaster.err file to the same link as above, updated it actually.

mdavej · Post by **mdavej** » Mon Dec 14, 2015 11:10 am

Try a different USB port, one with black inside instead of blue.

Then make sure you go back to Auto select or JP1.X, not JPS.

Your remote is connected when you try to download, right?

Where did your cable come from? You may have a counterfeit FTDI chip that's incompatible with FTDI drivers. It's very strange that Windows won't auto install the driver.

Sam · Post by **Sam** » Mon Dec 14, 2015 11:25 am

I've tried 3 different USB ports, one on the side and 2 on the back. All are black on this Win7 PC. And I have select "Auto-detect".

Absolutely the cable is in a USB port and connected to my 1056B01 when I attempt but it acts as if it's not.

The cable came from ebay as far as I can remember and has always worked perfectly. I just fired up my old XP PC and it worked perfectly I just now uploaded and downloaded to the same 1056 remote. I just want to phase out the XP machine completely.

On my XP PC, I just looked in Device Manager with the cable plugged into the USB port and it's listed as "Prolific USB-to Serial Comm Port

and the only drivers showing in driver details (on the XP PC) are
C:\WINDOWS\system32\DRIVERS\ser2pl.sys
C:\WINDOWS\system32\DRIVERS\serenum.sys

However, RMIR on the XP is old, Version 8.03

Post by **The Robman** » Mon Dec 14, 2015 11:29 am

Sam wrote:However, RMIR on the XP is old, Version 8.03

That's not a valid version number, the current version is v2.03 build 12