Coolsat - discrete codes?

[majunga]

I downloaded the .txt file but not sure how to read it....I am looking to make an IR translator....

Would you happen to have the discrete hex codes for the CoolSat 4000 for 0-9?

Or is there a way for me to decode what these commands are from the .txt file?

[majunga]

Posted a question another thread.....I am a noob to JP1 (although I do have an EE degree in microprocessing).

I would like to find the discrete codes for a particular device (I have its remote). I am then planning on making my own IR blaster which will emulate a remote.

What is the best way to accomplish this capture of discretes? Does one of the remotes you sell plug in to a computer for easy capture of discretes?

[whompus]

Open the file with rm or km and you will see the codes under functions.

[majunga]

Thanks very much for the info.....definitely helps.....now lets say I am going to create my own remote and I want the hex codes (on/off times of the IR LED) for each function.....

In this case, the format = NEC1, Setup code = 1554, Protocol ID = 00 5A

For the num 0:
EFC = 054, OBC = 014, Hex = 8F

What would the full hex string look like (with start and stop bits)?

[johnsfine]

Posted a question another thread.....I am a noob to JP1 (although I do have an EE degree in microprocessing).

I would like to find the discrete codes for a particular device (I have its remote). I am then planning on making my own IR blaster which will emulate a remote.

What is the best way to accomplish this capture of discretes? Does one of the remotes you sell plug in to a computer for easy capture of discretes?

You seem to want to ask a new non-JP1 question. But instead you tacked some vague partial questions onto the ends of two JP1 threads that have no obvious connection to the question you're trying to ask.

We have a Non-Jp1 forum specifically for asking the JP1 experts that sort of question.

But even there we need a bit more detail about what you're really trying to do.

"full hex string" might mean a lot of things. I think you mean Pronto Hex, but I'm not sure. You can use MakeHex.exe to generate Proto Hex strings, or there is a new Java program for that (forget its name at the moment).

A setup code number such as your 1554 is meaningless if it came from some user built upgrade. Those numbers are only meaningful for official setup codes. They're arbitrary numbers for user upgrades.

If you want to discuss a specific user upgrade, always give the URL where you got it.

Outside of a JP1 context the important info is
Protocol name (You said NEC1)
Device and subdevice numbers (You didn't say)
OBC number for each function (you gave one)

The setup code number, Protocol ID, EFC and Hex cmd are all useful only as indirect ways of getting the above info.

Edit: On reread, I guess I see the connection to this thread and the URL in an earlier post of the Coolsat 4000 Pro upgrade that you're talking about.
And inside that I see the device number is 1 and there is no Subdevice.

So if you want Pronto Hex you can use MakeHex.exe after editing the device line in nec1.irp to read
device=1

[johnsfine]

Thanks very much for the info.....definitely helps.....now lets say I am going to create my own remote and I want the hex codes (on/off times of the IR LED) for each function.....

In this case, the format = NEC1, Setup code = 1554, Protocol ID = 00 5A

For the num 0:
EFC = 054, OBC = 014, Hex = 8F

What would the full hex string look like (with start and stop bits)?

Even more than in your other thread, I think you're asking that in the wrong thread and wrong forum. But for the moment I'll just answer rather than try to split/move this to where it belongs.

We need a better idea about what you think you mean by "capture of discretes".

I have a very good idea what it means to "capture" IR signals (from original remotes). Any of the JP1 learning remotes plus a JP1 cable could be used for that purpose and very often are. But I think the CaptureIr hardware and software (discussed in other threads) are a much better choice for that task.

I also know the typical meanings of the word "discretes" as used in various remote control forums:

1) The more correct meaning is based on the fact that certain functions such as Power On/Off or input selection are commonly controlled by toggle or round robin commands. When there is a command for such functions that always goes to the same state, it is called a discrete.

2) The more common, less correct, overlapping meaning for discretes is the set of useful commands that the device understands but the original remote doesn't have buttons for.

Especially for definition (2) the concept of "capturing" a "discrete" is almost a contradiction. We have ways of experimenting to discover discretes.

[The Robman]

I have split these posts from the two other threads and combined them into this single thread.

[majunga]

Sorry for posting in the wrong area.....thanks for your help/info.

I have built an IR translator (bvwelch design). I am working on the code and I think I only have one issue left to tackle.

I am trying to talk to a Coolsat 4000 Pro, but I need the device and subdevice (NEC1) codes for this STB. Can someone tell me what these codes are? My IR decoder (parallel port) does not seem to be working. It could be a "noisy" environment here at work.

[classicsat]

To translate from what to what? (not stealing Dishnet I hope).