Ohhhh, I spoke too soon.
It is transmitting but... it's rare. Currently, it does so under the following circumstance:
1. When MD has just started up
2. From the AV properties (IR commands) of the TV device screen - Test Command.
It will not do it from the "Test Command" on my media scenario.
In addition, the USBUIRT stops working after a "quick reload". It joins the ranks of "Some devices failed to correctly start..." and even the receiving part no longer works despite the littel LED desperately flashing. Arrrggghh. As you can imagine, this is pretty frustrating because I'm trying to set up commands, scenarios etc and reload/regen needs to happen quite often. Now they have to be replace with a reboot.
My age-old question - When some devices "fails to start correctly" and you get that polite little message in the top left... how do I track down the problem? It doesn't tell me which devices... and how do I know which?
2nd question- how do I track down what is causing the USBUIRT to enter the above group of devices on quick reload?
3rd question - why does the unco-operative little begger stop performing (ie transmitting)? I thought it was even after the IR codes are "received" for the first time because shortly after I push the "right" button on my remote to get to the menu, transmit stops working. However, an odd thing happens in between - my TV switches off. It's almost as if the MD is sending the "toggle power" to the TV because I've never had conflict between my MD remote and the TV before. Maybe as soon as I start to "use" my MD it tries to power on the TV because the TV is connected to the MD? But since the TV is already on, that results in a power off? And maybe the entering of that state (scenario, whatever) is correlated to the transmit stopping.
Sorry, all very confusing at this moment.