Repository navigation
Description
Hello offa,
I have a Fender Bronco 40 amp which from what I understand is very similar to the Mustang series, just with different modeling presets for bass. (Fender Bronco 40 Manual)
It used to be controllable with the Fuse Silverlight-app from Fender.
I managed to build Plug v1.4.3 and the connection fails with the error message
ERROR: Invalid amp id: 239
This error changes depending on the position of the amp selection knob. It has 8 positions and for my setup it produces the ids 171, 0, 0, 244, 239, 219, 219, 219.
Here is the output from dmesg:
[56819.047021] usb 1-7: new full-speed USB device number 26 using xhci_hcd
[56819.204199] usb 1-7: New USB device found, idVendor=1ed8, idProduct=000a, bcdDevice= 1.00
[56819.204216] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[56819.204224] usb 1-7: Product: Bronco Amplifier
[56819.204230] usb 1-7: Manufacturer: FMIC
[56819.204236] usb 1-7: SerialNumber: F62BFF373537553057156631
[56819.210811] hid-generic 0003:1ED8:000A.0011: hiddev2,hidraw4: USB HID v1.10 Device [FMIC Bronco Amplifier ] on usb-0000:00:14.0-7/input0
lsusb:
Bus 001 Device 026: ID 1ed8:000a FMIC Bronco Amplifier
lsusb -v:
Bus 001 Device 026: ID 1ed8:000a FMIC Bronco Amplifier
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1ed8
idProduct 0x000a
bcdDevice 1.00
iManufacturer 1 FMIC
iProduct 2 Bronco Amplifier
iSerial 3 F62BFF373537553057156631
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0084
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 32
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 0x001e
bInCollection 1
baInterfaceNr(0) 1
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0200 Input Undefined
bAssocTerminal 0
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 2
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 1
iTerminal 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 2
bDelay 1 frames
wFormatTag 0x0001 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 44100
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x00c0 1x 192 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioStreaming Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0x0000
Sadly, I lack the C++ skills to look into this but if the Bronco is as similar to the Mustang as I suspect then making Plug compatible with the Bronco should be doable. If someone is interested I will try to help as good as I can.
Activity
StillVoidingWarranties commentedon Oct 8, 2023
I just tried to connect with usb debugging enabled.
On plugging in the amp there is
Then, when trying to connect I get
offa commentedon Oct 12, 2023
The amp IDs listed above aren't known to plug yet, but
0usually indicates some kind of communication issues (eg. a different protocol or package format used).Can you dump the initial packets between PC and device? If not, I can provide you a test version which does it.
StillVoidingWarranties commentedon Oct 12, 2023
I am sorry but I don't know how to log USB traffic except for what I have posted above. If you could provide me with a test version I will happily make some logs. I may also be able to reactivate an old Windows 7 installation with FUSE installed but I don't know how to create any logs on Windows.
offa commentedon Oct 12, 2023
The
20-broncobranch contains a very basic dumper – it'll write all received bytes to stdout (hex).Amp packets are those with a
0x05on the 3rd position (aka array index 2).StillVoidingWarranties commentedon Oct 12, 2023
Ok, thank you very much. I will look into this in a bit.
StillVoidingWarranties commentedon Oct 12, 2023
Ok, here is what I found. First try:
1c 01 05 00 13 00 01 00 00 00 00 00 00 00 00 00 9b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ba aa ff aa 8f 60 86 80 80 00 80 80 07 07 07 01 02 04 00 01 7f 01 07 64 19 8c b3 80 80 89 00 00Second try, different virtual amp selection:
1c 01 05 00 07 00 01 00 00 00 00 00 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 80 ff 8e 63 80 80 80 ff 80 80 01 01 01 02 03 00 00 01 7f 01 00 0d 80 4c ff ff 55 aa 00 00Third try, different USB port, different virtual amp selection
1c 01 05 00 12 00 01 00 00 00 00 00 00 00 00 00 9a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f3 59 80 ff 9c 47 aa 80 80 00 80 80 06 06 06 01 02 06 06 01 7f 01 06 60 19 80 b3 80 80 80 00 00StillVoidingWarranties commentedon Oct 12, 2023
I have tried each of the 24 presets because they result in different bytes being sent. These are organized in 3 banks:
1 - 8: Factory presets (amber bank)
9 - 16: User presets A (green bank)
17 - 24: User presets B (red bank)
These are the 24 lines of data I received:
offa commentedon Oct 12, 2023
The packets seem similar to the mustang ones. I've taken your first example and decoded it using it's format (some values only):
Could these match your settings?
StillVoidingWarranties commentedon Oct 12, 2023
Yes, this looks plausible, I think for the first try I used the 3rd model in the 3rd bank which would be #19.
BTW: The amps of the Bronco 40 are called:
offa commentedon Oct 12, 2023
The 59 Bassman is included with id 0x64. Could you select that one, start Plug and see if you get past the invalid amp id error?
We have to figure out the id's of each amp model. Selecting on of those prior to starting Plug should yield a
Invalid amp id <ID of selected amp>error.StillVoidingWarranties commentedon Oct 12, 2023
Sadly, the Bronco's 59 Bassman preset does not seem to work.
Strangely, I get different IDs without changing the preset. The first one (Rumble) was reported as 0, 71, 171, 238, 244, 245, 251, 252 and 255 on different attempts. Now, after a few tries I cannot get anything other than 0. I tried different cables and different USB ports and power cycling the amp. I will try rebooting the computer.
StillVoidingWarranties commentedon Oct 13, 2023
Error ids vary wildly even after reboot or closing and reopening Plug.
StillVoidingWarranties commentedon Oct 13, 2023
I read your documentation and the Bronco's amp name packets (0x1c 0x01 0x04) seem to differ from that as the Bronco sends the slot number as the 5th byte, not the 4th which is always 0. It does however send the amp names in bytes 16 - 32. I could decode them from a connection log, e.g. the factory presets were sent as
Also, after the mysterious device with address 0x0a there is another packet for a device 0x0d containing only zeroes. After that the following packets seem to be the same as with Mustangs with the confirmation and effects settings.
bronco.txt
offa commentedon Oct 14, 2023
Did your test with the log attached fail with a 0 too? The amp packet seems to use model 0x9a there.
Could it be that the slot is not one, but two bytes?
StillVoidingWarranties commentedon Oct 14, 2023
I didn't remember so I redid the test. I selected the "Bassman '59" factory preset (device id 0x01) and the log is about the same (except for the selected amp), see attached log.
bronco_bassman59.log
Yes. I guess Fender wanted to accomodate more than 256 devices and extended the device id to a little endian Word.
12 remaining items
offa commentedon Oct 17, 2023
While Mustangs transmit presets with two packets each (first starts with
0x1c 0x01 0x04) plus an additional for the current preset, the bronco does something different: After 24 preset (each 2 packets) comes an additional set of packets (the current values?) but then more with the preset prefix, but varying number of follow-ups. This could be the fxloop?However, the amp packet seems at the right place but is decoded wrong later!?
offa commentedon Oct 17, 2023
Branch updated: It'll print the number of presets received (should be 48) and the 7 packets, that contain the current settings. Expected are a
1c 01 04 …and1c 01 05 …as the first two.StillVoidingWarranties commentedon Oct 17, 2023
Thank you. Two logs, both resulted in
bronco_07.log
bronco_08.log
And another with a result in amp data:
ERROR: Invalid amp id: 255bronco_09.log
StillVoidingWarranties commentedon Oct 18, 2023
I managed to capture a connection between the Bronco and the Fender Fuse software using Wireshark :-). I hope this will be helpful in unterstanding what is going on.
Connection_01.zip^
Here is an export of the raw data transmitted. I removed the first packets which I guess are associated with the Bronco's USB audio interface and the packets from the host to the Bronco since these seem to be just acknowledgement packets.
Connection_01_dissected_raw.txt
offa commentedon Oct 18, 2023
🤦 That's a problem. It should be 48 on your device (2x number of presets).
Update: For quick testing there's a fixed number now, could you give the newest commit a try please?
Interesting, the packets use some different values than those received over plug!?
StillVoidingWarranties commentedon Oct 18, 2023
Thank you. But still no luck (Invalid amp id: 189).
Log: bronco_10.log
offa commentedon Oct 20, 2023
But this time the correct amp packet is parsed. An invalid amp id is normal here as it's not mapped yet. 189 = 0xbd looks plausible. Do subsequent tests with the same amp yield the same value?
The first thing to fix is the wrong number of presets for Bronco.
StillVoidingWarranties commentedon Oct 20, 2023
Mostly yes. In my tests I sometimes got a different error on the first try but subsequent tries were consistent. Here are the IDs for the first 8 presets (amber bank, factory presets):
The ids repeat in the two other banks (green, red) because I left the amp models the same in the user presets and only changed the settings and effects.
On the second preset I did not get an "Invalid Amp" error but rather an "Invalid Cabinet" error (id 13). The controls of Plug don't seem to do anything, however. Here is the logfile of this connection:
bronco_preset_02a.txt
In the preset 10 (2nd in the green bank) I even got a connection without any error! However, trying to set an amp setting resulted in an Input/Output error. Here is the log for that:
bronco_preset_10b.txt
offa commentedon Oct 23, 2023
Yes, Bronco cabinets are likely not complete mapped yet.
UI needs some additional code too.
I have added some more code get some steps further:
Everything far from complete, but at least some steps.
StillVoidingWarranties commentedon Oct 23, 2023
Awesome, I will give it a try. In the meantime, here are some ids of the cabinet simulations the bronco uses. I took them from the FUSE backup files, there they are called "ControlIndex 17". Maybe these are the same ids that are received from/sent to the Bronco. I listed them in the order they appear in the FUSE cabinet selection.
StillVoidingWarranties commentedon Oct 23, 2023
Next, I will try to find out the ids of the effects of the Bronco.
Post Gain
StillVoidingWarranties commentedon Oct 23, 2023
I can confirm. As long as there are no invalid cab ids the connections are successful and show the correct id in the debug output.
When I connect with an amp model active other than the 59 Bassman the Amplifier dropdown text is just empty. When I open the dropdown it shows the Mustang amp names (Fender '57 Deluxe, Fender '59 Bassman, Fender '57 Champ, ...)
This seems to work. I changed the Treble and Bass settings in Plug and verified in FUSE that they have been indeed saved to the preset in the amp. Great progress.
Even better, all other amp settings like tone control, USB gain, noise gate settings (even custom ones) are read and saved correctly. Also, all effects settings were read and saved correctly with the exception of the four overdrive effects that are still unknown to Plug. I added the ids of these effects to the table above. This looks very close to a fully working version.
offa commentedon Oct 24, 2023
These are good news! 😄
offa commentedon Mar 23, 2024
The current architecture makes it quite challenging to support new devices unfortunately. And there's no proper way to do it right now :-/.
StillVoidingWarranties commentedon Mar 23, 2024
Sad to hear. Maybe one day someone will have the motivation to do a refactoring or rewrite. Thank you very much for looking into this anyways.