decoding a protocol

[zigger]

The overall goal is I'm trying to figure out what frequency the protocol inside the "Hughes_TiVo_HDVR2_-_DirecTiVo.txt" is.

I got the protocol builder spreadsheet and tried to past the protocol hex data into the decode area in the lower right. Hitting the decode button did nothing.

Any tips?

[Mark Pierson]

Hitting the decode button did nothing.

My guess is that you didn't Enable Macros when opening PB, or have your Excel security set to High. I just tried it and it worked fine. The protocol decodes as 37.7 KHz.

[zigger]

Thanks for trying it for me. I still can't get it to work.

[johnsfine]

Why do you want the frequency?

In answering an earlier post today, I proved my reading ability was not up to the job. That might be the problem again, but this time it feels like my mind reading ability isn't up to the job.

What or where is "Hughes_TiVo_HDVR2_-_DirecTiVo.txt"?

I found some files that looked like they might be the same thing, but not under that name. Those files contained the upgrade I pasted in below. Only the first two content bytes (43 8D) affect the frequency, so if those match it's the same frequency. I pasted that into PB and pressed decode and it said the frequency is 37.7Khz.

Upgrade Protocol 0 = 00 41 (S3C8) TiVo (Advanced) (KM v8.25)
43 8D 31 8B 12 CF 44 08 08 01 1A 01 06 01 1A 03
31 D7 42 11 A7 08 B7 08 05 76 7C 04 6B 0B 56 7C
E3 56 00 DF B0 0D E6 06 77 E4 06 05 60 06 46 06
F0 54 C0 06 F6 01 33 46 29 0D 8D 01 36
End

[Mark Pierson]

this time it feels like my mind reading ability isn't up to the job.

What or where is "Hughes_TiVo_HDVR2_-_DirecTiVo.txt"?

Not to worry John... I had the same problem. The actual file is listed as Hughes-HDVR2.txt.

[Mark Pierson]

I still can't get it to work.

The two items I mentioned above are the only plausible explanations for your problem. Try exiting and restarting Excel, and then try opening PB again. Make sure Excel's security is NOT set to High, and/or be sure to Enable Macros if prompted when opening PB.

[johnsfine]

The two items I mentioned above are the only plausible explanations for your problem.

Your mind reading efforts are getting different results than mine

My "plausible explanation" is that he pasted the wrong thing into PB's notes area.

To get it to work, I pasted the same text I pasted in my earlier message (from the word Uprade through the word End).

I don't know how much PB tolerates differences from that format, but my GUESS is not enough for this case.

[Mark Pierson]

Your mind reading efforts are getting different results than mine

My "plausible explanation" is that he pasted the wrong thing into PB's notes area.

You got me there! I hadn't considered the possibility of user error.

[johnsfine]

I hadn't considered the possibility of user error.

People sometimes need to be a little thick skinned to get help from me, because I ASSUME user error until there is strong evidence to the contrary.

In situations where I'm getting paid to do customer support, I try a lot harder to HIDE the fact that I still assume user error.

[Mark Pierson]

To get it to work, I pasted the same text I pasted in my earlier message (from the word Uprade through the word End).

I don't know how much PB tolerates differences from that format, but my GUESS is not enough for this case.

You're correct John. I checked and PB requires the "Upgrade Protocol 0 = ..." header in order to determine that A) it's valid protocol code, and B) to determine the processor type (if possible; it seems to assume the S3C8-Old if none is specified). Without it, PB correctly assumes it's just a bunch of Notes. The "End" line doesn't need to be there, but it makes PB's life a bit easier.