Is there a “Known Good” commit of the LaserWeb4 repository that works with Raspberry Pi? I’m having a devil of a time getting LaserWeb4 to work properly on a pi. Even if I get “npm start” to produce a website (by changing the webpack settings to enable more than just localhost) I get an error saying / is not found and webpack fails to generate the site.
Is there instructions or a tutorial somewhere for going from repo to hosted server for LW4 on the Pi? I’d love any input others may have on this.
@cprezzi How do I cause the server to listen to 0.0.0.0 instead of localhost for lw.comm-server? I tried changing all of the instances of ‘localhost’ I could find in server.js, but the app still starts saying: “Use http://127.0.1.1:8000 to connect this server.”
@cprezzi - so I worked around the issue by changing my hosts entry for my local hostname to ‘0.0.0.0’ – obviously the worst possible workaround for this, but, it worked If you have a method of changing the ip address via code or command line argument, I’d still love to hear about it. Thanks for your work on this!
Finally, I realized: that hosts entry hack just changed the text on the screen. In reality, it was binding to 0.0.0.0 the whole time, it just used the ip address from the hosts file to populate the string literal. I feel like an idiot, apologies.
The NodeJS server just listens on the default interface on port 8000. You should not need to configure something. The string you get in the start-message is comming from the environment, but could be wrong. Just get your network config with “ifconfig” and use the correct IP.
If you run into performance issues (for example lasering raster images with more than 25 mm/s, causing the Pi CPU to peak at 100% and doing a lot of jitter) you could consider running a ser2net server on the pi and forwarding the serial port to your powerful PC, where Laserweb4&lw-commserver have enough CPU.
@Michael_Schindler Did you make any tests with ser2net?
As I wrote, I did not find any performace issue on Pi 2b, if only the node server is used (which is a serial to websocket bridge).
I don’t belief that bridging the serial connection through ser2net -> net2ser -> lw.comm-server could be much faster.
For what its worth, lw.comm-server on a pi3 is working just fine for me, I have no complaints. Thanks again for pointing me in that direction @cprezzi !
