laserweb / laserweb4-binaries Goto Github PK

View Code? Open in Web Editor NEW

307.0 307.0 56.0 1.59 MB

Installers for LaserWeb4

License: GNU Affero General Public License v3.0

Shell 21.01% Batchfile 30.06% JavaScript 48.93%

laserweb4-binaries's Introduction

DEPRECATED!

LASERWEB3 is available! See https://github.com/openhardwarecoza/LaserWeb3 for details!

laserweb4-binaries's People

Contributors

Stargazers

Watchers

laserweb4-binaries's Issues

white page on launch of app

hi. thank you for the hard work. ive run across a problem, i wish to request some assistance. the laserweb worked on my laptop this morning and i was trying to work thru some tutorials when the progr4am just turned the screen white. ive uninstalled and reinstalled a couple times but now if i click on shortcut it goes to white screen with laserweb in upper left hand corner. im running the current laser web from gthub. im on a windows 7 pro machine that i still use for video editing so i assume its not the machine. ive downloaded the software each time ive tried to reinstall. im kinda at loss as to why this is happening. thank you if you read this and hopely there is a solution. jmartens

How to get latest as .DMG ?

There is something I probably don't understand, but for each latest release there is often .exe and .yaml, but no .dmg, how can I manage to get those? Thanks

generating "laser cut" paths slow and not complete

when "laser cut" generated from large dxf or svg file most of paths are missing and takes very long time to generate. If i import same file with laserweb 3 takes couple of seconds and generates all paths. Files are exported with corel draw.

Any plan to support android device?

I tried run nodejs on android , it's working in demo, but install comm server no luck.

build.osx.sh fails on Arch Linux

First, it complained about yarn not being there, but that was an easy fix. But then there were so many errors I don't know where to begin. I've created a log of the build and attached it.

build.log

v4.0.998-136 Marcos Bug

Error on any macros button pressed.

Issues with gcode generation for big svg (about 20mb)

The execution of the program stop after exactly one hour. Must be a maximum delay that's shutting down the process after an hour. How can I address this ? Thanks :)

White screen on startup (Windows 10)

This looks like an old and common issue, but I can't find a resolution that works for me.

I just installed LW4 4.0.998-136 on my Windows 10 machine and I get a white screen on startup.
(Windows 10 Home, Version 1909, OS Build 18363.1198.)

I tried uninstalling and reinstalling and tried both 32 and 64 bit. I ran System File Checker and Compatibility Troubleshooter. All with no luck. Also removed ~/Library/Application\ Support/lw.comm-server/ also with no luck.

Any help will be appreciated.

Where is the .dmg (for OSX)

Where is the .dmg (for OSX)?

Unable to Build/Package anything

I'm attempting to modify the LW4 frontend and I've been trying to find a way to package everything for release. At this point, I don't care if that release is in the form of a docker image, native app (OSX, Windows, Linux), or whatever. I have tried what feels like everything under the sun, but no luck. Every error I talk about was reproducible for both my forks of LaserWeb4's stuff AND the official repos. They were also reproducible on both MacOS (my machine) and inside a Ubuntu VM. I've also tried ./build.osx.sh with node versions 10.16.3, v12.22.12, and v20.0.0 (just as a hail-mary). I could be approaching this all wrong and if I am, I'd appreciate more information on how the maintainers do their releases. Do those build process even work still? I've attached a build log from ./build.osx.sh

build_osx_2.log

Edit: I've also tried building the docker containers in the LaserWeb4 repo, but my changes to the frontend never copy over to the image and it's honestly baffling. I found out the npm run bundle-prod command is throwing a lot of UglifyJs errors and failing and my guess is that is a sign of the source of the docker problem. Here is a log of npm run bundle-prod:
bundle-prod.log

Hello Need Help

Hello Good Morning !
im Using LaserWeb4 Now and is good application So Far
But i have Some Question ?!
im using Grbl 1.1 So i set Machine Profile is Grbl That is Right ?!
and i Changed PWM to 12000 For My laser !
if there any setting i must set it be4 i work Becuse when im engrave photo i got Result Not Good idk Why Can u help me with this question`s
thnx

Documentation site closed down ("CNCPRO.CO").

A note: the "Documentation" section on this GITHUB archive says "Head over to http://cncpro.co".

When I tried to go there as of the date of this posting (9/25/17) the site says

"Looking for LaserWeb? no longer here... CNCpro.co is retired"

FYI<

Makeit working with NEJE laser diodes (blue 20W)

NEJE Master 2 products, after being re-flashed with Grbl 1.1f, are working with Lightburn.
But not possible to make it work with LaserWeb4 latest (for linux): " No supported firmware detected. Closing port /dev/ttyS14". Same for all ports listed and a variety of speeds.
Would be really cool to have it working with Laserweb :-)

Blank screen at startup

after re-installing latest Laserweb.dmg, blank screen at startup, deleted all files and folders on iMac and re-install again without any succes.

中文视频教程，vedio tutorial in chinese language

this is my vedio show the step of the software
vedio tutorial for chinese。

【开源激光雕刻软件（含矢量）操作简介——LaserWeb4-哔哩哔哩】
https://b23.tv/QNMz3WX

Weird release numbers

Release numbers don't seem to coincide with the .exe you download? Also for the last several release the version of the downloaded .exe has stayed the same?

build.osx.sh fails on Ubuntu with webpack --progress --colors


npm ERR! Linux 5.0.0-29-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "bundle-dev"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] bundle-dev: `webpack --progress --colors`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] bundle-dev script 'webpack --progress --colors'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the laserweb package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack --progress --colors
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs laserweb
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls laserweb
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntourist/gits/Laserweb4/npm-debug.log

npm-debug.log

Apple Silicon compatibility

Mac computers do not run on Intel chips anymore, but Apple Silicon CPUs. For two years.
It's time to upgrade your code so LaserWeb can run smoothly on M1 (and now M2) Macs!
Running through emulation thanks to Rosetta 2 is only to let developers some time to port their app as a Universal binary.

Windows Install

Installing 64 bit version (also same with x86), get blank screen!
System configuration:
Windows 10 64bit V 1709 Build 16299.19
CPU Intel i7-4770K 3.5GHz
Graphics NVIDIA GeForce GTX 760 (1920 X 1080)

LaserWeb ARM 64

Hey guys, is there any way I can get LaserWeb running on the latest Raspberry Pi (3B+)?

LaserWeb Linux image.app

I saw that my previous issue was closed because the problem was stated in the subject line. The link to the linux files was not a valid link. I see that it has been updated. However, the updated link to files has an .exe file and is for PC and Mac users only. I have been using laser web successfully on Ubuntu 16.04 but it has been awhile since I installed it. I am now using Ubuntu 18. I do not believe LaserWeb will work with the .exe or .tar or other source code provided. I may be incorrect about that. If so, can we have a better tutorial on how to install on updated Ubuntu. Thank you.

Linux Appimage does not exist

No links to download the Linux appimage from https://github.com/LaserWeb/LaserWeb4-Binaries/releases

Update backend

@jorgerobles Hi Jorge

Would it be possible that you update the backend (lw.comm-server) and compile new binaries to include all the backend updates since juli 2018?

I have invested a lot of time to add new features and support new firmwares (like RepRapFirmware) and it would be nice if it finally gets to the binaries. Thanks!

Best wishes, Claudio

32-bit linux

The laserweb-builder-v4.0.993-130-x86_64.AppImage dosen't work on 32-bit Linux.
It looks like it is only made for 64-bit.

Windows 10 - error: Listening EACCES 0.0.0.0:8000

Hello,
I´v installed LaserWeb4 app on a few devices without issue, but I am struggling to make it work on my PC. I am getting error message: "error: Listening EACCES 0.0.0.0:8000", it looks like ports are in collision. I´v checked this and I found that port 8000 is already in use, but unfortunately it´s System and I´am not able to kill it. Is there a way, how to change port number for this app manually?

Thank You

Petr

README.md 404 Linux AppImage not found

Linux Users: Download from http://laserweb-release.s3-website-us-east-1.amazonaws.com/

leads to:

404 Not Found

    Code: NoSuchBucket
    Message: The specified bucket does not exist
    BucketName: laserweb-release
    RequestId: DE30B800DABAF1D6
    HostId: PYloZH2ZnzLbxfsXWylyrY21obqwsuTVOMQ2u5tEyqK8B0M4wp9Ig/gKUp+td9O8CljiTHpEdP8=

Machine Settings Left x offest not working

Laserweb version 996-130 and before.
in settings/machine/machine left x
this works for -1 but anything smaller (-2/-2.25/-3/etc) does not make any difference.
I am running as a GRBL machine.
Doug

Abandoned project ?

Its over 2 years now since any activity here, has this been abandoned?

changing grid size settings breaks program, no way to reset settings

Im adding a separate ticket for this though in the white window startup ticket someone had had this same happen but the topic is different.

So basically went to adjust the grid settings, the grid size number boxes were near 0 size and could not see what the number was so tried to type in new one and broke it and now the program wont start and there does not seem to be a way to reset settings. Uninstall and reinstall does nothing so local settings must be somewhere.

Generate Linux distribution on this repository

@sdesalas Can you help us to make a multi .travis for run multiple build targets adding linux also?

appimage gives error re js-yaml

Dowloaded laserweb-builder-v4.0.996-130-x86_64.AppImage, the latest available version with an AppImage.
Made executable and ran it, got error message:

Checking for update
Error: Error: Cannot find module 'js-yaml'

Detailed error message attached.
issue.txt

AppImage missing for recent builds

The AppImage is missing for recent builds.

Reference:
AppImage/appimage.github.io#117

need wainlux k6 driver

just got a wainlux k6 engraver
unable to connect
can someone make a driver for it and this LaserWeb software?

thanks

lw.comm-server does not start after grid set to 0

I messed around with the grid settings and by mistake I set the grid size to 0. The application froze immediately and I had to kill it.
Since then, i can not start the LaserWeb anymore.
I am using Windows 10 x64 Pro.
I tried to uninstall and reinstall, cleared the installation path, cleaned registry entries, even tried an older version of LW, nothing helped. The application starts up, a short flickering with a black rectangle is shown and then the window remains white and nothing happens.
Maybe someone can give me a hint what else I could do, but i suppose this is (still) a bug.

v4.0.994-130 windows release shows up as v4.0.993-130 after update???

I was running v4.0.993-130 and I got notification there was a new release. I downloaded the new release .exe file and ran it. I got the expected windows 10 warning so I continued on and proceeded with the download of v4.0.994-130. The downloaded completed and automatically launched Laserweb however at the top left it still says Laserweb 4.0.993 ? I am not sure if you have simply forgotten to change the version number within the program or if you renamed the wrong installer.

Can you verify or am I doing something wrong during install?

I could not find any release notes to see what has changed.

Unable to open files

When clicking the button to add a file, nothing happens (no file dialog opens) - latest version - Windows 10

A javascript error occurred in the main process

dear sirs,
i have downloaded the newest version on a clean win 10 machine,
installed java
installed chrome
but somehow i get this error:
A javascript error occurred in main process details see attachment
followed by a 404 message in the main screen.
what could be the problem?

Finishing Appveyor / Travis autocompilation

HELP NEEDED

Have no time right now to finish the autocompilation through AppVeyor/Travis of releases, nor manually compilate every change of LW.

I think the only thing it lacks is the proper api keys to distribute the releases.

Not working with Ubuntu 32bit

Seems the binaries for Linux work only in 64bit systems.
I tryed to download the source code and i successfully build everything but i have no idea on how to create the executable for my Ubuntu version. Is this documented somewhere?

Thank you!!!

Relaunch LaserWeb

Hi All,

Just wanted to see if there was any interest in taking up the project and continuing the development. I am willing to take this on if there are others also willing to jump on and dedicate a bit of time.

Please contact me so we can chat.

Laser power weak running job, but tests fine.

So when I add a test job line cut at %100 power, it doesn't burn and the laser just even looks dim.
But in the same workspace, if I set laser test to %100, 100ms, it burns a dot instantly and looks very bright.

This only started happening. On my first test at line cut a circle %100, 800m/m cut rate, it burned fine.

Falcon2 connection errors

I am trying to control the Falcon2 (40w) on a MacBook Pro 2020 with LaserWeb, but the connection keeps dropping out during lasering and the laser just stops (the queued display gets higher and higher values...)

Install failure

I'm trying to follow these directions:

https://laserweb.yurl.ch/documentation/installation/36-install-raspberry-pi

But I get a lot of errors and warnings. Any fixes for these?

dilbert /home/gem/src/lw.comm-server #  npm install serialport --unsafe-perm --build-from-source
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm notice 
npm notice New minor version of npm available! 10.1.0 -> 10.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.3.0
npm notice Run npm install -g [email protected] to update!
npm notice 
npm ERR! code 1
npm ERR! path /home/gem/src/lw.comm-server/node_modules/@serialport/bindings
npm ERR! command failed
npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
npm ERR! make: Entering directory '/home/gem/src/lw.comm-server/node_modules/@serialport/bindings/build'
npm ERR!   CXX(target) Release/obj.target/bindings/src/serialport.o
npm ERR! make: Leaving directory '/home/gem/src/lw.comm-server/node_modules/@serialport/bindings/build'
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | x64
npm ERR! gyp info find Python using Python version 3.11.7 found at "/usr/lib/python-exec/python3.11/python3"
npm ERR! gyp http GET https://nodejs.org/download/release/v20.9.0/node-v20.9.0-headers.tar.gz
npm ERR! gyp http 200 https://nodejs.org/download/release/v20.9.0/node-v20.9.0-headers.tar.gz
npm ERR! gyp http GET https://nodejs.org/download/release/v20.9.0/SHASUMS256.txt
npm ERR! gyp http 200 https://nodejs.org/download/release/v20.9.0/SHASUMS256.txt
npm ERR! gyp info spawn /usr/lib/python-exec/python3.11/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/usr/lib64/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/gem/src/lw.comm-server/node_modules/@serialport/bindings/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/usr/lib64/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/root/.cache/node-gyp/20.9.0/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/root/.cache/node-gyp/20.9.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib64/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/root/.cache/node-gyp/20.9.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/gem/src/lw.comm-server/node_modules/@serialport/bindings',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn make
npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! In file included from ../../../nan/nan.h:178,
npm ERR!                  from ../src/./serialport.h:13,
npm ERR!                  from ../src/serialport.cpp:1:
npm ERR! ../../../nan/nan_callbacks.h:55:23: error: ‘AccessorSignature’ is not a member of ‘v8’
npm ERR!    55 | typedef v8::Local<v8::AccessorSignature> Sig;
npm ERR!       |                       ^~~~~~~~~~~~~~~~~
npm ERR! ../../../nan/nan_callbacks.h:55:40: error: template argument 1 is invalid
npm ERR!    55 | typedef v8::Local<v8::AccessorSignature> Sig;
npm ERR!       |                                        ^
npm ERR! ../../../nan/nan.h: In function ‘bool Nan::IdleNotification(int)’:
npm ERR! ../../../nan/nan.h:684:63: warning: ‘bool v8::Isolate::IdleNotificationDeadline(double)’ is deprecated: Use MemoryPressureNotification() to influence the GC schedule. [-Wdeprecated-declarations]
npm ERR!   684 |     return v8::Isolate::GetCurrent()->IdleNotificationDeadline(
npm ERR!       |            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
npm ERR!   685 |         idle_time_in_ms * 0.001);
npm ERR!       |         ~~~~~~~~~~~~~~~~~~~~~~~~                               
npm ERR! In file included from /root/.cache/node-gyp/20.9.0/include/node/v8-initialization.h:13,
npm ERR!                  from /root/.cache/node-gyp/20.9.0/include/node/v8.h:34,
npm ERR!                  from /root/.cache/node-gyp/20.9.0/include/node/node.h:73,
npm ERR!                  from ../../../nan/nan.h:58:
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/v8-isolate.h:1293:8: note: declared here
npm ERR!  1293 |   bool IdleNotificationDeadline(double deadline_in_seconds);
npm ERR!       |        ^~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, GetterCallback, SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, imp::Sig)’:
npm ERR! ../../../nan/nan.h:2544:19: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&, Nan::imp::Sig&)’
npm ERR!  2544 |   tpl->SetAccessor(
npm ERR!       |   ~~~~~~~~~~~~~~~~^
npm ERR!  2545 |       name
npm ERR!       |       ~~~~         
npm ERR!  2546 |     , getter_
npm ERR!       |     ~~~~~~~~~      
npm ERR!  2547 |     , setter_
npm ERR!       |     ~~~~~~~~~      
npm ERR!  2548 |     , obj
npm ERR!       |     ~~~~~          
npm ERR!  2549 |     , settings
npm ERR!       |     ~~~~~~~~~~     
npm ERR!  2550 |     , attribute
npm ERR!       |     ~~~~~~~~~~~    
npm ERR!  2551 |     , signature);
npm ERR!       |     ~~~~~~~~~~~~   
npm ERR! In file included from /root/.cache/node-gyp/20.9.0/include/node/v8-function.h:15,
npm ERR!                  from /root/.cache/node-gyp/20.9.0/include/node/v8.h:33:
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/v8-template.h:809:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
npm ERR!   809 |   void SetAccessor(
npm ERR!       |        ^~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/v8-template.h:814:22: note:   no known conversion for argument 7 from ‘Nan::imp::Sig’ {aka ‘int’} to ‘v8::SideEffectType’
npm ERR!   814 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
npm ERR!       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/v8-template.h:816:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
npm ERR!   816 |   void SetAccessor(
npm ERR!       |        ^~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/v8-template.h:821:22: note:   no known conversion for argument 7 from ‘Nan::imp::Sig’ {aka ‘int’} to ‘v8::SideEffectType’
npm ERR!   821 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
npm ERR!       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:78:51: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!    78 |   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
npm ERR!       |                                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:135:53: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   135 |   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
npm ERR!       |                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:175:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   175 |   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
npm ERR!       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:215:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   215 |   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
npm ERR!       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:271:50: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   271 |   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
npm ERR!       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:316:50: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   316 |   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
npm ERR!       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:366:58: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   366 |   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
npm ERR!       |                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/serialport.cpp:412:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
npm ERR!   412 |   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
npm ERR!       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp: At global scope:
npm ERR! ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
npm ERR!   433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
npm ERR!       |                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp:433:28: note: remove parentheses
npm ERR!   433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
npm ERR!       |                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR!       |                            -                                                -
npm ERR! ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
npm ERR!   452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
npm ERR!       |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp:452:30: note: remove parentheses
npm ERR!   452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
npm ERR!       |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR!       |                              -                              -
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/node.h:1170:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
npm ERR!  1170 |       (node::addon_register_func) (regfunc),                          \
npm ERR!       |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/20.9.0/include/node/node.h:1204:3: note: in expansion of macro ‘NODE_MODULE_X’
npm ERR!  1204 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
npm ERR!       |   ^~~~~~~~~~~~~
npm ERR! ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
npm ERR!   486 | NODE_MODULE(serialport, init);
npm ERR!       | ^~~~~~~~~~~
npm ERR! make: *** [bindings.target.mk:112: Release/obj.target/bindings/src/serialport.o] Error 1
npm ERR! gyp ERR! build error 
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib64/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
npm ERR! gyp ERR! System Linux 6.7.0-gentoo
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib64/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /home/gem/src/lw.comm-server/node_modules/@serialport/bindings
npm ERR! gyp ERR! node -v v20.9.0
npm ERR! gyp ERR! node-gyp -v v9.4.0
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-01-20T03_19_44_704Z-debug-0.log

v4.0.996-134 DMG release

Where can I find release for MAC?
Thank you

High cpu usage

Hi, when launch, it is taking up high cpu usage approx 30% even when doing nothing.
I'm using a ultrabook, this cause heat and loud fan noise.
Any way to fix?

gcode out of bounds can lead to running work halt

Hi– I'm trying to set up a coreXY machine but can't figure out how to change the gcode origin point. How can I make the machine start at 0,0?

Gcode isn't Marlin friendly

Hello Everyone! I just discovered this app today and tried to get it to work with my MPCNC running the Marlin Firmware.

Both of these issues are related to Settings > GCode

Issue #1 the On Off button for "Intensity Separate Line" doesn't seem to do anything.

Issue #2 the "Tool On" and "Intensity settings" don't generate usable gcode for Marlin. Examples below

Some details on my settings. please let me know if I missed something.
I have GCODE Generator set to "Marlin"
GCode End set to M107 ;This is what will turn off my laser.
Tool Off is also set to M107.
Then before I generate the Gcode I have tried "Verbose Gcode" on and off.

Ok I need the program to generate Gcode that will look like this.
G0 X### Y### F###; Travel to the starting X and Y at the travel feedrate.
M106 S###; Turn the laser on at the desired intensity level
G1 X###; Move some distance while burning
M107; Turn off the laser before the next move. Or this could be M106 S0. Either option would work.

When I try setting Tool ON to "M106" I get gcode like this...
G1 F###; Feedrate is on its own line. I'll have to double check but I don't think this works in marlin without it getting added to an actual X or Y move.
G0 X### Y###; Travel to the starting X and Y
M106; Turn the laser on at FULL POWER NOT the desired intensity level
G1 X###; Move some distance while burning
M106 S###; Adjust the laser to the desired intensity level; This happens AFTER the burn move aka too late.

So I tried to leave the Tool On setting blank and changed the Laser Intensity setting to "M106 S"
That resulted in Gcode that looked like this...

G1 F###; Again not sure if this works to set the speed

; stripped: S0.0000; Looks like it is trying to set the laser to 0 for a Travel move but it Should have looked like this "M106 S0.0"
G0 X### Y##; Travel move
; stripped: S###; Should have looked like "M106 S###"
G0 X### Y###; Burn move
; stripped: S0.0000; Should have looked like this "M106 S0.0"

So I can't get this thing to produce marlin flavored Gcode. On top of that I tried all of these same combinations with the "Intensity Seperate Line" on and off and I never saw a difference in the Gcode it produced.

Please not that Marlin could use M106 S### to turn on a laser or M03 O####. It just depends on how it is configured. Then it would also use M107 or M05 to turn the laser off. But that detail really doesn't matter here.

laserweb / laserweb4-binaries Goto Github PK

laserweb4-binaries's Introduction

DEPRECATED!

laserweb4-binaries's People

Contributors

Stargazers

Watchers

Forkers

laserweb4-binaries's Issues

Recommend Projects

Recommend Topics

Recommend Org