If you are not seeing any data on a standard CANBUS setup then there is something wrong with your setup. You can verify that the M2 is working properly by trying it in an operational vehicle. If you can get it communicating with your vehicle then something is wrong with your test setup.
I am having something similar happening with my system currently. Where it was working in vehicle but not on my test lab.
My test lab consists of two simulators and an ODBII connector. With a standard ODBII dongle it won’t work without a 120 ohm resistor between the can high/can lo pins. Currently getting garbage with the M2. But if you have followed this thread I hope to add a second 120 ohm resistor to take care of that.
But first, verify your system is working properly by connecting your M2 to a vehicle and insure it works properly. If it doesn’t then the issue is with the firmware in your M2 or the device its self. Likely the firmware.
You shouldn’t have to make any changes to any of the software to get it to read data. The other possible issue is that you need data to be broadcast. In my test lab the software can be run as a simulator where it responds to requests or just broadcast the same data every so often. I can see the data in the simulator and with my STN based dongle so I know it is there.
Hopefully that helps.