I'm using NodeJS to connect a barcode scanner to a web front-end. The barcode scanner's serial port runs to the PC (Windows7 pro x64) through a usb-to-serial converter. I'm using node-serialport. This setup is running at an installation in a museum.
The computers reboot daily and sometimes the barcode scanner will work fine the whole day, but about 25% of the time it will stop working throughout the day. With stop working I mean that NodeJS isn't relaying the incoming serial stream anymore. The barcode scanner itself seems to be doing fine, it still bleeps happily and after a reboot it will function just fine.. until NodeJS stops working again.
When the scanner stops working the NodeJS windows doesn't show any error codes but it's fully unresponsive by then. By then it's seemingly impossible to close the NodeJS instance. I've tried Ctrl-C, ending the process through the task manager and using taskkill to kill the PID of NodeJS from a CMD window. They all have ZERO effect. When using Taskkill the CMD window will happily say that the process was killed, but the NodeJS window won't close and also still exists in the task manager. Only a forceful reboot will 'solve' this.
I feel I have very little information to go on. I'd love a few tips on what to try next.