-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible to add Madlion Nano 68 Pro? #10
Comments
Certainly possible (albeit very bad polling-based support as their firmware has no better interface), it'd just need to have some basic descriptions including the layout. It might help you to try modifying AnalogSense.js and then I could port it to C++: https://github.com/AnalogSense/JavaScript-SDK/blob/senpai/AnalogSense.js#L715 |
Could you give me a brief explanation on how to do that? Im a hardstuck noob when it comes to doing stuff like that |
Well, you can download the JavaScript-SDK repository and open the demo.html in your browser to test it, then just modify the AnalogSense.js to adjust the layout. I'm not entirely sure about the productId but you can remove that from the filter and then use |
The device does not even show up on trying to connect on this demo site. What exactly do i need to do? Im so sorry D: |
You did not remove productId from the filters |
Well, that's interesting. I guess you can try also removing vendorId? |
Still nothing |
You did press Ctrl+S and reload the browser, yeah? Otherwise I'm not sure what's wrong with your keyboard firmware if it's not even got the interface I'd expect from Madlions. |
Noticed u did not text back. Will there be any fix for this? i got this info from my keyboard: productName: Nano 68 Pro The device splits into 3 modes i guess: productName: Nano 68 Pro productName: Nano 68 Pro |
None of these seem like the expected management interface. |
Does it actually detect your key presses when you 'connect to it'? |
Detect it where? They keyboard is still usable as usual |
On the demo page. |
No the site is blank. |
Yeah, I thought so. I'm probably not gonna bother buying a Nano 68 Pro because Madlions have a horribly useless firmware interface to begin with. |
Yeah, do you have any idea on how i could do this myself? I guess i need to figure the usage and usagepage? |
I guess reverse-engineer their management website if you say it does indeed work. |
With the usage 0x0 and usagepage 0x1 i can connect on your site. It wont show anything still... |
Ive tried multiple things now. Cant seem to get an this.dev.oninputreport out of this crap. The keyboard wont put out anything in the usage modes 0x0 and 0x6. The other ones cant be used to connect.
|
Ok i have absolutely why or how this works, but i was able to get it to do this when turning on axis alignment mode on the official website, i assume this is what allows it to start interfacing analogue inputs but i might be wrong. Normally on the website this mode allows you to see travel distances of each key, I hope this helps idk, maybe try your code with this enabled, as i only added filters to get this to trigger |
Why didnt i thought of that. Yeah thats good! Can u share the code that u changed in the AnalogeSense.js? I think i just need to figure out how to get the Calibration running on other sites. |
wait fr |
please let me know how the hell you've done that cus all i did was enable the extra filter and turn on axial alignment, essentially ive not done anything but let it actually recognise the keyboard. I assume this is what they changed between the new boards and the madlion 60//68 |
Yes it looks like Byte17 reports the exact depth of the key. I will need to figure more stuff out but this is a breakthrough! |
And you'll also need to figure out a way to programatically enable the 'axial alignment mode' :^) |
ok cool, idk what the image was or anything cus im about as good at coding as a rock but nicee, good to know i helped ig |
also let me know if your able to implement it and how cus ima see if i can at least try for the mad68 pro (r) aswell. might have bought both |
Yeah that will be my next step. Should not be too hard. |
damn welp guess bro is cooking ( very excited ) |
also @Sainan what does the website actually look like when it works (i dont have any supported boards so idk what it should look like) |
ohr, makes a lot more sense than what i was seeing before, thanks |
ok so i got ai to try to write something, it sort of works (it updates when you click, connects etc) but idk if its accurate or correct cus theres way too many keys, its using the code that u put here earlier so idk. How would i at least try to filter it a bit so im not being overwhelmed by values ` <script src="analogsense.js"></script> <title>AnalogSense HID Tester</title> <style> body { font-family: Arial, sans-serif; padding: 20px; } button { padding: 10px; margin: 10px 0; cursor: pointer; } #device-list { margin-top: 20px; } #key-logs { background: #f4f4f4; padding: 10px; min-height: 150px; border-radius: 5px; } </style>
|
Does not look accurate because u have a weird output. Ur Output has the same number everytime. I dont have time today to look into this more but maybe tomorrow. I will figure something out :) |
yup oki sounds about right thanks |
This is a working code for the nano68 pro. The only thing that is missing, is the activation of the Calibration mode.
|
@Actiongomini ive got some news!! AnalogSense.JS
HTML
|
WAIT SICK nice bro got it, i dont believe u need the other site open but you do need to enable it as an option again might be wrong but i'll check in a sec thx @nisayera |
Nice, yeah we will need @Sainan to implement this in the thing. Ai helped me out so much, glad that exists |
Also figured out the Axial Alignment code. but i was not able to execute it . This is the enable command.
|
Does not look like that im able to get the Axial Alignment to work. If anyone could help out this is the protocoll:
|
If needed i could supply any info that is needed. Thanks :)
The text was updated successfully, but these errors were encountered: