Hope someone can help...I'm getting this message when downloading to an msc40: You are connected to an RF1WAY-Micom version 1.02.001.007, if you need to set two RFID# for an MX-950 or MX-3000 , you must use an RF1WAY-Micom version 1.02.001.009. However, if oyu are using an MX-900 or TX-1000 , you can simply use RFID#s from ID#10 to 1F to address IR outputs 7-12

I get this whentrying to set a secondary rf id to enable access to ir ports 7-12 on an MX-3000.

In the mx editor, I can''t choose an rf id greater than 0F, so am limited to using two rf id's in the mx-3000 editor. In the MSC editor, if I choose any rf id 0F and below only emitter 1-6 are enabled.

I've tried testing various configurations but can not any emotters on ports 7-12 to flash.

Please, anyone have any help?

I have the registered live update versions of the mx-3000 editor and msc-400 editor. I purchased from Damon at ProRemotes.com several years ago.

Thanks!
Jim

I know I can use smart macros from the devices as configured in the MSC-400, and drop those on the buttons in the file in the MX-3000 editor via universal browser, but wanted to use the pass-thru capability to send IR commands from the devices configured in the MX3000

Any ideas? Can I update the firmware in the MSC-400 to 1.02.001.009? I have Live Updated the MSC-400 editor, and uploaded to the controller, but no luck.

I would like to know about the firmware update too. I have noticed this on my MSC-400 (the firmware is the older version too).

Anybody?

Ports 7-12 are combination RS232 or IR ports. If you are using IR emitters on those ports they must be sleaved emitters. What that means is that there is some heat shrink on part of the male connector so that the 3rd line on the RS232 female connector does not short to ground. When that happens the IR emitter will not work. URC sells a starter kit for the MSC 400 that includes these emitters.

The RFID is not the issue nor is the firmware.

DB

I am in fact using the sleeved emitters purchased from SurfRemote.

The emittters will flash if I use a smart macro on the MSC side and have the trigger defined in the MX3000. The issue is trying to use it as pass thru directly from the mx-3000

Thanks for the response tho, I appreciate it!

Anybody from URC want to weigh in here? Jeff wagner? Dale/Darnitol?

Just looking for a little help, I have a workround.

Are Joe C5 and I the only ones experiencing this?

Here's the scoop. The MX-3000 is only capable of ID 01-0F but that is not significant. You do not have to set an ID greater than 0F to get IR ports 7-12. You can set the MSC400 primary to 01 and the secondary to 02.

In the MX-3000 software go under RF setup and set the Default Receiver ID to 01. Then click 'add' and give it a name such as "secondary" and set that one to 02.

Now to properly route to ports 7-12 use the following
Port7 = Secondary Receiver Port1
Port8 = Secondary Receiver Port2
Port9 = Secondary Receiver Port3
Port10 = Secondary Receiver Port4
Port11 = Secondary Receiver Port5
Port12 = Secondary Receiver Port6

There is text at the bottom of the RF Setup window in the MX-3000 software that explains this as well.

Hope this helps.

This is the RF1WAY-Micom version and I believe this is a hardware version and can not be updated. It really isn't an issue though, all it means is you have to set 2 IDs to be able to address all 12 ports

Thanks Eric! That is exactly what I tried to do, but couldn't get emitter 7-12 to flash when I set Secondary in the Msc400 (for example Primary is 01, secondary is 02) and creating two RF recievers in the MX3000 (1 and 2). I set some components to RF on Receiver 2, and the emitters on 7-12 won't flash, which seems to jive with the comment in the msc editor and the firmware warning.

Oh well...smart macros it is for those devices. Thanks for the info on the firmware!

I will give it another try, just in case i mucked it up the 1st time.

Hopefully this is related enough not to be considered hijacking...

Does the new firmware fix the issue with the MSC400 sending out data to all the flashers for every command? I might consider purchasing a new unit to replace mine if that is fixed (it causes some issues). The other thing does not currently bother me as much since I am using the second set for RS-232 (until I add something to my system - almost full).

What I am talking about is there is a exremely brief flash to all units before the IR commands are sent out to the specified unit. Some devices don't much care for this :-(. The MRF-350 does not do this (sending a command to a selected port does not have the brief flash). I have verified this flash is sent out using a Slink-e (reads IR).

jbwood1 - I still have a pair of original MSC400s in a box in the basement I can try this on, but I was pretty sure it worked back when I tested it last. Please email me your MSC file and your 3000 file and I'll load 'em up and see what's going on.

I also have a pair of newer MSC400s I can load it on and tell you what I find there too.

JoeC5 - I vaguely remember an issue like you are describing, but I've got to really think about that one to remember what that was about. What remote are you using? You could send me your files as well, once I get that stuff set up again I can test them both.

Thanks - I'm using an MX-980 with the MSC-400 (I have another 980 with a MRF-350 in another room).