-
Notifications
You must be signed in to change notification settings - Fork 66
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
Not work on ATmega32u4 on Arduino pro micro Leonardo Board #20
Comments
How many reset drives are running? |
what is meant? |
The device will not be recognized if line 3 to PB5 is not connected correctly. If only the FFB does not work (sometimes) try to invert the X1 line 11 to PB4 - that solved the issue for me. I changed the Hex code accordingly. Adding capacitors did not help, i even removed the one the Joystick mainboard. |
Do you mean that if i connect only the board without the joystick it doesn't even show up on windows? Edit (for future reference): I built the circuit and I can confirm the joystick it's not recognized by windows until the joystick itself is connected. |
Its a while ago... If I remember correctly that is the case. |
Help me out please. What do you mean by invert? Swap PB4 and 5 ? I seem to have that issue but I am a total noob when it comes to coding. |
Invert means turn a high level to a low level and vice versa. You can either change the Hex-code or use a transistor to do so. |
ah ok, that was the other option :D I'll give it a try right away, thanks! |
tried the hex....could you check if that was the right one? It behaves like a sample-hex. its not detected as Lufa JoystickwFFB and gives a periodic push upwards on the stick every second. |
That sounds wrong - i will need to search... I am running it on the "SideWinder Force-Feedback Pro" and it works well. Here is what i did:
Then you find two sections where the port B4 is used: at adress: and at B6D and B77 accordingly. I simply exchanged the commands - 98 to 9A and vice versa. If you understand the Intel Hex format you can see that in the file compare... then convert to Intel Hex again and you should get the uploaded file. If you find the sources to the 54 version file you could do it directly in the code - but i didn't find that. |
I didn't even notice that the Version 54 is different from the Git-sources. I didn't find any Version besides Lufa & 3DP-Vert...where did you find the code version? One thing I notice is, that your hex is a bit bigger than the non-inverted one. r54 39.348 Bytes Interesting thing: The guys over at decentbb took the code a bit farther it seems, integrating the Shift and more buttons. But they worked with the sources provided. Hexes & Text here https://dbb.d3k.org/viewtopic.php?f=8&p=386319 |
The original 54 file is in the download section of this repository: https://github.com/tloimu/adapt-ffb-joy/tree/master/downloads As far as i see it In ffb.c it is this section that needs to be changed: (clr <--> set for TRGX1BIT) //------------------------------------------------------------------------------ #define X1_pull() WRAP( { |
I used 7Zip, thanks for the md5, I'll check my file. Thanks for the help with finding the line in code. I'll give it a try in the evening. Edit: Editedit: #define X1_pull() WRAP( { results in a working hex (no pulsing like when I use your hex. But no FF. The stick centers and FF-Tester does not complain, but no force is applied (and spring effect is not removed when starting the app like usually. |
I am a bit embarrassed to tell you (but also very happy). I found the issue with my stick loosing force feedback while playing. Inside the joystick, a pin of the power connector was broken. So usually the stick had power and worked, but the vibrations of the motors made it loose it's power for FF. Replugging usually worked, because it pushed the pin back in place. After 30 seconds of soldering the beast is working. |
same kind of isssue for me on arduino micro stick is well recognised all axis ok on joystick conf i feel some motor resitance but not effect works with dcs game or force test programe any advice ? i tried the inverted Hex joystick is not reconized at all with this one How did you manage the "PD0 PB0" connection on the micro pro ??? by default the pin PB0 is not exposed to soldering pad... it's connected to a to TX led via small SMD resistor i unsolder the resitor to make the connection but still not work midi is send but ignored by FFB1 i m not sure of but it look that the X1_pull is used to init the midi protocol before effect sending. this pulse bifore midi protocol may be my issue... i will try to recompile the source code instead of using the hex provided to see if it help to solve pb with Arduino pro micro |
Anyone managed to port/patch latest adapt-ffb-joy to run on standard "Arduino Pro Micro" and/or "Arduino Leonardo" boards? Related question also posted here -> #43 (and also in #38) According to the wiki at https://github.com/tloimu/adapt-ffb-joy/wiki there was an old project making it into an Arduino library: |
Yes! I was going to try changing the pinouts to make it compatible myself but I instead stumbled across this fork by @juchong which swaps PB0 for PB6. It also has a PCB design, flashing instructions and is forked from the JayBee-git version with the shift button function and no extra axes. Also the original Teensy 2.0 .hex files using the PB0 pin should work with the Arduino Micro with no modification and with the Pro Micro if you solder to the LED pad.
|
I just tried to get the Micro Pro working. |
Sounds similar to #56. Maybe capacitors? |
I try 1nF upto 10nF in small steps. |
Report: I have two joysticks #96755 device (no fan) and 96755 device (with fan), |
Is this the right schematics for it ? |
I have Teensy 2.0 and Pro Micro working fine on v0.5.0beta1 |
Thanks. |
Yes (PIN3 and PIN10) |
Thanks, Then I check all again |
I found the problem. |
I flash chip with "adaptffbjoy-r54.hex" and it not work! Device not recognized, no device in device manager.
But arduino bootloader work perfectly, this means that the board is working.
The text was updated successfully, but these errors were encountered: