Automatically loading different IR Files?
deadken
Posts: 10
in AMX Hardware
Hello,
we work on systems for boats which travel all around the world and are always needing to change satellite receivers on the fly.
Our other systems (on hardware from a manufacturer which will remain nameless
) we have 17 satellite IR files stacked, and we simply enable the current satellite receiver. Even if we squeezed all the receivers down with no empty IR codes, we won't have enough room in a single IRL file.
Is there any way to tell the master to load an IRL file?
________
TOYOTA TSUSHO HISTORY
we work on systems for boats which travel all around the world and are always needing to change satellite receivers on the fly.
Our other systems (on hardware from a manufacturer which will remain nameless
) we have 17 satellite IR files stacked, and we simply enable the current satellite receiver. Even if we squeezed all the receivers down with no empty IR codes, we won't have enough room in a single IRL file.Is there any way to tell the master to load an IRL file?
________
TOYOTA TSUSHO HISTORY
0
Comments
I've never tried this, but I don't see why you couldn't ftp them to the master. They need to be named correctly like irfile09, irfile10, etc but I can't see why it wouldn't work unless the master does something to it other than renaming it.
Paul
Shame. Did you try loading 8 IR files to the master, then copying them to a different folder on the master, then loading another 8 different IR files? Using the file_copy method you could then just copy them back into the irfile09 files dynamically as needed. That's the only other thing I can think of that might work.
Paul
Ok, now I'm interested. Can you provide any more specifics? I suppose if you were to impliment icsp in a duet module you could get the master to connect to itself on port 1319 and emulate what file transfer / IREdit does.
I think you could be on to something with the ICSP connection, but then you've gotta figure out the ICSP transfer protocol. Probably not fun.
I believe this was prior to the encryption of ICSP, which will present another issue if it's turned on.
P.S. - did you notice what is NOT listed in the file types? Netlinx token.
re: tkn's, I'm guessing they may either be ftp'ed or it was simply ommitted in that version of the doc. Would be interesting to WireShark a transfer and see what's happening.
Surely there've been modifications within that 3 year period, let alone now.
By the time you've got today's protocol, they'll have a different protocol out and this will be obsolete. Of course, you can always sniff it with Wireshark.
Edit: sans encryption. Don't know if this would be a concern.
Yeah, the whole idea isn't that difficult really. I may ACTUALLY work on it tonight to see if I can get it going.
Kevin D.
I know. But you could easily fit 4 sets of codes into one file.
Hence the "worse case" part of my reply.
What about a Global cache unit? Store all IR timings on the master and send them as needed. No limit on the number of channels as the timing can be dynamic.
Kevin D.
I haven't tried this from a program but using FT2's command line is no big deal.
Just a thought.
Side detail-
The IR files you see in FTP in the NetLinx are created when you upload an IRL to an IR bank. They are not interactive, as mentioned, you can't affect the bank by changing or removing the "IR" file you see in the FTP view.
What they ARE for is to store the metadata that is in the uploaded IRL file, but isn't stored in the IR bank. This allows you to extract/download the IR file later, intact, using IREDIT. If you delete or change the FTP-side file, you won't be able to extract the IRL. It will still work with or without any of the FTP-viewable IR files.