AXB-IRS4 Downloading IR file from port.

Pep_SD

I'm having my hands on this exisiting old system with NI3000 and a couple of AXB-IRS4.
We're moving IR around and equipment, so I wanted to first download each IR file before moving stuff around...
Well turns out that every download I tried on 8 different ports just failed.
Using Netlinx Studio I can upload correctly a new file, but can't get any download. Is it normal behavior? Any special trick?
I go to "Tools/File Transfer", "Receive" tab, select IRL/IRV File, enter a file name then enter Device:Port:system - for instance 80:1:1 - and launch it.
Takes a couple of seconds then I get the Red cross and Failed message.
Any idea?

Auser

Try retrieving the file with IREdit instead of NetLinx Studio. I have seen this behaviour before and believe that something in the format of IR information changed at some point in time meaning that NetLinx Studio won't retrieve IR files that were sent to a device in the distant past.

If you can't retrieve the IR files with IREdit, it's probable that you'll be able to get them with the old Axcess vintage DOS tools.

John Nagy

Use IREDIT, it has a wizard that walks you through making a database, from which you can save individual IRL files. This should work fine for the IRS4's.

Depending on the firmware level of the NetLinx when the IR was uploaded to it, it may not play nice. For a number of years now, when you upload IR to a port on the NetLinx, it also creates a metafile in the FTP files area named "irfile[#]" with the # being the port number. This is NOT the IR file, only the labels for it. If the irfile is missing or corrupted, you will be unable to extract the IRL from the port, it will fail when it can't match the data in a irfile[#]. You can see the files via FTP, but you can't fake in ones from another set and make it download. It might come down but it will not work. Also note that the files look ASCII to FTP programs, but if they download as ASCII rather than BINARY, which can happen if the FTP is set to AUTO, the files will be corrupted in transit. If you look at the result, they are all truncated and lose their metadata. If you download them BINARY, you can upload them again and they will stay intact. Note further that the irfiles are of no use by themselves, only when in place correctly corresponding to the IRL loaded in its matching port.

Your other choice is to manually recapture the IR in each port by use of an IRIS, pulsing each port on each channel and saving it as a new file. Tedious.

Pep_SD

Thank you all!

Yes, the use of IREdit did the treak - just one thing, all functions in the IR file appear as F1, F2, .. Fn for the corresponding code (1, 2,... n).
Not really pretty to use since now you don't know what is what...
But in my case, it will do the trick until I redo the system.

Thank you again John and Auser.

pdabrowski

Pep_SD wrote: »

just one thing, all functions in the IR file appear as F1, F2, .. Fn for the corresponding code (1, 2,... n).
Not really pretty to use since now you don't know what is what...

One of the few side effects of downloading from the device IMO, but generally if you look at a similar device IRL file the function labels will be very similar.
Or grab a copy of the AVT database http://www.amxforums.com/showthread.php?6171-AMX-Australia-IR-Zip which has been my go-to place for IR files since starting.