Sounds like the same problem I had with my rsp1 after I upgraded to API 3.11. I would say unplug your rsp1 and plug it back in again and see if it generates a different serial number on the screen you posted. I asked the tech support if there was a way I can change the serial number on my rsp1 and they said that there wasnt a way cause it didnt have a EEPROM in the rsp1
Heres the email I got from tech support from SDRPlay regarding the same problem:
"
Here’s the email
“The RSP1 has no embedded serial number. The only record of the actual S/N is the label printed on the underside of the unit
The problem that this created is that if the user has two RSP1s, then there is no way to distinguish between the two devices.
A change was implemented in v3.08 of the API to generate a 'random' S/N for each RSP1 in software to allow the two devices to be distinguished.
Clearly this has implications for other software that we were unaware of and in fact, you are the first person to flag this as an issue.
I am afraid that I have no idea why you are having a problem entering the new S/N into the configuration file for DSD+ Fastlane as this is not software that we use ourselves. I can only suggest that you revert back to v3.07 of the API, or contact the author of Fastlane to see if they can help you on using the alternative S/N that is created by later versions of the API. In the meantime, I will ask the S/W team the review this feature to determine how useful it actually is and whether we may be better to revert to the old approach in the next version of the API.”
Regards
Tech_Support
also heres the thread I posted on Radio Reference back in March dealing with the same problem
Ive been using DSDPlus with Fastlane for quite a while now with my RSP1 & 1A. I had API version 3.07 but I had to upgrade it to the newest one which is 3.11. My RSP!A works fine but now my RSP1 serial number has changed and when I put it in the fmpp config file, it wont open and gives me the...
forums.radioreference.com