Finding the protocol PID number for SAT 1657

[calisoto]

Hi
Maybe it is a strange question, because my remote is working flawlessly.
But I am curious!

I'm triying to make a device upgrade for SAT 1657 (Siemens Gigaset MV740 PVR), but I can't find the protocol ID.

I can both use the native URC implementation in my remote (URC-7950)
and Rob's upgrade:
http://www.hifi-remote.com/forums/dload ... le_id=2859
http://www.hifi-remote.com/forums/dload ... le_id=2858

I have the URC official EFCs for all the buttons for Siemens MV740 and are the same than Rob's upgrade. I assume than the official protocol has the same device (155) and subdevice (16) than the forum upgrade.

I have tried the protocol 01 71 as described in devices-dev (beta), but it's a different protocol (not phase-shifted).

The protocol is decoded as CanalSat, but CanalSat has higher frecuency than Siemen's, and it doesn't work either:
http://www.hifi-remote.com/forums/dload ... le_id=2833

Is there any way of finding the URC PID number?

[vickyg2003]

Hi
Maybe it is a strange question, because my remote is working flawlessly.
But I am curious!

I'm triying to make a device upgrade for SAT 1657 (Siemens Gigaset MV740 PVR), but I can't find the protocol ID.

Well you do have the PID, it is 0171. The problem is that there are three versions of 0171, and the one you need is not currently in the Protocols.ini (or at least its not in the one that I have on my PC).

I can both use the native URC implementation in my remote (URC-7950)
and Rob's upgrade:
http://www.hifi-remote.com/forums/dload ... le_id=2859
http://www.hifi-remote.com/forums/dload ... le_id=2858

I have the URC official EFCs for all the buttons for Siemens MV740 and are the same than Rob's upgrade. I assume than the official protocol has the same device (155) and subdevice (16) than the forum upgrade.

Kind of, the 155, and the 16 are two of the 3 parameters that the 0171 in your remote takes.

I have tried the protocol 01 71 as described in devices-dev (beta), but it's a different protocol (not phase-shifted).

The protocol is decoded as CanalSat, but CanalSat has higher frecuency than Siemen's, and it doesn't work either:
http://www.hifi-remote.com/forums/dload ... le_id=2833

Is there any way of finding the URC PID number?

You've found it, now we just have to get the tools caught up.

[calisoto]

Thanks, Vicky

I understand that the protocol ID is 0171, it's in the ROM of my remote, but we need to call it properly (with the right parameters), and it is not implemented in protocols.ini yet.

Is that correct?

[vickyg2003]

Thanks, Vicky
I understand that the protocol ID is 0171, it's in the ROM of my remote, but we need to call it properly (with the right parameters), and it is not implemented in protocols.ini yet.

Is that correct?

Yes,

I've mocked up an RM file for you that will pass the right parameters to your ROM protocol. It says that the protocol is required, but it is not. You can use this file to add additional EFC's.
sat 1657

[calisoto]

It works!

Thank you for your help, Vicky

I've made an upgrade for the Siemens Gigaset MV740 PVR:

http://www.hifi-remote.com/forums/dload ... le_id=7702

I have several questions:
What is the third fixed byte used for? (it's not send by the IR engine)
How do we say it (don't send) in PB spreadsheet?
If I didn't know the protocol ID & the fixed data, How I could read them in my remote?

[vickyg2003]

It works!

Thank you for your help, Vicky

I've made an upgrade for the Siemens Gigaset MV740 PVR:

http://www.hifi-remote.com/forums/dload ... le_id=7702

I have several questions:
What is the third fixed byte used for? (it's not send by the IR engine)

Actually in this case, this informatin is sent out after the first frame, but often we pass additional parameters to an executor in the fixed byte. For example the NEC Pid, 005A, the first byte of fixed data isn't part of the signal at all.

How do we say it (don't send) in PB spreadsheet?

When an executor uses parameters that are not going to be sent, you need to use assembly code. You can dissassemble the protocol using PB and study how this third byte of information (DCBuf+2 )nformation is used.

If I didn't know the protocol ID & the fixed data, How I could read them in my remote?

You can't read them from your remote directly. Currently your best source for that information is from Devices.xls or the Lookup Tool.

[calisoto]

You can't read them from your remote directly. Currently your best source for that information is from Devices.xls or the Lookup Tool.

Is it and advanced topic?
Or people are patiently reading OFA flash upgrades and studying them to update devices.xls or your Lookup Tool?

I think this information is slowly gathered by many people like us.
We have discovered now that SAT 1657 has a dev1=155,dev2=16 and dev3=18 and it is used by Siemens.

I can study a protocol learning it with my remote. I've read some Rob's examples on how to use the PB spreadsheet. But using "blindly" the Rom is magic!

[vickyg2003]

You can't read them from your remote directly. Currently your best source for that information is from Devices.xls or the Lookup Tool.

Is it and advanced topic?
Or people are patiently reading OFA flash upgrades and studying them to update devices.xls or your Lookup Tool?

Its beyond my ability to understand how they get the information out of the remote.