The rear encoder shafts are not removable. It's theoretically possible to cut off the rear shaft but you'd have to be very careful not to put too much sideways force on the shaft or you could damage the motor internals. You would also have to ensure no debris from the cutting makes it's way into the...

If the work computer (Phidget21) is the one that has the Phidgets physically attached, then you're limited to the 1018_2B and other older Phidgets. You can have your personal computer be the one that actually runs the program, you'd just have to install Phidget21 (ideally same version number) in ord...

There is no 1013_3B so I'm assuming you mean the 1018_3B. Unfortunately, the 1018_3B has a newer processor chip that is not supported under Phidget21. For this reason, we still sell the 1018_2B which is compatible with Phidget21. Similarly, any VINT hub or VINT device like the HUB0000_1 or OUT1000_0...

That is correct. The DCC1100 is controlled with the VINT protocol, which is a communication standard made by Phidgets to provide maximum data transfer speed and minimal vulnerability to interference for our devices. There is no Arduino library for VINT communication. So you need to use a VINT Hub of...

Phidgets can run in a closed system, but you need to have a computer as part of that system. This means using either a desktop computer, laptop, single-board computer or raspberry pi running one of the operating systems supported by our libraries (Windows, MacOS, Linux). The code for your project ru...

We already spoke over the phone, but I'll summarize here in case it helps anyone reading this thread. - The above list was missing a thermocouple interface, we recommend getting two TMP1100s, because isolated thermocouple interfaces are recommended when the thermocouples are going to be bolted into ...

Since the STC1005 is a newer device, it sounds to me like the firmware on the HUB5000 is just out of date.

Go to the HUB5000 User Guide and scroll down to the advanced topics and click on "Updating the OS and VINT Hub Firmware".

A discrepancy between multiple thermocouples, or a discrepancy between the readout on your roaster vs. what's reported in artisan?

The CPR variable is set outside of the event handler, and only updated when the value is changed by the user.

You can find the code sample on the page you linked if you scroll past the code sample generator to the table below. It's the visual studio C# GUI example for the encoder object.

Q1- You're correct that the velocity calculation is a feature of the control panel example, not the API itself. Essentially it's using the timeChange and positionChange variables of the postionChange event to keep a running average velocity. Q2- You can't have a Phidget channel open in both your own...