English Amiga Board - New USB HID mouse / USB Joystick / Gamepad USB adapter for the classic Amiga

English Amiga Board (https://eab.abime.net/index.php)

- News (https://eab.abime.net/forumdisplay.php?f=29)

Quote:

Originally Posted by jarp (Post 1114377)

Couldn't you just multiplex mouse wheel events to 3rd button signal and then simple driver would be needed to do the decoding? Legacy software won't care about 3rd button being crazy, no?

If memory serves, for the EZMouse I used the middle-mouse button pin in output mode, and multiplexed the extra signals similar to how a Megadrive pad works: with the MMB pin in a low state, the wheel button is mapped to the left button, the fourth button, if present, is mapped to the right button, and wheel events are mapped to the lowest bit of each mouse counter.

Indeed, i'm pretty sure the Mroocheck and PS2m and derivatives all use the MMB pin for this as well.

Quote:

Originally Posted by spidi (Post 1114370)

If there is documentation of the protocol to use the third mouse button to send traffic mouse wheel in IBrowse please link to it.

No protocol. IBrowse scrolls the window when you hold the middle mouse button and move the mouse.

Freewheel has some support to force scrolling on MUI toolbars by IDCMP events (mouse scrolling).

I just tried and here it works. as soon as i run FreeWheel scrolling works in iBrowse.

Note that i'm using a USB Mouse over Poseidon + the v50 input.device from Ralph Schmidt.

However this should work with any FreeWheel compatible mouse driver (Cocolino/PS2m have them).

Quote:

Originally Posted by jarp (Post 1114377)

Couldn't you just multiplex mouse wheel events to 3rd button signal and then simple driver would be needed to do the decoding? Legacy software won't care about 3rd button being crazy, no?

I know for a fact that reading wheel on USB side of mouse and emulate FreeWheel (hold middle mouse and move up/down) on Amiga port side works, have it working in WildPort since January 2015. Also nailed stable CD32 pad emulation around the same time. Not that it matters much as long as there is no product released. ;)

Quote:

Originally Posted by vroom6sri (Post 1114146)

even - Have you got a program like Freewheel running?

BTW I successfully flashed the device and now have working autofire buttons. Thanks again, folks. Loving this gizmo.

Hi, vroom6sri. Yes, I'm using Freewheel. I've made some tests with Cocolino software and noticed that it registers some kind of activity when middle button is pressed while wheel is moved, but nothing that I could use for scrolling.

Another problem is, wheel button is already assigned for mode selection and sometimes mouse speed changes when the button is pressed. However, I could not yet understand exactly how this works.

Except for that limitation, I really like the little adapter! My old serial mouse was making me crazy :laughing

I got SUM Keyboard adapter on my A600 with Vampire, and I love it.

A few programs doesnt seem to like the combination;

Hippoplayer
Protracker 362
THX

I should add that I have disconnected/removed my floppydrive, so the USB cable can fit thru there. Sadly the USB cable is too short to be dragged thru the RF Modulator hole in the case.

Anyone had similar issues? I guess I should test if reinstalling the floppydrive will fix this crashing/freezing...

Reinstalled the Floppydrive, and Hippoplayer stopped crashing/freezing the computer.

Protracker 362 and THX still freeze the computer, altho its not really of any consequence since I dont really use them... :p

One for the compatibility list. The Arendo CSL vertical mouse (wireless) works perfectly fine with Rys MK II. :)

Hi Spidi, I hope you still read this thread and are open for more ys MkII irmware updates. As also can be seen in this thread http://eab.abime.net/showthread.php?t=86497 On my CD32 I'm using a combination of:

Rys MkII with latest firmware
8Bitdo wireless USB adapter: https://www.8bitdo.com/wireless-usb-adapter/
8Bitdo SF30Pro (not plus) wireless controller and PS4 dual shock controller

Both controllers work fine in joystick, pad & CD32 modes. However, the button mapping is totally weird and confusing. Can I still provide you with the info using the tools mentioned earlier in this thread so you can provide an updated firmware?

I figured out the mapping and USB info:

Code:

Wireless connector



Device Descriptor:

bcdUSB:             0x0200

bDeviceClass:         0x00

bDeviceSubClass:      0x00

bDeviceProtocol:      0x00

bMaxPacketSize0:      0x40 (64)

idVendor:           0x2DC8

idProduct:          0x3100

bcdDevice:          0x0001

iManufacturer:        0x01

0x0409: "8BitDo



Button mapping of wireless 8bitdo SN30 Pro = SF30 Pro (not SF30Pro+)



D-pad                                POV Hat

Left analog stick                X & Y Axis

Left analog stick button (L3)        Button 14

Right analog stick                Z Axis & Z Rotation

Right analog stick button (R3)        Button 15

Select                                Button 11

Start                                Button 12

Blue X                                Button 4

Green Y                                Button 5

Red A                                Button 1  

Yellow B                        Button 2

Home                                Button 3

L1                                Button 7

L2                                Button 9

R1                                Button 8

R2                                Button 10



Not mapped                        Button 6, Button 13



Button mapping of wireless PS4 dual shock

D-pad                                POV Hat

Left analog stick                X & Y Axis

Left analog stick button (L3)        Button 14

Right analog stick                Z Axis & Z Rotation

Right analog stick button (R3)        Button 15

Share                                Button 11

Options                                Button 12

Square                                Button 4

Triangle                        Button 5

Cross                                Button 1  

Circle                                Button 2

Playstation button                Button 3

L1                                Button 7

L2                                Button 9

R1                                Button 8 

R2                                Button 10



Not mapped                        Button 6, Button 13



Preferred mapping (Rys MkII CD32 emulation mode):

I corrected my original info, my thinking was wrong. Of course you can't change the mapping between the wireless controller and the receiver. Only between the receiver and the CD32.



D-pad                                POV Hat                --> CD32 D-Pad

Left analog stick                X & Y Axis        --> CD32 D-Pad (Is that possible map this to both D-Pad and left analog stick?)

Left analog stick button (L3)        Button 14        --> No CD32 mapping

Right analog stick                Z Axis & Z Rot        --> No CD32 mapping

Right analog stick button (R3)        Button 15        --> No CD32 mapping

Select                                Button 11        --> Together with button 12 operation mode switch

Start                                Button 12        --> Together with button 11 operation mode switch

Blue X                                Button 4        --> CD32 blue button

Green Y                                Button 5        --> CD32 green button

Red A                                Button 1        --> CD32 red button  

Yellow B                        Button 2        --> CD32 yellow button

Home                                Button 3        --> No CD32 mapping (If this is mapped in joystick and pad mode, please also replace this with other button)

L1                                Button 7        --> CD32 L button (<<)

L2                                Button 9        --> Autofire 2

R1                                Button 8        --> CD32 R button (>>)

R2                                Button 10        --> Autofire 1

I'll send Spidi a pm as well, hoping he can bake this in a new firmware.

Unfortunately no response from Spidi yet :( Still hoping they're still willing to make a new firmware to (better) support this wireless adapter.