I can use a WebSocket connection, please check the WebSocket configuration yourself. I am not the original author, and I do not know how to add a serial port.
1 Like
Still, I concur, native serial connection would be great, as that’d would allow CoyoteSocket to work with EDI
I agree, its great. I was just hoping to get a sense of what settings are working well for people.
I get that a degree of experimentation is necessary, and is half the fun, but don’t have a good understanding of settings like “freq balance” and “int balance” actually do. I also didn’t realize (until seeing your screenshot above just now) that I could make some of these settings static by deselecting all axes.
Haha, I don’t have a particularly clear understanding of settings like “Frequency Balance” and “Intensity Balance” either, so I’ve just kept them static and only let the intensity remain dynamic. I’ll add more once I figure out what those parameters actually do later on.
1 Like
CoyoteSocket can now be used with EDI, so a serial connection isn’t strictly necessary. However, there are quite a few parameters, which can be overwhelming. Also, my EDI crashes frequently, and I’m not sure why.
Open the advanced security firewall:
Method 1: Press Win+R, enter wf.msc, and then press enter.
Method 2: Control Panel>System and Security>Windows Defender Firewall>Advanced Settings.
Create a new rule:
Select ‘Inbound Rules’ on the left and click’ New Rule 'on the right.
Select rule type:
Port: For a specific port (such as HTTP port 80), select the TCP/UDP protocol, enter the port number (I select all local ports), and then select “Allow connection” for operation. Enter the name ‘coyote’, that’s it
Do you plan to post the source for this anywhere, or do you plan on making more updates? The current version is working pretty well, but the code to decay to minimum when there is no input, is not working. As soon as the script input stops, my coyote goes to maximum instead of minimum.
Fantastic work though. Thanks for your efforts!
GitHub for Coyote Socket is here. I turned off the decay function too, also found sometimes it felt like the response speed would start feeling choppy and that would be fixed when I’d temporarily pause the output.
1 Like
Hey all - we’re building MotionStim, a web platform for synced playback and toy control, and we’re looking for early users + honest feedback.
It is supposed to be a closed system video player, funscript parser and coyote itegration in one. Login is not required, guest mode supports all features:
What MotionStim does right now
- Scan your local video library
- Auto-match videos with funscripts
- Upload your own funscript if needed
- Run playback + toy control in one interface
- Use modulators to shape how motion feels
- Current supported device: Coyote V3 (E-Stim)
Modulators (this is where it gets fun)
Not just basic sync - you can tune the feel live:
- Intensity (base feel + response curve)
- Frequency Top (change sensation near top position)
- Staggered (delay channel B for offset feel)
- Signal Inverter
So it’s not only “play script = output” - you can dial in your own style per session.
What we’re building next
- More toy/device support
2 Likes
Thanks for the PR. I’ve reviewed, merged, and made a new release, v2.3.0 is now live with Coyote 2.0 support!
Hey, could you upload the edited EXE file to GitHub? I don’t know how to use the source code. Thanks.
1 Like
Just made a thread for this and included a link to where you can download the EXE on GitHub.
Coyote Socket - A DG Labs Coyote GUI
Heya, this is looking awesome!
I may be the only one with this feature request, and I don’t know if I got a weird Coyote or what… but the thing is OVERWHELMINGLY POWERFUL in the normal mode for me. Like… literally… running the power from 1 to 2 (on a scale of 200) is excruciatingly painful (and I’ve used stereostim setups for years… so I’m not just trying it on a ‘pain’ setting - I’ve poked around with a lot of different kinds of signals.)
When using it only externally, I can survive up to about 10 or so. lol. But internally… 1 is too powerful.
The Coyote App has a ‘soft mode’ toggle that you have to turn on every session that scales the output WAY down… so you can still use the full 1 to 200 range, but it’s scaled to a lower max, rather than just capped to 10, like most 3rd party apps offer in the setup.
So that’s the feature request - a ‘soft mode’ that gives full resolution on the input but lets you scale the output instead of cap it! Have you found english language documentation/samples for the coyote API? I took a look but their github page was entirely in chinese and my autotranslate wasn’t complete enough for a first glance, because I was thinking about trying to add it to a tool myself.
I’d love a PC based scriptplayer / tcode translator that also offered soft mode. Having to ONLY use the coyote app has been a drag!
Just added it in the latest version 
You can now limit the max strength per channel to whatever you want. “Soft Mode” sets both to 50%
Grab the latest on GitHub
1 Like
How exactly does the Lovense API thingy work? Does it work with Game that have Lovense Integration now?
Yeah, I only have one game that I tried it with, but basically you just point the lovense connection at the machine you have Coyote Socket running on at the port you have configured and it’ll connect. It basically just wraps the buttplug handling with a shim that allows lovense games to connect.
yep, serial ports support should be implemented in your app @maps524, it is needed to use your tool with Virt-a-Mate plugins for e-stim (only one way)