Do.your controllers have the same name ??? I saw you forced the player 1 controller. If your nes and psx pad both have the same name, recalbox can't know which is which 
That's the problem? How can I rename it?
When I Configure a controller both are called Gamepad.
Can I solve the problem anyway?
mmhhhh udev can't rename devices as far as i remember. Both your pads are USB ? Or they come with adapters ?
Am I the only one who has that problem?
Can I change something in the configuration files?
The controllers are new and all work.
I found this: https://github.com/recalbox/recalbox-os/issues/5
Maybe you can say me, what i must change.
no, better try http://askubuntu.com/a/722906
Let me explain : devices are handled by udev. But you can "force" some behaviours of udev, one could be to rename your pads
Even http://blog.petrockblock.com/forums/topic/using-udev-rules-to-assign-persistent-names-to-joypads/ has the very same problem as you
Thanks very much subs. I have tested it with your first link (Case A). It doesn't work. 
Case B, it does not concern.
Assign USB ports with ID_PATH in udev also makes no sense, because there are 8 Controller.
Did you have another idea?
Could I solve it with RetroPi?
Here what I did according to your first link:
You should first connect with SSH and mount -o remount, rw / as the root filesystem is read only for better stability
Next, please run /recalbox/scripts/recalbox-support.sh and upload the resulting archive so thtat i can check a few things by myself
The output as follows: http://ul.to/pdns3861
Could it be a solution, the individual controller when I save for each emulator, if possible?
http://github.com/recalbox/recalbox-os/wiki/How-to-use-custom-config-for-emulators-(EN)
well ... It's worth a try, can't promise it will work. The downside of that method is that you may need to set it for evey emulator unless you don't use N64, Kodi, moonlight and scummvm. If so, you could add to recalbox.conf global.configfile=..... replacing the dots with the full path to your custom file
Ok, thanks very much sub. I will try it later.
And what do you think, if I use a USB-hub and then make a udev Rule with ID_PATH as described in the last post from the first link? I'm not sure, but when you see the second link, I think the author had problems with a USB-hub and udev-Rule. Are you the same opinion?
@subs said in Beginner: Why does not Recalbox remembers the controller layout for each controller? No-Name-Controllers, Chinaware:
no, better try http://askubuntu.com/a/722906
Let me explain : devices are handled by
udev. But you can "force" some behaviours of udev, one could be to rename your padsEven http://blog.petrockblock.com/forums/topic/using-udev-rules-to-assign-persistent-names-to-joypads/ has the very same problem as you
I'm not really familiar with udev, just know a few things about it. I might test at home some rules to rename some pads as i have several PS3 clones that have the same name
Have you read the link on retropie ? bad idea in fact
I started with the configuration for each emulator.
What do you mean with global.configfile=..... why not nes.configfile=..... for example? It's important for me to know that. I'm going to learn retroarch very quickly.
Tjat's a recalbox parameter file, not retroarch.
If you use the global keyword, it means that you force custom configs for ALL emulators, even non retroarch ones (mupen, kodi, moonlight, scummvm)
Yes but can you explain me something:
I only connect the one (!) specific controller to a usb-port and then I start a game in the specific emulator (for example snes) and start retroarch to make the configuration. Then I Save new config for this controller with his specific buttons.
If I would like to game SNES someday, I connect the SNES-controller to a usb-port and I start a SNES-game. recalbox.conf starts for me the specific cfg-file that I have configured (snesright.cfg for example).
I make also a cfg-file for PSX, etc. etc. there all need a seperate cfg-file because the controllers are different for each emulator. So why global.configfile= and not snes.configfile= ?
Or I understand something wrong?
Thanks very much.
The system name is the one in the roms folder
Tbh, you'd better buy another pad for 10 €/$ from a different brand, it's worth the trouble you'd avoid. It's gonna be really complicated for you
It works. With manual configuration for each emalutor in RetroArch it works. And it works also for multiplayer with more of the same controller.. But it's a little bit dangerous with the device index in RetroArch, but it works.
It was a simple question, why did you want to use global.configfile=. I can not understand. That's all. I want to learn and have now learned a lot - for me and my friends!
I now have an overview and can now googling individual pieces.
Thanks very much subs!
the global.configgile would have forced custom config files also for moonlight, scummvm, mupen and kodi
Vy the way : congratulations for solving your problem! was not the shortest solution, but at least you can enjoy recalbox now 
Thanks.
Yes, but if I make configs for a SNES-controller for example and use the global.configfile variable instead of snes.configfile then the controller layout also applies to NES, PSX, etc. or not? If yes, can you tell me why that makes sense? Because each emulator like PSX, NES, etc. have his own controller.
For me: NES, PSX, etc. are emulators and this was your post:
@subs said in [SOLVED] How to configure several No-Name-Controllers, Chinaware with the same name in recalbox:
Tjat's a recalbox parameter file, not retroarch.
If you use the global keyword, it means that you force custom configs for ALL emulators, even non retroarch ones (mupen, kodi, moonlight, scummvm)
If yes, can you tell me why that makes sense? Because each emulator like PSX, NES, etc. have his own controller.
NO. specifying a configfile means that the autoconfiguration will be disabled. You can make it for a single system, or blindly for the whole recalbox.
You should first connect with SSH and mount -o remount, rw / as the root filesystem is read only for better stability
Next, please run /recalbox/scripts/recalbox-support.sh and upload the resulting archive so thtat i can check a few things by myself
