You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New error from the Easel interface when running /setup...
"The Easel Driver doesn't support your machine"
Updating the project files with libraries from the latest EaselLocal (0.3.10) cleared the error, but even with some fiddling to merge the updates from iris.js to index.js (SSL was added) and changing the version number, Easel was getting stuck while trying to connect "Connecting to X-Carve…".
Debugging the xcarve-server in Node, the opening of the serial port seems to time out after a minute or so?
/usr/local/lib/node_modules/xcarve-server/lib/serial_port_controller.js:54
thisPort = new SerialPort(comName, {
^
TypeError: SerialPort is not a function
I updated SerialPort and socket.io dependency versions specified by EaselLocal 0.3.10, and added the new "abilities" to package.json from EaselLocal 0.3.10. I can now successfully connect to the X-Contoller and move the gantry.
Sorry if this isn't very helpful. I'm new to Node.
The text was updated successfully, but these errors were encountered:
New error from the Easel interface when running /setup...
"The Easel Driver doesn't support your machine"
Updating the project files with libraries from the latest EaselLocal (0.3.10) cleared the error, but even with some fiddling to merge the updates from iris.js to index.js (SSL was added) and changing the version number, Easel was getting stuck while trying to connect "Connecting to X-Carve…".
Debugging the xcarve-server in Node, the opening of the serial port seems to time out after a minute or so?
I updated SerialPort and socket.io dependency versions specified by EaselLocal 0.3.10, and added the new "abilities" to package.json from EaselLocal 0.3.10. I can now successfully connect to the X-Contoller and move the gantry.
Sorry if this isn't very helpful. I'm new to Node.
The text was updated successfully, but these errors were encountered: