RMIR remote not found - EEPROM adapter works on term program

KJaget · Post by **KJaget** » Sun Feb 21, 2021 5:26 pm

I'll try to include all the info I can.

I'm getting "No Remotes Found" when trying a raw download in RMIR 2.12.8. Same result with "download from remote".

I'm using an FDTI USB serial hooked up to a JP1 eeprom adapter. USB serial is this one https://www.ebay.com/itm/152712195878 The remote is an 8910B02 I programmed a while back using KM2.17 and IR 8.x with a parallel port, but since my win xp box died I'm trying to upgrade to something more modern.

The weird thing is I can open a term program and talk to the eeprom adapter. I can set it to 38.4K 8N1, and hit ? a few times and see a menu

Code: Select all

JP1 EEPROM Programming Adapter
Copyright 2010 Kevin Timmerman
Rev 003 Config 08 1
d Display EEPROM contents 
...

Using 'd' to display EEPROM contents gives some sort of data, not sure if it is valid but it isn't all FF or 00, so I have some hope

Code: Select all

d
A0 0 00 0 A1 0 
0000: EE 11 43 50 54 30 43 50 54 30 04 24 10 68 86 0E
0010: 75 61 90 B9 21 F7 A4 57 07 DD 00 2F 10 3C 21 F7
0020: 30 3B 40 F3 50 9E 61 DC 04 06 FF 03 06 03 03 00
0030: FF 00 14 00 00 00 00 00 00 00 13 83 90 B9 14 30
0040: C4 A4 57 F3 20 14 C4 A4 57 DE 20 13 C4 A4 57 1B
0050: 22 37 C4 A4 57 AA 20 25 C4 A4 57 FF 22 26 C4 A4
0060: 57 3F 22 27 C4 A4 57 9F 22 28 C4 A4 57 6F 22 3E
0070: C4 A4 57 47 20 3F C4 A4 57 87 20 25 63 75 61 41
0080: 26 63 75 61 43 27 63 75 61 42 28 63 75 61 44 3F
0090: 63 75 61 81 25 03 04 24 C9 26 03 04 24 D7 27 03
00A0: 04 24 57 28 03 04 24 97 3E 03 04 24 66 3F 03 04
00B0: 24 E6 94 03 04 24 2D B7 03 04 24 E5 2D 03 04 24
00C0: 93 0C 03 04 24 CE 10 03 04 24 36 AE 16 01 3E 22
00D0: 3E 11 03 2F 18 01 3F 23 30 22 3F 11 3F 24 13 22
00E0: 25 11 12 13 22 26 11 2E 16 23 03 22 3E 11 03 2A
00F0: 03 04 24 82 29 03 04 24 68 00 E3 07 DD 76 00 0E
0100: 03 7A 03 94 62 00 FE FE FE F1 C3 11 01 02 03 04
0110: 05 06 07 08 09 00 00 27 0D 0E 10 0F 2E 21 22 23
0120: 24 25 20 28 26 37 36 13 30 32 33 34 31 35 12 2A
0130: 27 00 BE FE FE FF 92 5B 00 00 90 59 00 59 80 59
0140: 40 59 C0 59 20 59 A0 59 60 59 E0 59 10 59 8C 59
0150: 0C 59 A8 5B 58 59 14 59 9E 59 5E 59 DE 59 3E 59
0160: D0 59 D8 59 2A 59 F0 59 8C 59 0C 59 86 59 4C 59
0170: 9C 59 CC 59 2C 59 1C 59 68 5B 06 59 26 59 14 59
0180: A6 59 C6 59 CA 00 A8 66 F1 88 88 00 00 02 82 42
0190: C2 22 00 00 00 00 8C 0C 96 7C BA 34 4C 9C CC 2C
01A0: 1C 5A 18 7E FE FD 31 1F 1F 1F 2F 0F B7 F7 BF A7
01B0: 7F 37 F9 79 59 B9 E9 3F 07 4B FB BD 83 29 3B 1A
01C0: 00 FE F8 07 A1 5E 81 7E 01 7F FF 00 B2 20 58 20
01D0: 98 20 18 20 E8 20 68 20 A8 20 28 20 C8 20 72 20
01E0: A7 20 27 20 C7 20 79 A2 D9 A2 AB 60 29 22 46 20
01F0: C6 20 06 20 86 20 84 20 32 20 07 22 4E 20 6E 20
0200: 5A 00 D8 FE 8D 21 3E 55 23 31 11 46 06 2E 3E 3B
0210: 0E AA 00 00 4A F6 A6 F2 B2 32 72 5E 76 36 DE 63
0220: 5E 40 84 11 8B 15 00 01 2C 01 18 01 2C 02 44 02
0230: 58 01 18 02 58 02 44 0B B8 02 44 B0 0C 68 03 37
0240: 64 0B E6 0E 2C E6 0F 5D F6 01 55 8B 0C 37 62 09
0250: E6 0E 43 E6 0F 8A F6 01 55 F6 FF 91 1C 22 F6 01
0260: 4C 38 03 F6 FF 7A 38 04 F6 FF 76 38 05 F6 FF 7A
0270: 1C 12 F6 01 64 37 60 07 C6 F8 29 04 F6 01 58 C6
0280: F8 11 94 F6 01 58 76 0C 01 EB 06 C6 22 05 DC 20
0290: 0C F6 01 0A 7B C6 AF 4C 04 8B 02 4C 02 90 C3 90
02A0: C3 08 C3 56 C0 03 86 04 C0 06 C1 12 F6 01 4C 4A
02B0: EC AF C6 08 01 03 C6 0A 05 07 B0 C0 B0 C2 38 04
02C0: 48 C3 56 C4 03 87 50 08 02 24 5A FC E0 C3 E0 C3
02D0: 0E 37 04 EC F0 C2 29 05 AF 3A 8A 42 8B 15 F8 15
02E0: 05 07 02 58 01 18 01 2C 01 18 57 D0 04 B0 01 18
02F0: 08 03 08 76 07 01 EB 17 76 08 01 6B 0F E6 28 F9
0300: E6 12 08 08 08 E0 C0 56 C0 03 09 01 E6 24 05 8D
0310: 01 49 43 8B 82 8B 14 CF 44 08 08 01 18 01 06 01
0320: 18 03 39 D2 DC 11 94 08 B6 08 CA E6 10 02 08 0C
0330: 18 C0 56 C1 C0 F0 C1 E0 C1 06 C1 03 93 C1 03 E5
0340: C1 04 E4 0B 05 E4 0B 06 60 06 37 02 03 B6 06 01
0350: 37 06 05 F6 01 04 7B 09 37 09 0C 37 01 03 46 29
0360: 0D 46 29 01 8D 01 49 C4 22 1E 37 01 EE F6 01 49
0370: E6 28 C1 60 03 E6 12 01 8B E7 00 06 7D 61 8E 0E
0380: 90 B9 04 24 AC 57 07 DD 01 04 01 30 01 84 01 A1
0390: 01 BF 02 00 00 03 01 62 01 27 01 1A 02 21 02 D9
03A0: 03 12 90 B9 04 24 AC 57 01 04 01 30 01 71 01 C5
03B0: 01 E2 02 00 00 03 01 62 01 1A 01 27 02 41 02 F9
03C0: 03 61 03 63 43 23 46 23 54 23 EE 23 FC 01 04 01
03D0: 24 01 42 01 63 01 86 01 B1 01 CF 01 EF 02 0F 02
03E0: 31 02 56 02 74 02 9B 02 C2 02 E9 03 10 03 38 03
03F0: 5E 00 01 01 6A 03 86 00 00 00 00 00 00 00 FF 00
0400: 00 00 1B 00 C8 04 01 2C 35 EE 04 B0 01 2E 02 58
0410: 01 2D 01 2C 01 2C 8D 13 33 32 33 23 33 00 26 00
0420: 1B 00 C8 04 01 2C 35 EE 04 B0 01 2E 02 58 01 2D
0430: 01 2C 01 2C 8D 13 33 32 33 23 33 00 27 00 1B 00
0440: C8 04 01 2C 35 EE 04 B0 01 2E 02 58 01 2D 01 2C
0450: 01 2C 8D 13 33 32 33 23 33 00 28 00 1B 00 C8 04
0460: 01 2C 35 EE 04 B0 01 2E 02 58 01 2D 01 2C 01 2D
0470: 8D 13 33 32 33 23 33 00 00 FF FF FF FF FF FF FF
0480: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

