LaserWeb4 (0.4.0) Serial communication done ! need testing 
So what’s the current install / run process. I there a new server ( I installed one). Also are we testing just the connection is elf or is there any way to interact with the connection?
@Ariel_Yahni_UniKpty Sorry for the lack of details.
And what you think about the console in the left panel ?
Just add disconnection on page reload/refresh.
@raykholo can I have one of those Keychain smoothie stamps to carry with me?
Well yes and no, maybe. I would love to have at this very second something portable to test the COM. 
Is this an addiction?
Maybe v2 should have a keychain hole and a JST connector for a lipo battery that can be adhered to the bottom layer.
Oh, and before I came up with this, I wanted a smoothie flash drive - which was essentially this but with the male USB connector as part of the PCB.
I appears to test as expected.
For those running from Mac or Linux there has been a change in the port number and the dir structure.
The port is now 8080.
When running on the command line from node you’ll need to cd to the server dir and run server.js to start the server.
I can submit a pull request for the readme or put it into the wiki if you feel that info is needed. It’s something an node dev should know but since the testing base is more of a user base than a dev base it may make sense to provide a bit more instruction than if it was a dev community.
@dstevens_lv I’m able to run the server from the root of the LW4 folder.
I’m unable to use localhost as an alternative to my ip. Why is that?
@Ariel_Yahni_UniKpty now you can connect on localhost or 127.0.0.1 
Thanks, I’m was looking for those users with isolated machines maybe
@dstevens_lv make sense to put this on the wiki and if you want i can change the port number or put this kind of settings in a config file ?
@Ariel_Yahni_UniKpty it was not wanted, thank you for pointing that out.
@Sebastien_Mischler I think as long as it’s clear what port it’s on, it’s not an issue though for consistency with the previous version 8000 might make more sense. I think asking the user to choose a port may cause more issues than it solves. I think most users of laser cutters aren’t familiar with server ports.
If you package the app and autoload a browser then selection would be irrelevant but if you use a port that’s allready used by another app/service then that could cause trouble. Maybe use a custom port for laserweb?
