Description

The a314-500 works fine when connected on its own. The aca500plus works fine when connected on its own.
When both are connected, the a314-500 can't be reached.

Testbed 0

In case other testers join in, they can describe their kit and give it a number, so it's easier to refer to different kits.

Hardware

a500: mb rev 6a, soldered for 1MB chip RAM.
a314-500: v1.2
aca500plus: T502 V5 15-may-2016

Software/firmware

a500: first I worked only with WB1.3, but now I have proceeded to WB3.1 as it has more features and it seems more people use it.
a500 + a314-500: https://github.com/niklasekstrom/a314 commit 2a03888 (Jan 5 2023)
aca500plus: Media:aca500+menu0.146.lha (30-Jun-2022)

Goals

0. To find a working configuration for this.
1. To figure out the reason why it does not work, in case no working config can be found.
2. If possible, find a workaround to that reason.

Open requests

If you have a similar setup as above, and have gotten it to work, if possible, please kindly post a comment with any or all of:

0. A photo of your aca500plus config screen.
1. A CF-card image with a workbench installation that has pi installed.
2. Any other note or comment about how you produced your setup.

These could provide valuable clues to us that can't get it to work.

Todo

I will document all currently tested aca500plus configurations.