It's FF all the way down from there.

RMIR rmaster.err is this

Code: Select all

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 = x86
   java.home = C:\Program Files (x86)\Java\jre1.8.0_281
   java.class.path = RemoteMaster.jar

Loading protocols from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\protocols.ini'
Option to include Slingbox protocols is Off

libraryFolder=C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86
LibraryLoader: Attempting to load 'jp12serial' from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp12serial.dll'...
LibraryLoader: Loaded 'jp12serial' successfully from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp12serial.dll'
    JP12Serial version 0.25
LibraryLoader: Attempting to load 'hidapi' from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\hidapi.dll'...
LibraryLoader: Loaded 'hidapi' successfully from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\hidapi.dll'
    CommHID version 1.2
Loading internal library JP2BT
    JP2BT version 1.2
LibraryLoader: Attempting to load 'jp1usb' from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp1usb.dll'...
LibraryLoader: Loaded 'jp1usb' successfully from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp1usb.dll'
    JP1USB version 0.04
Loading internal library JPS
    JPS version 0.1
LibraryLoader: Attempting to load 'jp1parallel' from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp1parallel.dll'...
LibraryLoader: Loaded 'jp1parallel' successfully from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\jp1parallel.dll'
    JP1Parallel version 0.12
    JP1Parallel InpOutDriver is open
