Page 2 of 3
Posted: Thu Apr 06, 2006 1:53 pm
by SGordon
aberguerand wrote:I did not get from your postings whether you have actually been able to upgrade your remote via WAV file or not.
Hello.

Yes, I have been able to upgrade my remote via WAV file from the site. That is how I got the PVR functions for my DISH satellite receivers. However, I have other devices which I can't seem to put in via the site, and I would really like to create my own mappings if possible. I got the same remote for a friend and he has a number of devices that don't quite do what he wants from the site upgrades as well. Any and all help is definitely appreciated !
Posted: Thu Apr 06, 2006 2:27 pm
by The Robman
I've figured out the signature thing also. The "EML2" signature is for the European remotes. I was downloading the WAV files from the European site.
The "USM0" signature is for the US remotes.
US Downloads:
http://www.ezremote.com/cgi-bin/init.cg ... t=USMOSAIC
Europe Downloads:
http://www.ezremote.com/cgi-bin/initBV. ... t=EUMOSAIC
Posted: Thu Apr 06, 2006 9:56 pm
by aberguerand
The Robman wrote:Maybe we could develop an application that would take a text file which contains all the upgrades as input and creates the WAV file from it? There could be a few standard fields at the top of the file for things such as the signature and the fixed data, but the rest of the file could just be the upgrades in th standard format that we use to copy them from KM and RM over to IR.
What do you think Alain, is that something that you could put together?
That should be possible, I have to think about what the required fields are. The signature and the address of the ugrade area are certainly required. Do you see other ones ? Would some address translation be needed for the protocols ?
Of course this application will be limited to upgrade devices and protocols, the rest of the IR stuff (assignments, macros, VPT, etc.) will have to be done manually on the remote.
Posted: Thu Apr 06, 2006 10:07 pm
by The Robman
Take a look at the following file:
https://www.hifi-remote.com/forums/dload ... le_id=3025
It contains a WAV file that I downloaded along with a text file in the format that I was suggesting. This new program should be able to take that text file as input and re-create the WAV file.
Given that you already have an IRtoWAV program, all the program really needs to do is re-format the upgrades into an IR style file and feed the resulting file into IRtoWAV. I have also included the IR file in the zip.
Given that they are using a similar chip to the one used in the Slingbox, I don't think the "EEPROM" (or whatever is used) is used to hold macros, etc (they must be stored elsewhere) so it's not possible to program them via a WAV anyway.
Now that I think about it, we used to have a program that took upgrades in the format I just used and created an IR type file, it was called
asmdump, maybe we can make use of that?
Posted: Thu Apr 06, 2006 10:54 pm
by aberguerand
The Robman wrote:Take a look at the following file:
https://www.hifi-remote.com/forums/dload ... le_id=3025
It contains a WAV file that I downloaded along with a text file in the format that I was suggesting. This new program should be able to take that text file as input and re-create the WAV file.
Sorry to aks, but what is the use of these two fields ?
Code: Select all
fixed1="FF FF 45 4D"
fixed2="44 44"
Posted: Fri Apr 07, 2006 6:28 am
by The Robman
I was thinking that we'd use those to populate the two fixed areas as defined below...
The Robman wrote:The first 4 bytes are always "FF FF 45 4D"
The next 2 bytes are the total length of the all upgrades.
The next 2 bytes are always "44 44".
The next byte is the number of upgrades in the file.
This was just in case we discover that those two areas aren't really fixed and need to have different values sometimes.
Posted: Fri Apr 07, 2006 7:04 am
by aberguerand
Ok.
I don't think we need the first 4 bytes, as the WAV file will start at address $0004, so we will not overwrite them.
I was surprised to find that the code I had written supports the Mosaic, but then remembered we had some email exchanges back in october 2003...
Posted: Fri Apr 07, 2006 2:29 pm
by aberguerand
Rob,
I'm almost done with a quick Java application.
Instead of directly produce a WAV file, it will create an IR-like file that can be fed to IRToWav.
I am however stuck with the last two bytes that are supposed to be a checksum, but trivially adding all the upgrades bytes does not give the expected sum. Do you know how to compute it ?
Posted: Fri Apr 07, 2006 2:52 pm
by The Robman
Good catch, I hadn't noticed that there was a checksum at the end of the data. The formula is SUM 4:end, so for the mosaic2.txt file that I included, the SUM range is 4 thru 178
I have updated the sample file, I removed the 2 checksum bytes from the end of the last upgrade.
Posted: Sat Apr 08, 2006 1:42 am
by aberguerand
Actually the first byte is the sum of the upgrade bytes (modulo 256) and the second byte is the binary complement of the first one.
I have uploaded the above mentionned tool
here.
It creates an IR-like file from a text file containing codes and protocols. Look at the included readme and sample for the format of this file.
I have also included a batch file to directly create the upgrade WAV file.
Note that :
1. The tool does a minimal error checking on the structure of the input file and requires it to have the " " delimitors at the right place.
2. For upgrades that use non built-in protocols, the protocol definition must directly follow the upgrade code that uses it.
3. I do not have access to a Mosaic, so could not test whether the generated WAV files work correctly.
Posted: Wed May 31, 2006 6:20 pm
by SGordon
Wow ! Thanks guys !!
I'm sorry it's taken me so long to respond. Work and "real life" kept me busy for a while.
I have a spare Mosaic (I actually bought 3, one for me, one for a friend, and one to give my mother for Christmas), so I could send it to one of you guys for testing.
I'll have to play with what you've put up and see what I can figure out.
Cheers!
SGordon
Compatibility of upgrades between remotes?
Posted: Fri Jul 28, 2006 2:31 am
by David Lewis
I've been using JP1 for a few years on a URC-7562 with great success - thanks to everyone for making this possible!
I'm about to take delivery of a URC-9990 (OFA Mosaic). I know this isn't a JP1 remote, but I plan to use aberguerand's MosAsm program (and IRtoWav) to create any upgrades I need for the Mosaic.
What I don't yet know is whether I can simply cut and paste any Device Upgrades and Protocol Upgrades I've created for my URC-7562, and re-use them on the URC-9990? If not, is there some kind of conversion process I can follow (bearing in mind that the Mosaic isn't supported by RemoteMaster or IR)? I realise I won't be able to re-use my existing Macros and Key Moves, but what about my Upgrades?
Posted: Fri Jul 28, 2006 5:58 am
by johnsfine
I don't know anything about the 9990. But .wav files are very specific to the model of remote. If you don't have a correct .rdf file for the 9990, you won't get ir.exe to produce the data IRtoWav would need to create the .wav file.
Posted: Fri Jul 28, 2006 7:49 am
by David Lewis
johnsfine wrote:If you don't have a correct .rdf file for the 9990, you won't get ir.exe to produce the data IRtoWav would need to create the .wav file.
I know. That's why I'll be using MosAsm to create the data for IRtoWav, not ir.exe. It's described in the post I linked.
Posted: Fri Jul 28, 2006 8:21 am
by gfb107
You'll still need an RDF in order to get RM to generate a device upgrade for the 9990, which you can then import into MosAsm.