Getting a Coyote v2 to co-exist with a Coyote v3 possible?

eeetteee

Hi all,
I have an older Coyote v2 that I wanted to add it to Multi-Device. Looks like we are currently limited to Coyote v3 Bluetooth support. In the past, I've connected to the v2 as a Legacy Device audio room using XToys and system audio.

Is there any work around to make this work?

KairosJS

I'm not sure as I've never used a coyote2 or any coyote with audio. But if you made it work using xToys in the past, maybe you can:

create the two areas with BT Coyote3
And two areas as Stereo or 2B Stereo (choose what you used as audio back then), for your coyote2 setup.

Test carefully!

eeetteee

Thanks for the reply. A lot easier to interface with you here rather than over in reddit r/estim XD

I just tested it

Defined Estim Settings Multi-Device four Areas total = 2x for 2B use External Device, 2x for Coyote v3 use BT
Connected to Audio Room MZWBO, tested Pleasure/Pain Calibration for A/B and heard signals in System Audio
Selected Scenario Pain Lab w/recommended Persona, Local EstimAI Gemma4 12B, Local TTS ChatterBox(Voice plays), Predefined Gallery
Estim Settings defaulted to Multi-Device, had to manually click Legacy Devices (to select/highlight)
a) Clicking on 2B Stims lib and nothing played in System Audio, had to Click on a 2B focus Area setting and refresh the Audio Room URL in another tab, then tested Play Pleasure Calibration and verified sound, X to close
b) Tested 2B sims lib and this time they played in System Audio now
c) Clicked on BT button to connect to Coyote v3
d) Started the Scenario and it was hit or miss. Sometimes it started with a Stim, other times it didn't (when it should)
e) further testing needed

KairosJS

Maybe I misunderstood what you explained, but you must use the Multi-Device feature with all four areas created. This won't work with a legacy device (unless you only want to use one device).

To do the testing, I recommend using the scenario "The Experiment." You can directly ask Amilia to use specific stims on specific areas, or everything at the same. Don't ask for impossible things, such as a shock on an area that you configured as "no pain."

One last thing, smaller models may have issues handling the complete stim command with 4 different areas in multi-device.

eeetteee

KairosJS Thanks for the scenario recommendation. I will test that. Let me try to explain my test further for you.

I was testing with Multi-Device and Legacy Device active at the same time. At least, that was what I thought because both were highlighted. For some reason, I couldn't get any stim sounds through System Audio without activating Legacy Device and the audio room URL during a scenario. This was evident when I went into Estim Settings and activated the audio room and confirmed calibration sounds prior to entering the scenario. Entering the Scenario, something changed with the setup.

Within the scenario, Multi-Device actually displayed the 4x areas with 2x devices correctly, however, when Multi-Device was selected by itself, there was no stim calibration sound coming from the 2B stims play buttons. 2B stims should be playing to System Audio as a Legacy external device for this to work. So, to re-iterate, I configured the Coyote v2 as a 2B non serial remote device (via external device config).

When I clicked on Legacy Device, the Multi-Device button and content continued to stay active and displayed correctly. Once I went through the audio room connect again for the 2B, system audio and the calibration buttons produced sound again. Clicking on the 2B stims produced sounds.

Multi-Device displays the BT Coyote v3 correctly next to the 2B with its list of stim sounds. I need to verify this works when I have more time since the only way to test it is wired up.

The System Audio option allows you to listen to the stim patterns in real-time along with the TTS during the session.

Smaller 8-bit models like Gemma 4 12b and v3.1 Claude 3-5 Sonnet seem to work fine with local TTS ChatterBox, but for some reason Mistral (qwq-12b-test-q6_k.gguf) hangs during the generation stage consistently.

Perhaps these smaller local models could be the cause of not starting stims at the beginning of scenarios (yellow warning message) even though there most definitely should be. Is this a problem with the AI not interpreting the user response correctly or is it related to not being able to load an associated stim? Would the subscription route be more consistent with stims using the bigger models/cloud power?