Using DecodeIR to decode Learned Signals
DecodeIR: Looking in 'C:\Users\Kevin\Documents\JP1\RM2.17.8'.
LibraryLoader: Attempting to load 'DecodeIR' from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\DecodeIR.dll'...
LibraryLoader: Loaded 'DecodeIR' successfully from 'C:\Users\Kevin\Documents\JP1\RM2.17.8\Windows-x86\DecodeIR.dll'
Using IrpTransmogrifier as decoder of learned signals
Starting raw download
Interface Name = JP1.X Serial
Port Name = COM3
Testing interface: JP1.X Serial
Interface matched.  Trying to open remote
Port Name = NULL
Failed to open
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@41f216 devices are:
Device 0: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col01#9&3345ce1f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=6, interface_number=1]
Device 1: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col01#9&28287e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=16, interface_number=-1]
Device 2: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_00#9&f6e905d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=2, interface_number=0]
Device 3: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col02#9&28287e8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=204, interface_number=-1]
Device 4: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col02#9&3345ce1f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=12, usage=1, interface_number=1]
Device 5: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col03#9&3345ce1f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=128, interface_number=1]
Device 6: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col04#9&3345ce1f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=1, interface_number=1]
Device 7: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col05#9&3345ce1f&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=2, interface_number=1]
Device 8: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c232#2&8478db6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49714, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=6, interface_number=-1]
Device 9: HIDDeviceInfo [path=\\?\hid#vid_04b3&pid_3005#a&2a836ed1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1203, product_id=12293, serial_number=null, release_number=256, manufacturer_string=Silitek, product_string=IBM USB HUB KEYBOARD, usage_page=1, usage=6, interface_number=-1]
Device 10: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c231#2&1d9ea34b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49713, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=2, interface_number=-1]
Device 11: HIDDeviceInfo [path=\\?\hid#vid_8086&pid_0808&mi_02#a&957a752&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=32902, product_id=2056, serial_number=null, release_number=256, manufacturer_string=C-Media Electronics Inc.      , product_string=USB PnP Sound Device, usage_page=12, usage=1, interface_number=2]
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
Starting raw download
Interface Name = NULL
Port Name = NULL
Testing interface: JP1.X Serial
Port Name = NULL
Testing interface: CommHID
HIDManager com.codeminders.hidapi.HIDManager@41f216 devices are:
Device 0: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col01#9&3345ce1f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=6, interface_number=1]
Device 1: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col01#9&28287e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=16, interface_number=-1]
Device 2: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_00#9&f6e905d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=2, interface_number=0]
Device 3: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col02#9&28287e8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=204, interface_number=-1]
Device 4: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col02#9&3345ce1f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=12, usage=1, interface_number=1]
Device 5: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col03#9&3345ce1f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=128, interface_number=1]
Device 6: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col04#9&3345ce1f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=1, interface_number=1]
Device 7: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col05#9&3345ce1f&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=2, interface_number=1]
Device 8: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c232#2&8478db6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49714, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=6, interface_number=-1]
Device 9: HIDDeviceInfo [path=\\?\hid#vid_04b3&pid_3005#a&2a836ed1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1203, product_id=12293, serial_number=null, release_number=256, manufacturer_string=Silitek, product_string=IBM USB HUB KEYBOARD, usage_page=1, usage=6, interface_number=-1]
Device 10: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c231#2&1d9ea34b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49713, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=2, interface_number=-1]
Device 11: HIDDeviceInfo [path=\\?\hid#vid_8086&pid_0808&mi_02#a&957a752&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=32902, product_id=2056, serial_number=null, release_number=256, manufacturer_string=C-Media Electronics Inc.      , product_string=USB PnP Sound Device, usage_page=12, usage=1, interface_number=2]
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
Starting raw download
Interface Name = NULL
Port Name = NULL
Testing interface: JP1.X Serial
Port Name = NULL
Testing interface: CommHID
HIDManager com.codeminders.hidapi.HIDManager@41f216 devices are:
Device 0: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col01#9&3345ce1f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=6, interface_number=1]
Device 1: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col01#9&28287e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=16, interface_number=-1]
Device 2: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_00#9&f6e905d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=2, interface_number=0]
Device 3: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col02#9&28287e8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=204, interface_number=-1]
Device 4: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col02#9&3345ce1f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=12, usage=1, interface_number=1]
Device 5: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col03#9&3345ce1f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=128, interface_number=1]
Device 6: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col04#9&3345ce1f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=1, interface_number=1]
Device 7: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col05#9&3345ce1f&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=2, interface_number=1]
Device 8: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c232#2&8478db6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49714, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=6, interface_number=-1]
Device 9: HIDDeviceInfo [path=\\?\hid#vid_04b3&pid_3005#a&2a836ed1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1203, product_id=12293, serial_number=null, release_number=256, manufacturer_string=Silitek, product_string=IBM USB HUB KEYBOARD, usage_page=1, usage=6, interface_number=-1]
Device 10: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c231#2&1d9ea34b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49713, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=2, interface_number=-1]
Device 11: HIDDeviceInfo [path=\\?\hid#vid_8086&pid_0808&mi_02#a&957a752&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=32902, product_id=2056, serial_number=null, release_number=256, manufacturer_string=C-Media Electronics Inc.      , product_string=USB PnP Sound Device, usage_page=12, usage=1, interface_number=2]
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
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@41f216 devices are:
Device 0: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col01#9&3345ce1f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=6, interface_number=1]
Device 1: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col01#9&28287e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=16, interface_number=-1]
Device 2: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_00#9&f6e905d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=2, interface_number=0]
Device 3: HIDDeviceInfo [path=\\?\hid#vid_048d&pid_8297&col02#9&28287e8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1165, product_id=33431, serial_number=null, release_number=3, manufacturer_string=ITE Tech. Inc., product_string=ITE Device(8595), usage_page=65417, usage=204, interface_number=-1]
Device 4: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col02#9&3345ce1f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=12, usage=1, interface_number=1]
Device 5: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col03#9&3345ce1f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=1, usage=128, interface_number=1]
Device 6: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col04#9&3345ce1f&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=1, interface_number=1]
Device 7: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c08c&mi_01&col05#9&3345ce1f&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49292, serial_number=037938563538, release_number=10242, manufacturer_string=Logitech, product_string=G PRO Gaming Mouse, usage_page=65280, usage=2, interface_number=1]
Device 8: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c232#2&8478db6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1133, product_id=49714, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=6, interface_number=-1]
Device 9: HIDDeviceInfo [path=\\?\hid#vid_04b3&pid_3005#a&2a836ed1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd, vendor_id=1203, product_id=12293, serial_number=null, release_number=256, manufacturer_string=Silitek, product_string=IBM USB HUB KEYBOARD, usage_page=1, usage=6, interface_number=-1]
Device 10: HIDDeviceInfo [path=\\?\hid#vid_046d&pid_c231#2&1d9ea34b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=1133, product_id=49713, serial_number=null, release_number=1, manufacturer_string=null, product_string=null, usage_page=1, usage=2, interface_number=-1]
Device 11: HIDDeviceInfo [path=\\?\hid#vid_8086&pid_0808&mi_02#a&957a752&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vendor_id=32902, product_id=2056, serial_number=null, release_number=256, manufacturer_string=C-Media Electronics Inc.      , product_string=USB PnP Sound Device, usage_page=12, usage=1, interface_number=2]
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

Post by **The Robman** » Sun Feb 21, 2021 8:23 pm

I think the most important thing for us to confirm is, did you connect the adapter correctly? I can't tell from the listing what each of the 6 pins are connected to, but I do see that it has RTS, GND, TXD and RXD ports on the board, so if any of those aren't connected to a pin, you'll need to connect to the port itself.

Then on the remote end, you'll need to connect them as follows:
pin - type
1 - (empty)
2 - RTS
3 - GND
4 - TXD
5 - (empty)
6 - RXD

3FG · Post by **3FG** » Sun Feb 21, 2021 9:20 pm

The first 10 bytes of the EEPROM dump are EE 11 43 50 54 30 43 50 54 30. The first 2 are the check sum (adds to FF) and the next 8 when converted from hex to ASCII are CPT0CPT0 which is the signature of the 8910. So I think this tells us the adapter does work.

I would attach the cable and adapter to the remote, use the terminal program to ensure that you can dump the EEPROM, and without disconnecting the adapter or cable run RMIR. Assuming that RMIR can't find the remote, rerun the terminal program and verify that it still can dump. Also, I see that RMIR is trying to use COM3. Is that the port you're using with the terminal program?

KJaget · Post by **KJaget** » Mon Feb 22, 2021 6:51 am

Thanks for the quick responses.

I believe I have the adapter hooked up correctly. Looking at the pin-out from the ebay listing, I have :

Red wire： 5V
Black wire： GND
White wire： RXD
Green wire： TXD
Yellow wire： RTS
Blue wire： CTS

And the adapter is wired with

Pin 1 - nc
pin 2 - yellow
pin 3 - black
pin 4 - green
pin 5 - nc
pin 6- white

Given I have comms using a terminal program, that at least points to rx, tx and gnd being correct.

The term program is set up for COM3, which also agreed with the device in device manager. I did try to auto-detect but got the same "No remotes found!" message. But thanks for the reminder there to watch out if the com port moves next time I replug or reboot.

For the test mentioned by 3FG, I tested I could dump the eeprom using a term program, then started up RMIR. I tried a raw download and got "No remotes found!". I then went back to the term program and it took sending a few dozen ?'s before the menu showed up. And before it did, the adapter sent 0xFA 0xFF, not sure of the significance.

I've read that battery level might make a difference, could that be the case here? Also, the RTS pin seems like a potential suspect, just because I haven't been able to test it yet. I'll try to put a meter on it this morning.

Post by **The Robman** » Tue Feb 23, 2021 8:54 am

Have you made any progress? And just out of curiosity, have you tried the old IR.exe to see if that can connect?

KJaget · Post by **KJaget** » Tue Feb 23, 2021 11:37 am

I haven't had a chance to to much extra debug on it, hope to have some time tonight.

I have tried IR8.04, but as a random "let's see if anything works". It didn't but I don't have any really controlled tests using it so I wouldn't read too much into that.

KJaget · Post by **KJaget** » Thu Feb 25, 2021 4:52 pm

OK, another attempt, this time with an Adafruit CP2104 adapter ( https://www.adafruit.com/product/3309 )

Same results as before. I can dump the remote using a term program, but immediately switching to RMIR, I still get "No remotes found!".

With the CP2104 board I have (limited) LED diagnostics and there is a difference. Using the term program, I get a few blinks of the TX LED followed by lots of RX LED blinks as data is displayed in the terminal. Using RMIR, I see 2 slow followed by 3 fast LED blinks on TX, then nothing on the RX led (I'm not convinced these correspond to any particular number of bytes, but there is a consistent pattern at least).

I guess this at least confirms RMIR is sending something to the adapter?

I did try some more systematic testing with IR8.04. Remote->download from remote gives a pop up error of "Jp12 read failed 0." The adapter shows 5 blinks of TX, 2 slow then 3 faster ones. Similar to the RMIR pattern just a bit slower.

Not sure if there are debugging builds or switches for the comm libraries but I'm game to try them if they exist.

Post by **The Robman** » Thu Feb 25, 2021 6:19 pm

I added the missing rows of FFs and saved your EEPROM dump as a valid IR file, which can be opened using either IR.exe or RMIR, so that does indeed prove that you're able to download using your term. I have no idea why you can't get IR or RMIR to download though.

https://www.hifi-remote.com/forums/dload ... e_id=26247

KJaget · Post by **KJaget** » Thu Feb 25, 2021 6:23 pm

I've found the source for jp12serial, and am downloading mingw now. I'll see what I can find after building a version with debug output.

mdavej · Post by **mdavej** » Thu Feb 25, 2021 6:30 pm

FWIW, auto detect hasn't worked for me for many years and often crashes RMIR immediately. I always have to pick the comm port manually.

Have you tried it without batteries?

KJaget · Post by **KJaget** » Thu Feb 25, 2021 6:44 pm

I have tried with and without batteries, and with a new vs. used but still working set. I didn't see any differences.

And I have switched back and forth between autodetect and COMx a few times. Autodetect never crashed on me, but none of the permutations worked, either.

One guess I'm working from now - the eeprom adapter's rts->reset line isn't connected. That would explain why it eventually works with enough ?s from the serial port, and also why it seems to be in a weird state after running rmir. For the latter, it could be all the other attempts to identify it as other interfaces before falling through to the test for it being an eeprom adapter put it in a bad state, and since reset isn't hooked up it doesn't respond because it is in some random state. If true, I think I can hack around it.

BTW - I genuinely appreciate all the help. Double checking my assumptions and confirming the things I did find have saved a lot of time so far. Fingers crossed we're getting closer to the bottom of this.

Post by **The Robman** » Thu Feb 25, 2021 9:25 pm

Do you have any JP1.x remotes? I think it might be interesting to know if your cable setup works without the EEPROM adapter, which would require trying it with a JP1.x remote. Do we have any proof that the adapter works, or has ever worked? I see that when you originally programmed your URC-8910, you were using a parallel port. Of course, you are able to get it to work with Term, which adds to the confusion. We have hundreds of people using FTDI cables with RMIR with no problem, though we probably don't have so many people using the adapter, but I still have plenty of old JP1 remotes and I use one, so I can verify that mine works. But that's the only variable that I can think of, other than perhaps you having some non-standard driver loaded for something?

Post by **mathdon** » Fri Feb 26, 2021 7:21 am

mdavej wrote:FWIW, auto detect hasn't worked for me for many years and often crashes RMIR immediately. I always have to pick the comm port manually.

I have never heard of that happening before, and certainly AutoDetect always works for me. The rmaster.err file from a crash might be interesting, if you can post one. Apart from that, I'm afraid I have no suggestions to contribute to this thread.

Post by **mathdon** » Fri Feb 26, 2021 8:22 am

I have just done the closest test I can to your situation. It is Windows 10 with 32-bit Java 8, a JP1.2/3 USB cable with an EEPROM adapter on a URC-8550, the only JP1 remote that I have. It downloaded perfectly, with the interface set to Auto-detect. The cable and EEPROM adapter are early Tommy Tyler ones, which will be different from yours but should be functionally equivalent, so I can see no reason why your setup does not work.

I see that you are going to rebuild JP12serial from source and put in some debugging. I suspect there may be sources for old versions still around, so to remove any ambiguity, the source of jp12serial as included in RMIR v2.12.8 is here on SourceForge. The Windows binaries were built with MS Visual Studio 2017 Community Edition (which is the free version.)

Edit: Correction - the 64-bit binary was built with MS Visual Studio 2017, the 32-bit binary was built under Windows XP with MinGW as described in the source. This was to ensure backward compatibility as far as WinXP, but MS Visual Studio 2017 can compile the 32-bit version as well. I have not tried MinGW under Windows 10.

KJaget · Post by **KJaget** » Fri Feb 26, 2021 1:33 pm

It looks like there might be something wrong with the eeprom adapter.

What I saw from the jp12serial debug info was that early checks for a jp2_14 setup were sending data, and this seemed to cause the eeprom adapter to ignore input for a while. If I repeatedly did a raw download, it would succeed every so often as the additional data sent would wake the eeprom adapter back up at the right time.

I hacked up a version of jp12serial which doesn't do the initial jp2_14 check, and everything now works. With that function removed, the only thing jp12serial sends is commands understood by the eeprom adapter, it now never gets in a bad state. Or if it does, it is at least infrequent enough that I can work around it.

If I had to guess, I'm sticking with my guess is that the rts->reset connection in the eeprom adapter is broken.

oh, just refreshed and saw the last 2 posts. I was able to build the .dll using mingw x64, and it worked with no real issues (aside from the normal spaces in directories from the command line normal Windows weirdness).

And to be extra clear, I just commented-out the call to jp2_14Connect near the top of openPort plus the following check for flagAbort and everything started working. From the debug traces, everything in the subsequent init code is just pulling DTR/RTS until it gets to the 'E' request, which the eeprom adapter understands?

Again, I don't think this is anything wrong with the code, but it does work around the issues I'm seeing with my hardware.