counterfeit_DS18B20 VS x64dbg

I used this project to indetify it its Falimy C clone

Are you sure that it actually is a ds18b20? Most sold items are fake: https://github.com/cpetrich/counterfeit_DS18B20

Info on how to identify fakes: https://github.com/cpetrich/counterfeit_DS18B20

According to https://github.com/cpetrich/counterfeit_DS18B20 some fakes might run into crc errors. On the other hand any kind of cabling issue would probably also...

p.s., just a heads up, your DS18B20s are almost certainly fakes. I'm using some of the fakes as well, and they perform well enough for my application, but there's a real chance genuine sensors would perform better on a long network.

Looks like a counterfeit DS18B20 sensor. I think all these similar style sensors sourced from China contain counterfeit devices. See https://github.com/cpetrich/counterfeit_DS18B20

If you're using DS18B20 devices, you should probably be aware of https://github.com/cpetrich/counterfeit_DS18B20, just for general information.

I have recently purchased Sonoff DS18B20 temperature sensor. I was curious to check if it uses an original temperature sensor. For this I have tried this Arduino sketch: https://github.com/cpetrich/counterfeit_DS18B20 . To my big surprise it turned out that it has a counterfeit sensor. Could anyone test it as well and confirm or deny my findings?

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view