Flipper can not replay saved file ....

[DavidIgor]

Hi , it looks like modulation issue ?

[DavidIgor]

it just display : "cannot parse file "

[ErSeraph]

I found a potential fix, but cannot try it right now, but you can open the raw file now:

If you edit your file on notepad you will see that "Protocol: RAW" is not escaped, and some other code is escaped and it's not needed.

Example, before the edit:
Filetype: Flipper SubGhz RAW File
Version: 1
Frequency: 433920000
Preset: FuriHalSubGhzPresetCustom
Custom_preset_module: CC1101
Custom_preset_data: 02 0D 0B 06 08 32 07 04 14 00 13 02 12 04 11 93 10
6A 15 41 18 18 19 16 1D 91 1C 00 1B 07 20 FB 22 10 21 56 Protocol: RAW
RAW_Data: ........

After the edit:
Filetype: Flipper SubGhz RAW File
Version: 1
Frequency: 433920000
Preset: FuriHalSubGhzPresetCustom
Custom_preset_module: CC1101
Custom_preset_data: 02 0D 0B 06 08 32 07 04 14 00 13 02 12 04 11 93 10 6A 15 41 18 18 19 16 1D 91 1C 00 1B 07 20 FB 22 10 21 56
Protocol: RAW
RAW_Data: .........

Focus on "Custom_preset_data" and "Protocol: RAW", I managed to read the file with the Flipper, you can open it but i didn't tried it yet

[DavidIgor]

yes , it worked ! I added also custom modulations in setup file (according to custom preset data) , however when I create tpms signal in app it wont do anything .... any suggestions? I use sensor ID from my read with protoview app.

[DavidIgor]

I have recorder low pressure warning from my wheel (recorded on HackRF) when I reply it with HackRF it brings warning light on dashboard of my car. tested to capture and save with protoview app ....it captures it correctly as renault tpms with low pressure , but replaying it with app wont do anything .... nothing happen even if I replay saved file.

[ErSeraph]

Me too, file fixed but cannot replay correctly

[DavidIgor]

I want it to work! hhh
noticed strange thing with sensor IDs as hackrf reads different than protoview ... not sure which is correct ... I will have to investigate

[thedroidgeek]

There's 2 bugs in the capture file generation code for custom modulations, which cause the resulting custom preset data line to lack PATABLE bytes and a line feed.

You can try manually adding 00 00 C0 00 00 00 00 00 00 00 at the end of the preset data line to make it work.

I might make a pull request if I get around to fixing the code in a clean way.

[DavidIgor]

@thedroidgeek like this? and also creating new custom modulation in settings file?

Filetype: Flipper SubGhz RAW File
Version: 1
Frequency: 433920000
Preset: FuriHalSubGhzPresetCustom
Custom_preset_module: CC1101
Custom_preset_data: 02 0D 0B 06 08 32 07 04 14 00 13 02 12 04 11 93 10 6A 15 41 18 18 19 16 1D 91 1C 00 1B 07 20 FB 22 10 21 56 00 00 C0 00 00 00 00 00 00 00
Protocol: RAW
RAW_Data: .........

[thedroidgeek]

Yes, but there's no need to modify the settings file.

[DavidIgor]

@thedroidgeek ok copy that! but It may allow me to use modulation outside of protoview ...right?

[thedroidgeek]

Could you stop asking pointless questions and try to use some common sense?
Why the hell would we have to include preset data in the capture file if it's not to avoid having to add it in the settings file also?

[antirez]

I had the lack of PTABLE somewhere noted in a private TODO file. Then got trapped in the LoRa things and forgot to fix it.