Hey, I'm not sure if it's just slow but when I try to use the IR Camera, the program just freezes after it says "Configuring". The easter eggs don't appear to work either and I think trying to do NFC tag makes it crash. Not sure what's wrong.
Hmm, that's not good. You have a good signal?Hey, I'm not sure if it's just slow but when I try to use the IR Camera, the program just freezes after it says "Configuring". The easter eggs don't appear to work either and I think trying to do NFC tag makes it crash. Not sure what's wrong.
Your version made it freeze too, so I don't think anything's wrong with my compiling of it. And attempting to use the easter egg just makes the program freeze up as well. My signal should be fine... hmm.Hmm, that's not good. You have a good signal?
Also the IR camera function is blocking for now. That means that if a packet is lost in configuration part, it will stay there. So you need to close it and try again.
Lastly, for the easter eggs, you can't hear a thing? or it comes slow or strange noises?
EDIT: Also what sdk/net/vs did you used? It is supposed to be compiled with vs2017, net4.7.1 and win sdk 10.0.16299.0.
The new version fixed the easter egg. Because I now use a pointer I had to change the memcpy function and pass the pointer as is.Yeah, the new compile immediately just gives an error with the IR.
And I wanted to tell you to also test NFC. Great job!Both NFC and the IR camera give me "3MCUONBUSY." I hope that helps you solve the issue, I have no idea what's wrong with it.
And I wanted to tell you to also test NFC. Great job!
So it actually doesn't get any far.
What happens is the following:
- Switch to NFC/IR input report mode: OK
- Enable MCU: OK (got the cmd)
- Wait for MCU to boot/initialize/get ready: Problem.
Are you familiar with USBPcap?
This can capture packets from a BT adapter (USB or built-in) and can let me see what your controller replies back.
The way to do it is the following:
Then send me the PCAP through PM or email (the file has mac addresses).
- Install usbpcap. Restart.
- Connect the controller.
- Go to C:\Program Files\USBPcap and run USBPcapCMD.exe
- Enter which hub to capture (choose the one that the bt adapter and the controller is connected).
- Enter a filename: mpahmpah.pcap
- Let it run and open Joy-Con toolkit.
- Go to IR and press capture or stream once.
- After the error, press again (so I can have to samples).
- Close USBPcapCMD.exe console window by pressing X or hitting ctrl+C
Hello,And I wanted to tell you to also test NFC. Great job!
So it actually doesn't get any far.
What happens is the following:
- Switch to NFC/IR input report mode: OK
- Enable MCU: OK (got the cmd)
- Wait for MCU to boot/initialize/get ready: Problem.
Are you familiar with USBPcap?
This can capture packets from a BT adapter (USB or built-in) and can let me see what your controller replies back.
The way to do it is the following:
Then send me the PCAP through PM or email (the file has mac addresses).
- Install usbpcap. Restart.
- Connect the controller.
- Go to C:\Program Files\USBPcap and run USBPcapCMD.exe
- Enter which hub to capture (choose the one that the bt adapter and the controller is connected).
- Enter a filename: mpahmpah.pcap
- Let it run and open Joy-Con toolkit.
- Go to IR and press capture or stream once.
- After the error, press again (so I can have to samples).
- Close USBPcapCMD.exe console window by pressing X or hitting ctrl+C
Yeah, it's a kernel driver filter so you can't install it.Hello,
Very unfortunately, my laptop is a school one and it's the only one I have with Bluetooth support for the time being. Given it's a school laptop, I'm unable to install things that require admin privileges... which I believe usbpcap will need. I'm very sorry, I want to help out but maybe if you released a binary version to this thread proper you could see if any others have the same issue...? And if so, they could help out. It's a shame it doesn't work for me, but I hope you can get it to work soon.
I can install the program by extracting it from the exe but unfortunately of course I need the driver. It's a shame. :/
That's smart! if you could get that to work it may be helpful, I hope it is. I might not be able to do it tonight but will definitely try tomorrow (AEDT).I thought of a nice way though.
Accept a single command. This command will enable a flag in hidapi that will dump in a log file the traffic between the controllers.
I'll send you a PM when it's done
Ah, so it's almost 22:00. I'll try to be as fast as possibleThat's smart! if you could get that to work it may be helpful, I hope it is. I might not be able to do it tonight but will definitely try tomorrow (AEDT).
Thank you I'll examine it!I´ve send you a email with the USBPcap file. It´s the IR error 3MCUONBUSY.
At the moment I'm at work.EDIT3:
It seems that Switch update 5.0.1 has a new joy-con fw. If someone can dump the spi after the update and also test the IR/NFC and make a pcap would be good. Maybe these numbers changed again.
Or this is the same with v5.0.0 jc fw update and they included pro controller update also