Thread: XM works in Timetrax, not RR

Originally Posted by GizmoQ

All the time! RR doesn't care if its a commander or an XMD, it doesn't see any difference in my boxes. They may have changed something in the newer commanders (I haven't bought on in over a year) but the trick for me was initializing the USB driver. Its been a while but it sometimes would initialize as an HID Device and I had to manually update that so it would come up as a serial port.

Otherwise, I know RR initializes the port at startup so I believe if you're running a fast PC or cut power to the Commander everytime you shutdown or both, RR is trying to initialize a box thats not ready. Try powering the external power connector, plug it into the commander, and run Timetrax to initialize it outside RR. Then close Timetrax, wait 10-15 seconds and run RR. Everything should work. I think I remember this issue once before, but since all mine are powered off the external connector it doesn't affect me.

Another benefit of using the external power connector and FM modulator (at least for me) is I get to listen to the last XM station tuned without the PC or Commander headunit just by dialing it in on the headunit.

My Commander is at least a year old, so I think we're dealing with the same hardware. To get it to work, I do the aforementioned TimeTrax open/close. I found out I can run Pyro's XMTest and it also works (faster to do this at the moment).

I have the two types of boxes sitting right here and I'm only having problems with the Commander (same problem hank_kls65 is having). Both boxes work in TimeTrax, Pyro XMTest, Frodo, etc, but there is something wrong with RR that it doesn't initialize the Commander properly. I am using a serial connection; maybe since you use USB, your USB driver initializes the box (and not RR). Can you post the USB driver you are using? Maybe I'll make a cable tonight and test out the USB route.

Originally Posted by guino

If you make a log using portmon (www.sysinternals.com) I can try to work it out -- but without the unit to test it, it's not going to be simple. IF you do make the log, make sure it has time stamps and that it is showing the data in Hex

Guino,

Attached is the log, is it in the format you expected?

Thanks for you help,

Originally Posted by GizmoQ

Believe me serial is the best way to go! You didn't mention whether you tried the external power connector, I would assume the 12V constant in it keeps the initialization stored in memory somewhere allowing for instant on.

Yes, I've always used an external power connector for the XM Commander. I thought that may have been the problem, so thats why I tried power over the serial bus instead this weekend.

Have you gotten an XM Commander to work with RR using the serial connection?

Originally Posted by guino

Looking at the log you made it's basically what RR does to initialize it, the only difference are a few trailing bytes in there..

Make sure the XMPCR option in RRConfig is NOT checked and try this version:
http://www.rrdownloads.net/BETA/RoadRunner.exe

I also would appreciate if somebody else with a standard XMD1000 could test it to verify it still works.

Guino,

No luck with the new version. Looking at the Port Monitor, the last two strings RR is sending are different commands that what Pyro's XMTest is sending. Pyro sends:

5A A5 00 03 74 00 01 ED ED
5A A5 00 04 74 02 01 01 ED ED
5A A5 00 03 74 0B 00 ED ED
5A A5 00 05 00 10 10 10 01 ED ED
5A A5 00 02 00 ED ED
5A A5 00 06 10 02 01 00 00 01 ED ED

Beta RR sends:

5A A5 00 03 74 00 01 ED ED
5A A5 00 04 74 02 01 01 ED ED
5A A5 00 03 74 0B 00 ED ED
5A A5 00 05 00 10 10 10 01 ED ED
5A A5 00 06 10 02 01 00 00 01 ED ED (Pyro's last)
5A A5 00 02 13 01 ED ED (different)

Attached is a log with what is sent when the new beta RR is opened, closed, and then Pyro XMTest opened and closed.