 |
JP1 Remotes
|
| View previous topic :: View next topic |
| Author |
Message |
Sandlotje
Joined: 16 Jul 2019
Posts: 20
|
 Posted: Mon Mar 29, 2021 12:34 am Post subject: Total newbie trying to correct URC-7880 to RMIR |
 |
|
I have the JP1.2/3 Flash cable from DIYGADGET. This is the one. https://www.diygadget.com/jp1-2-1-3-flash-usb-cable-for-universal-remotes.
My device manager sees it, and says COM7.
I've installed Java and RMIR. Then I went to interfaces, chose auto-detect, and it says no remotes found.
What am I missing? Is it unable to see it because I've not downloaded and set a path for RDFs?
I've been trying to read directions, but I'm hours into it and I feel like I'm going in circles.
I'm on W10 if it matters.
Thank you so much. [/list] |
|
| Back to top |
|
 |
mathdon
Expert
Joined: 22 Jul 2008
Posts: 4523
Location: Cambridge, UK
|
| Posted: Mon Mar 29, 2021 6:22 am Post subject: |
|
|
It is nothing to do with downloading RDFs and setting a path for them. The RDFs are included in the RMIR download and the path to them is set by default. I suggest checking two things:
1. Do you have the latest version of RMIR? The current version is 2.12.8.
2. What does Device Manager > Ports say ? Under General tab, is the manufacturer FTDI? Under Driver tab, is the Driver Provider FTDI?
If these checks are OK and still no remotes found, close RMIR and then post the rmaster.err file, which you will find in your RMIR installation folder, in the Diagnosis area of our File Section and post a link to it in this thread.
_________________
Graham |
|
| Back to top |
|
|
Sandlotje
Joined: 16 Jul 2019
Posts: 20
|
| Posted: Mon Mar 29, 2021 10:04 pm Post subject: |
|
|
Hey there!
1. I checked, and I do have the latest version of RMIR you specified.
2. Dev mgr says Prolific USB-to-Serial Comm Port (Port 7).
I'll double check for the FTDI driver and see if I can find that particular one. in the meantime, here's my err file:
RMIR v2.12.8
Incorporates Girr v2.2.9
Girr Commit Id: ffb8129
Incorporates IrpTransmogrifier v1.2.8
IrpTransmogrifier Commit Id: 438b283
System Properties:
java.version = 1.8.0_281
java.vendor = Oracle Corporation
os.name = Windows 10
os.arch = amd64
java.home = C:\Program Files\Java\jre1.8.0_281
java.class.path = C:\Users\John\Downloads\RMIR.v2.12.8-bin\RemoteMaster.jar
Loading protocols from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\protocols.ini'
Option to include Slingbox protocols is Off
libraryFolder=C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64
LibraryLoader: Attempting to load 'jp12serial' from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp12serial.dll'...
LibraryLoader: Loaded 'jp12serial' successfully from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp12serial.dll'
JP12Serial version 0.25
LibraryLoader: Attempting to load 'hidapi' from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\hidapi.dll'...
LibraryLoader: Loaded 'hidapi' successfully from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\hidapi.dll'
CommHID version 1.2
Loading internal library JP2BT
JP2BT version 1.2
LibraryLoader: Attempting to load 'jp1usb' from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp1usb.dll'...
LibraryLoader: Loaded 'jp1usb' successfully from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp1usb.dll'
JP1USB version 0.04
Loading internal library JPS
JPS version 0.1
LibraryLoader: Attempting to load 'jp1parallel' from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp1parallel.dll'...
LibraryLoader: Loaded 'jp1parallel' successfully from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\jp1parallel.dll'
JP1Parallel version 0.12
JP1Parallel InpOutDriver is open
Using DecodeIR to decode Learned Signals
DecodeIR: Looking in 'C:\Users\John\Downloads\RMIR.v2.12.8-bin'.
LibraryLoader: Attempting to load 'DecodeIR' from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\DecodeIR.dll'...
LibraryLoader: Loaded 'DecodeIR' successfully from 'C:\Users\John\Downloads\RMIR.v2.12.8-bin\Windows-amd64\DecodeIR.dll'
Using IrpTransmogrifier as decoder of learned signals
Starting normal download
Interface Name = NULL
Port Name = NULL
Testing interface: JP1.X Serial
Port Name = NULL
Testing interface: CommHID
HIDManager com.codeminders.hidapi.HIDManager@1a82f0a4 devices are:
Device 0: HIDDeviceInfo [path=\\?\hid#vid_0a5c&pid_4502#8&288cd0ae&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=2652, product_id=17666, serial_number=null, release_number=256, manufacturer_string=null, product_string=null, usage_page=1, usage=6, interface_number=-1]
Device 1: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_01&col02#8&241220b4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=12, usage=1, interface_number=1]
Device 2: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_02#8&5464375&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=2, interface_number=2]
Device 3: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_001f&mi_00#8&1db3d20b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=31, serial_number=null, release_number=512, manufacturer_string=Razer, product_string=Razer Naga Epic, usage_page=1, usage=2, interface_number=0]
Device 4: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_01&col03#8&241220b4&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=128, interface_number=1]
Device 5: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_01&col04#8&241220b4&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=0, interface_number=1]
Device 6: HIDDeviceInfo [path=\\?\hid#vid_1462&pid_7c79#6&9bfb997&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5218, product_id=31865, serial_number=A02020021204, release_number=1, manufacturer_string=MSI, product_string=MYSTIC LIGHT , usage_page=1, usage=0, interface_number=-1]
Device 7: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_01&col05#8&241220b4&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=0, interface_number=1]
Device 8: HIDDeviceInfo [path=\\?\hid#vid_2687&pid_fb01&mi_01#8&30c81a20&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=9863, product_id=64257, serial_number=????????????????, release_number=256, manufacturer_string=Fitbit Inc., product_string=Fitbit Base Station, usage_page=65290, usage=1, interface_number=1]
Device 9: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_001f&mi_01#8&5f045c6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=5426, product_id=31, serial_number=null, release_number=512, manufacturer_string=Razer, product_string=Razer Naga Epic, usage_page=1, usage=6, interface_number=1]
Device 10: HIDDeviceInfo [path=\\?\hid#vid_051d&pid_0002#6&37cf2f04&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1309, product_id=2, serial_number=3B1711X16801 , release_number=144, manufacturer_string=American Power Conversion, product_string=Back-UPS NS1080G FW:914.L2 .D USB FW:L2 , usage_page=132, usage=4, interface_number=-1]
Device 11: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_01&col01#8&241220b4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=6, interface_number=1]
Device 12: HIDDeviceInfo [path=\\?\hid#vid_1532&pid_0228&mi_00#8&3ae2f2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=5426, product_id=552, serial_number=, release_number=512, manufacturer_string=Razer, product_string=Razer BlackWidow Elite, usage_page=1, usage=6, interface_number=0]
Device 13: HIDDeviceInfo [path=\\?\hid#vid_2687&pid_fb01&mi_00#8&cf0dc5e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=9863, product_id=64257, serial_number=????????????????, release_number=256, manufacturer_string=Fitbit Inc., product_string=Fitbit Base Station, usage_page=65290, usage=1, interface_number=0]
Device 14: HIDDeviceInfo [path=\\?\hid#vid_0a5c&pid_4503&col01#8&123da631&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=2652, product_id=17667, serial_number=null, release_number=256, manufacturer_string=null, product_string=null, usage_page=1, usage=2, interface_number=-1]
Device 15: HIDDeviceInfo [path=\\?\hid#vid_0a5c&pid_4503&col02#8&123da631&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=2652, product_id=17667, serial_number=null, release_number=256, manufacturer_string=null, product_string=null, usage_page=12, usage=1, interface_number=-1]
Failed to open remote
Port Name = NULL
Testing interface: JP1 USB
Port Name = NULL
Testing interface: JPS
Port Name = NULL
Testing interface: JP1 Parallel
Port Name = NULL |
|
| Back to top |
|
|
mathdon
Expert
Joined: 22 Jul 2008
Posts: 4523
Location: Cambridge, UK
|
| Posted: Tue Mar 30, 2021 5:40 am Post subject: |
|
|
Thank you for your further information. It looks as if the problem is that your cable uses a chip from Prolific rather than from FTDI. The announcement for RMIR v2.12 says:
| Quote: | | Remotes that use a Maxim processor can all be connected with a standard JP1.2/3 interface cable but only one that uses the FTDI chip. Cables with chips of other manufacturers such as Prolific have difficulty communicating with the Maxim processors. This is discussed in some detail in this thread. The most recent processors used by UEI are from Texas Instruments (TI). These can certainly be connected by JP1.2/3 cables with the FTDI chip. The situation with other chips is not yet known. |
The URC7880 uses the Texas Instruments processor. I think you are the first user to attempt to connect to a URC7880 with a cable that has the Prolific chip, so unfortunately it appears that, like remotes with a Maxim processor, those with a Texas Instruments processor also will not work with the Prolific chip.
I see that DIYGadget also sells a cable that does have the FTDI chip and they say about it "This version of cable is powered by FTDI chip, so it has better compatibility". That cable WILL work with the URC7880 but it costs $10 more than your present one. I suggest you contact DIYGadget and ask if they will exchange your cable for the FTDI one if you pay the $10 difference.
_________________
Graham |
|
| Back to top |
|
|
Sandlotje
Joined: 16 Jul 2019
Posts: 20
|
| Posted: Tue Mar 30, 2021 7:57 pm Post subject: |
|
|
| mathdon wrote: | Thank you for your further information. It looks as if the problem is that your cable uses a chip from Prolific rather than from FTDI. The announcement for RMIR v2.12 says:
| Quote: | | Remotes that use a Maxim processor can all be connected with a standard JP1.2/3 interface cable but only one that uses the FTDI chip. Cables with chips of other manufacturers such as Prolific have difficulty communicating with the Maxim processors. This is discussed in some detail in this thread. The most recent processors used by UEI are from Texas Instruments (TI). These can certainly be connected by JP1.2/3 cables with the FTDI chip. The situation with other chips is not yet known. |
The URC7880 uses the Texas Instruments processor. I think you are the first user to attempt to connect to a URC7880 with a cable that has the Prolific chip, so unfortunately it appears that, like remotes with a Maxim processor, those with a Texas Instruments processor also will not work with the Prolific chip.
I see that DIYGadget also sells a cable that does have the FTDI chip and they say about it "This version of cable is powered by FTDI chip, so it has better compatibility". That cable WILL work with the URC7880 but it costs $10 more than your present one. I suggest you contact DIYGadget and ask if they will exchange your cable for the FTDI one if you pay the $10 difference. |
Ah, I have been suspecting this to be the case after many hours of intense research and troubleshooting. Hopefully that solves my issues. I actually had already ordered it prior to reading the end of your post suggesting a possible exchange.. oh well..
Thank you so much for your help.  |
|
| Back to top |
|
|
mathdon
Expert
Joined: 22 Jul 2008
Posts: 4523
Location: Cambridge, UK
|
| Posted: Wed Mar 31, 2021 8:00 am Post subject: |
|
|
When you have your FTDI cable, please let us know if it works. We always like to know when a problem has been solved. Of course, if you still have problems then let us know about them too, so that we can try to resolve them.
_________________
Graham |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
File Section
Wiki
