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

[Jope]

Originally Posted by spudje

So that would be a combined SUM and Rys? Connecting to both keyboard and db9 and ending in 1 USB?

Yes, that's what I'd like. Then I could connect a USB KVM or perhaps some Logitech unifying receiver to it.

[spidi]

This [ Show youtube player ] demonstration new firmware for RyśMKII and USB Dance Mat on Decrunch 2016

[ReadOnlyCat]

Originally Posted by Retro-Nerd

Sega Saturn USB pad (original SLS)

Sega Saturn USB buttons assigned in Windows
[...]

After Retro-Nerd's contribution, here is mine.

I am using the original Saturn 3D controller plugged into the Raphnet.Net Saturn to USB adapter.

The original Saturn 3D controller has a nifty digital/analog switch which changes the output of the controller between digital and analog.
As you will see below, there is much in common between the two modes but some output change (dpad behaviour, analog stick behaviour, triggers).
All purely digital non directional buttons stay the same.

I guess that as far as CD32 emulation is concerned, the proper way to proceed would be to just take the digital mode into account.
Obviously, if the Rys supported to generate Amiga analog signals that would be even more fantastic since that would allow to use the controller in analog mode.

Note that the link I gave above for the Saturn-to-USB controller has additional informations regarding the mapping of buttons (cf http://www.raphnet.net/electronique/...b/index_en.php).

Hope this helps!
(Sorry for the long delay Spidi, back pain issues put me away from computers for a few months.)

Saturn USB Adapter:

Analog mode:

A:             button 2
B:             button 3
C:             button 6
X:             button 1
Y:             button 4
Z:             button 5
start:         button 10
dpad-left:     |
dpad-right:    | analog X axis / Y axis (only 0 and max values)
dpad-up:       |
dpad-down:     |
analog-left-trigger:  button 7
analog-right-trigger: button 8
analog-stick: nothing

Analog mode:

A:             button 2
B:             button 3
C:             button 6
X:             button 1
Y:             button 4
Z:             button 5
start:         button 10
dpad-left:     button 12
dpad-right:    button 11
dpad-up:       button 14
dpad-down:     button 13
analog-left-trigger:  button 7 (and analog axis "dial")
analog-right-trigger: button 8 (and analog axis "slider")
analog-stick: X axis / Y axis

USB VIEW OUTPUT:

Device Descriptor:
bcdUSB:             0x0101
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x289B
idProduct:          0x0005
bcdDevice:          0x0200
iManufacturer:        0x01
0x0409: "raphnet.net"
iProduct:             0x02
0x0409: "Saturn_Adapter_2.0"
iSerialNumber:        0x03
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Low
Device Address:       0x02
Open Pipes:              1

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

Configuration Descriptor:
wTotalLength:       0x0022
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0x80 (Bus Powered )
MaxPower:             0x32 (100 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x01
bInterfaceClass:      0x03 (HID)
bInterfaceSubClass:   0x00
bInterfaceProtocol:   0x00
iInterface:           0x00

HID Descriptor:
bcdHID:             0x0101
bCountryCode:         0x00
bNumDescriptors:      0x01
bDescriptorType:      0x22
wDescriptorLength:  0x002F

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x0A

[Acill]

Also wanting to know how I update it?? I have mine and have no idea what firmware is on it.

[Arnie]

Originally Posted by Acill

Also wanting to know how I update it?? I have mine and have no idea what firmware is on it.

You need to download the firmware along with the Rysflasher windows software. You also need an A to A usb cable.

I haven't flashed my adapter but, I would imagine that the flasher software will tell you what version you have.

[jarp]

Current flasher does not tell you which software is in. It can only read firmware from file and write it and that's all.

Does not matter though. Just flash newest firmware and you are all set (though I had problems with newest firmware and re-flashed older one back).

[vroom6sri]

Can anyone tell me how you actually flash the Rys MkII please? I have downloaded the flasher and the flash files and connected it to my laptop but it isn't detected. Is there something I have to do to put it into update mode?

[jarp]

There's a button on the top of Rys MKII you need to press while connecting it to the laptop. It goes then to flash mode and Rys Flasher is able to detect the dongle and flash new firmware in.

[vroom6sri]

Thanks, Jarp.

I don't recall seeing a button on it but there is a hole. Is it one of those you have to use a folded out paperclip to press in?

[Retro-Nerd]

Yes, it's a bit tricky to press and hold down this tiny button and plugin it into the USB port. But it works.

[vroom6sri]

Many thanks folks. I will try it tonight.

Hi, did someone manage to use the mouse wheel with Rys? Or isn't it technically possible? Just received mine and I'm doing some experiments, but no success yet.

[vroom6sri]

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.

[jarp]

Correct me if I am wrong but Amiga's DB9 joystick port does not support mouse wheel - there is just not enough pins for it? To get wheel support one must use either serial mouse (+driver) or some custom adapter (+driver) which feeds wheel related events to the Amiga via joystick port. After you somehow manage to input wheel events to the Amiga only then you can use software like FreeWheel, no?

Now what would be really, really really cool would be a Rys MKII like adapter, which connects to both DB9 ports and would have three USB-ports; two for joysticks and one for the mouse. Adapter would have three modes, joystick + joystick, mouse + joystick and wheel mouse. Modes could be switched just by pressing mouse button or joystick's fire button.

There should be no technical reason why this could not be done and even drivers for reading wheel events via joystick port exists in the Aminet. Anyone wanting to take the challenge? Rys MKIII perhaps?

[idrougge]

Doesn't the Mikromys support mouse wheel without occupying the joystick port?

[jarp]

Hmm true that! Micromys wheel mode seems to require a driver but yeah seems connection to another joystick post is not necessary unlike in example I found from Aminet.

Probably Micromys multiplexes wheel events to XY-movement events then and drivers will decode them. Very cool actually. But since Rys MKII does not have any drivers available, it just cannot do the same sadly (but with new firmare and a driver perhaps it COULD, developer would just need to implement such support) :/

[idrougge]

If mouse wheel was implemented as X/Y movement with third button pressed, it would at least work in IBrowse without any driver support. A driver would still be necessary to handle conflicts with software using the third button, such as the ASL file requester.

[jarp]

I wonder if @spidi is interested in developing Rys MKII further, wheel support could be cool addition...

[spidi]

Originally Posted by idrougge

If mouse wheel was implemented as X/Y movement with third button pressed, it would at least work in IBrowse without any driver support. A driver would still be necessary to handle conflicts with software using the third button, such as the ASL file requester.

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

[jarp]

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?