So I did run into a few issues getting Intiface Central setup myself, so hopefully I can provide a bit more helpful info for this.
I assume you were following mnh86’s example for setting up the firmware with Intiface. If you have MFP working then hopefully your connectivity module was properly setup.
In that case, there’s a few things worth double checking with the Intiface setup:
The quickest thing to check would be making sure “Serial Port” is toggled on in the “Advanced Device Managers” section of the settings. Just to make sure!
Next, let’s talk about the the buttplug-device-config.json file. For me, any time I had an issue, it was relating to this file. There are instructions for setting this up on mnh86’s Github, but I’ll walk through the process here to attempt to catch any potential issues that could happen:
So after opening the config file C:\Users\(User)\AppData\Roaming\com.nonpolynomial\intiface_central\config\buttplug-device-config.json, we want to find the block labeled “tcode-v03”. By default, it should look like this:
"tcode-v03": {
"serial": [
{
"port": "default",
"baud-rate": 115200,
"data-bits": 8,
"parity": "N",
"stop-bits": 1
}
],
"defaults": {
"name": "TCode v0.3 (Single Linear Axis)",
"messages": {
"LinearCmd": [
{
"StepRange": [
0,
100
],
"ActuatorType": "Position"
}
],
"FleshlightLaunchFW12Cmd": {}
}
}
},
Now before I explain anything else, it might just be worth attempting to replace that whole block with all the modifications at once. If the config is still in its default state, then go ahead and select that whole block (make sure to get it all the way down to the final curly brace and comma) and replace it with this:
"tcode-v03": {
"serial": [
{
"port": "COM4",
"baud-rate": 115200,
"data-bits": 8,
"parity": "N",
"stop-bits": 1
}
],
"defaults": {
"name": "NimbleStroker Connectivity Module (Serial TCode v0.3)",
"messages": {
"LinearCmd": [
{
"StepRange": [
0,
100
],
"ActuatorType": "Position",
"FeatureDescriptor": "Up/Down Position (L0)"
}
],
"ScalarCmd": [
{
"StepRange": [
0,
100
],
"ActuatorType": "Vibrate",
"FeatureDescriptor": "Vibration (V0)"
}
]
}
}
},
Starting from a default config, I have replicated doing this replacement and the device will show up when scanning. But let’s still look at this in detail:
First, we want to make sure the “port” option is correct. You said yours was listed as COM4, so I went ahead and put that in the paste. For me, it was COM5, so that’s what I used instead.
I think the main other thing that could go wrong is the json code being malformed. This could be the result of a comma or curly brace being out of place. That is why I suggest starting with the default file and pasting over the exact lines I posted. If you edited the default manually, it’s possible an error could’ve been introduced that way. Notably, the line "FleshlightLaunchFW12Cmd": {} could’ve messed things up too if it was left in there, since it might’ve looked like it was the start of a different block instead.
The final piece of advice I have is that if the json code is messed up at all, Intiface will show an error on launch and reset your config file. Keep an eye out for a red triangle icon in the top right corner and recheck your config file in case anything goes wrong. For various reasons, I’ve had my config file reset on me, so even if you think you got your config correct, just give it a look to ensure the changes you made are still there!
