writeRemote returned -5

avidgamr · Post by **avidgamr** » Mon Jul 22, 2019 4:00 am

What the heck does this mean? Sometimes I see this error message when I try to upload (to my JP1 remote with RMIR 2.03 Alpha 28 build 16; yes it's old but there's a reason I still use it). If I try again all goes fine.

mdavej · Post by **mdavej** » Mon Jul 22, 2019 1:36 pm

You mean "-1"? Could be lots of things, low batteries, failing interface, poor connection, port not found, corrupt memory, corrupt file, etc. Just have to try to eliminate one thing at a time. I'd start by changing interface detection from auto to actual comm port, then put in fresh batteries. Failing that, try a 981 reset on the remote before your next download (deactivate extender first).

What's the reason you have to use an older version of RMIR? I'm sure Graham would rather see a bug report that he can fix than have users running older versions that he can't support.

avidgamr · Post by **avidgamr** » Tue Jul 23, 2019 4:34 am

No, I actually mean -5.
https://www.hifi-remote.com/forums/dload ... e_id=25631

mdavej · Post by **mdavej** » Tue Jul 23, 2019 9:35 am

If you can't upgrade to the latest version, at least download it and replace your jp12serial and jp1usb files with the versions from the latest complete install package. Those contain fixes that are possibly related to your issue.

avidgamr · Post by **avidgamr** » Tue Jul 23, 2019 4:37 pm

I have upgraded to 2.08 b1 and
I still get the same error. If I could take a screenshot of the "about" along with the error message as proof I would but the program will not allow it.
Oh well. Forget it.
https://www.hifi-remote.com/forums/dload ... e_id=25632

Post by **The Robman** » Tue Jul 23, 2019 4:44 pm

see this thread for info on how to post images:
https://www.hifi-remote.com/forums/viewtopic.php?t=6557

mdavej · Post by **mdavej** » Tue Jul 23, 2019 5:29 pm

Your rmaster.err file might have some more clues. Please post that.

It's not that we demand proof. We just want information to help us diagnose. The error message doesn't mean much more to me than it does to you. We've never seen "-5", which is why I wanted you to confirm it wasn't a typo.

Post by **mathdon** » Wed Jul 24, 2019 7:10 am

I see that it is a JP1 remote you are using, so you may be using a JP1 interface cable with a Delcom chip. There are adapters to allow these remotes to be programmed with a JP1.x cable with an FTDI chip, but I think it likely that you are using a JP1 cable. If so, RMIR calls the jp1usb dll rather than the jp12serial dll. Both these dlls have recently been upgraded, as mdavej has pointed out. The upgrade to v0.24 of the jp12serial dll is included in the build 1 of RMIR v2.08 that you already have but that to v0.04 of the jp1usb dll needs an upgrade to the current development build of RMIR v2.08, which is build 5. That upgrade is available in the RMIR Development folder.

If you are using a JP1 interface cable then please install this upgrade to your RMIR v2.08 installation. I do not know if it will resolve this issue, but even if it does not, that failure will in itself give us useful info towards diagnosing this mysterious error message.