Mustang V v2 amp not recognized.

[beelzebud]

Plug v1.2.1 identifies the amp and works correctly, but this version does not. I'm not sure what the difference is. If you need any info from the Mustang V v2, just let me know and i'll get it.

[offa]

Thanks for reporting. Can you check die usb vid / pid of your amp (eg. using lsusb)? It should show a vid of 0x1ed8 and a pid of either 0x0014 or 0x0016 (supported pid's).

[beelzebud]

Ok today I had a chance to see the output of lsusb. In normal mode the amp reads 0x0016, and in maintenance mode it reads 0x0017

[beelzebud]

Also if it helps, the old software recognized the amp at v1.2.1. https://bitbucket.org/piorekf/plug/src/default/ is the version that works with the MustangV v2.

[offa]

The vid is still 0x1ed8? The supported pid's don't have changed between both versions and 0x0016 is still available. What kind of error do you get btw.?

Since there's a working earlier version, the udev rule or other permission issues aren't the root cause.

If you have some time left, you can use git bisect to figure out the causing commit. There are tags for the mercurial v1.2.1 and initial importing commit. Unfortunately I don't have a V2 around.

[zavorra]

Hi, I didn't noticed this issue, so i forked your project and added an initial support for V2 amps.

To be more precise, my Mustang II V2 was recognized and works correctly, but plug lacks the "V2-only" features (some mod, stomp and amp).

moreover, I am trying to fix some weird issue on raspberry pi with USB communication, and changed something in USBComm to handle transmission retries (as in mustang-midi-bridge). Some other changes including loadfromfile to handle (maybe) incorrect fuse files.

Still no changes in updater

Could you please review my changes and in case take them into account?

You can find them in https://github.com/zavorra/plug.git

[offa]

Still no changes in updater

Are there still updates for V2? V1 is dead.

Great to see people working on this! Feel free to submit PRs – either here or on Gitlab, whatever suits best for you.

[Snayler]

Getting a similar issue on a Mustang IV V2.

lsusb output as follows:
Bus 002 Device 007: ID 1ed8:0016 FENDER MUSICAL INSTRUMENTS CORPORATION Mustang IV v.2

On the GUI it only says:
Error: Failed to open usb device

Are there any log files that I can check?

Are there still updates for V2? V1 is dead.

The latest firmware update for V2 is 2.2, it's some years old and with fender removing support for Mustang V1/V2, I doubt there will be more updates.

[offa]

VID / PID look good, so the application should pick it up correctly. The error indicates there's no device found though. Does this happen always?

Just to be sure: udev rules are installed and working?

Are there any log files that I can check?

Unfortunately no, the application itself doesn't write any logs yet. Maybe you can get some hints through the system logs.

Are there still updates for V2? V1 is dead.

The latest firmware update for V2 is 2.2, it's some years old and with fender removing support for Mustang V1/V2, I doubt there will be more updates.

So the situation is the same as V1. 👎
Is there a still a reason to keep the updater code? If so, it definitely needs some improvements.

[Snayler]

Just to be sure: udev rules are installed and working?

Ok, the issue was I forgot to create the plugdev group and add my user to that group. Might be a good idea to include the same note piorekf added to his wiki to your README.md file.

Could also be a good idea to change the links to a wayback machine link, since apparently piorekfs repository is no longer available.

Is there a still a reason to keep the updater code? If so, it definitely needs some improvements.

Could be useful if someone is still running an older version of the firmware and wants to update. Some digging would need to be done to find the firmware files, as fender decided to stop hosting everything Mustang V1/V2 related. I keep a backup of everything on my computer just in case.

On another note, have you included anything from zavorra's repo?

[offa]

Ok, the issue was I forgot to create the plugdev group and add my user to that group. Might be a good idea to include the same note piorekf added to his wiki to your README.md file.

make install takes care of the udev files already. Is it a good idea to include another target, which installs the udev files only (in case someone wants the rules, but not the application installed)?

Could also be a good idea to change the links to a wayback machine link, since apparently piorekfs repository is no longer available.

Good point, all links back to Bitbucket are dead now. Well done Atlassian.

Could be useful if someone is still running an older version of the firmware and wants to update. Some digging would need to be done to find the firmware files, as fender decided to stop hosting everything Mustang V1/V2 related. I keep a backup of everything on my computer just in case.

The updater code is still there, but the updater is disabled in the UI (however, just a boolean to flip). Let's see if someone realy needs it.

On another note, have you included anything from zavorra's repo?

Not yet.

[offa]

Coming back to the origial issue: To get some more infos out of the USB device error, it's neccessary to replace the related libusb code, allowing error handling. It shouldn't be difficult though. But at this point it's worth thinking about replacing plain C libusb calls with something improved, eg. libusbpp or libusbpp11 (suggestions welcome).

[Odzinic]

I'm unsure if I'm experiencing the same issue, but I have been receiving a ERROR: Invalid amp id: 0 error for my Mustang I (V.2) with a lsub output of ID 1ed8:0014 FENDER MUSICAL INSTRUMENTS CORPORATION Mustang I (V.2).

[offa]

@Odzinic what version are you using? The usb vid / pid are ok.

[Odzinic]

@Odzinic what version are you using? The usb vid / pid are ok.

1.4.2 compiled from git yesterday.

[offa]

Could you test with latest master? I've rewritten most of the USB code. You can enable additional libusb logging by setting LIBUSB_DEBUG.