Difference "disablecrccws= 1" and "disablecrccws_only_for"

What are the disablecrccws= 1 and disablecrccws_only_for parameters for?

disablecrccws stands for "disable cw checksum test"

You can set the parameter: "disablecrccws = 0 or 1" or "disablecrccws_only_for = xxxxx:xxxxx" in the oscam.conf, then these values are set globally and affect all readers that you then entered in the oscam.server.

If you have also entered "disablecrccws" or "disablecrccws_only_for" in oscam.server, these values will be "overruled" by oscam.conf

If you do not make these settings in oscam.conf, you can also set them in oscam.server, in any reader. These settings then only affect the respective reader.

disablecrccws = 0 or 1 (0 keeps the checksum test on, 1 keeps it off)

disablecrccws_only_for = 098C:000000;09C4:000000;098D:000000

turns off the checksum test for the CardID 098C and 09C4 and 098D. It remains on for all other CardIDs.

By the way, the checksum test must be switched off by the SKY CAIDs.

So either in oscam.conf --> disablecrccws = 1 (then applies to all CAIDs and all lines) or disablecrccws_only_for = 098C:000000;09C4:000000;098D:000000 then applies globally to all SKY CAIDs and all lines

or but

in the OSCAM Server per line either disablecrccws = 1 (then applies to the respective line) or disablecrccws_only_for = 098C:000000;09C4:000000;098D:000000

is then in the respective line for the Sky CAIDs

Another small addition from me.

Since there are still configs that show the disablecrccws* parameters in absolutely nonsensical combinations, here is an explanation for handling:

1. Configuration:
oscam.conf:
disablecrccws = 1

All other disabecrccws and disablecrccws_only_for parameters have no effect. The CRC check is switched off for all readers and all CAIDs. It should now also be clear that it makes no sense to set one of these parameters for any reader or even the additional parameter disablecrccws_only_for in oscam.conf.

2. Configuration:
oscam.conf:
disablecrccws (not set)
disablecrccws_only_for = 09C4:000000;098C:000000;098D:000000

The CRC check is switched off for the V13, V14 and V15 CAIDs on all readers.
Using disablecrccws or disablecrccws_only_for in the reader only has an effect on other CAIDs.

3. Configuration
oscam.conf:
disablecrccws (not set)
disablecrccws_only_for (not set)

oscam.server:
disablecrccws = 1

With this reader, the CRC check is switched off for all CAIDs.
The additional setting of the disablecrccws_only_for parameter for this reader is therefore pointless and also ineffective.

4. Configuration
oscam.conf:
disablecrccws (not set)
disablecrccws_only_for (not set)

oscam.server:
disablecrccws (not set)
disablecrccws_only_for = 09C4:000000;098C:000000;098D:000000

The CRC check is switched off with this reader for the V13, V14 and V15 CAIDs.

Again for prioritization:
- disablecrccws before disablecrccws_only_for
- oscam.conf before oscam.server

Application:
Server:
currently the parameter disablecrccws = 1 is sufficient for the corresponding cards in the reader.
Due to the clarity/structure in the configs, I would generally do without the disablecrccws_only_for parameter on the server.
This would possibly make more sense in a form expanded by the SID, because then if other packages are offered via the CAID that are still CRC corrected (e.g.: HD+ via Sky). Although they are currently running without any CRC correction.

client:
It's actually very simple on the client. The server should be responsible for the correct 'processing' of the CWs. So what should the client still correct? ME nothing.

Therefore, the parameter disablecrccws = 1 can generally be set in the client in the oscam.conf.

The disablecrccws_only_for parameter in its current form can therefore be completely dispensed with, so an oscam update to versions >=11702 is not absolutely necessary. The use of the disablecrccws parameter is sufficient and it has been running without errors since it was introduced.