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
The node-pre-gyp command builds a serialport driver which is located at:
node_modules/serialport/build/serialport/v1.5.0/Release/node-webkit-v0.12.0-alpha3-darwin-x64
But when canbus-triple-app is successfully built. It tries to load the module from:
node_modules/serialport/build/serialport/v1.5.0/Release/node-webkit-v43-darwin-x64
I tried symlinking it, but somehow, the app does not seem to communicate correctly with my device. In the console, an empty log line is output:
[16349:0228/220353:INFO:CONSOLE(254)] "", source: file:///Users/trippelm/src/CANBus-Triple-App/build/CANBus%20Triple/osx64/CANBus%20Triple.app/Contents/Resources/app.nw/www/js/services/SerialService.js (254)
Seems like that is a console.log(device), and that device is empty. But it is empty even when I select the correct serial port in the list in the gui. So seems like the device name gets lost somewhere.
The text was updated successfully, but these errors were encountered:
The node-pre-gyp command builds a serialport driver which is located at:
node_modules/serialport/build/serialport/v1.5.0/Release/node-webkit-v0.12.0-alpha3-darwin-x64
But when canbus-triple-app is successfully built. It tries to load the module from:
node_modules/serialport/build/serialport/v1.5.0/Release/node-webkit-v43-darwin-x64
I tried symlinking it, but somehow, the app does not seem to communicate correctly with my device. In the console, an empty log line is output:
[16349:0228/220353:INFO:CONSOLE(254)] "", source: file:///Users/trippelm/src/CANBus-Triple-App/build/CANBus%20Triple/osx64/CANBus%20Triple.app/Contents/Resources/app.nw/www/js/services/SerialService.js (254)
Seems like that is a console.log(device), and that device is empty. But it is empty even when I select the correct serial port in the list in the gui. So seems like the device name gets lost somewhere.
The text was updated successfully, but these errors were encountered: