-
Notifications
You must be signed in to change notification settings - Fork 68
laserweb3 no port #231
Comments
@openhardwarecoza This is a recurring user error. Maybe the PIN should default to disabled. I doubt the PIN is good for safety since machines tend to have a physical test laser button. |
This particular instance is an JS error somewhere in the stack (if pin is a text field instead of how it looks if the jquery plugin ran) When theres JS errors in the stack, things stop working (ie hiding pin, threejs, jquery for the port selection, etc) So @gbrinki , read the syslog near the top and tell us what it says |
thank you for your mail. Now I have made 3 screenshots of my Laserweb3
console. I do not know exactely but i think there have been found two
mistakes but i do not know how to handle them and would be glad if you can
help me, Thanks!
2017-02-15 18:36 GMT+01:00 Peter van der Walt <notifications@github.com>:
… Closed #231 <#231>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#231 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AYmTjOPgY26L6IOBXLo7mBPAirB7HlaLks5rczeqgaJpZM4MB9vU>
.
|
@gbrinki Please reread the text @openhardwarecoza highlighted in yellow before he bans you. |
(; yeah I am getting close... Anyway, thats a browser plugin preventing websocket access... Use a clean install of chrome without shit installed Or server.js is not running |
after installation and settings i have no possibility to choose a serial port.
![problem](https://cloud.githubusercontent.com/assets/25793420/22985020/7df0ed20-f3a7-11e6-85d0-7e586fd760b8.JPG)
second probllem
wich pin is asked to get the mashine started?
The text was updated successfully, but these errors were encountered: