Tell me 100% truthful I am running an Arduino Uno board that was sent to me by sienci.
I just recently sold my 30-30 and I’m waiting for my 3048 to ship
But that said, I have been running that Arduino board as my controller in my 30-30 and on the workbench so I know it’s a valid scenario
Thanks for all the effort. Yes, you’re running a 32bit version of debain, buster. I’m playing around with the 64bit bullseye.
The other thing that I discovered is that the RPi 400 has an ARM8 chip or aarch64. I downloaded that version and am currently trying to get it to run, but can’t figure out which icon to use for launching the app. Strange that there is no instruction for this.
I will say back in the beta there used to be an installer and all kinds of fancy stuff
The last time I ran it, you basically just run the the application you download. I’ll take a picture of the icon I created to launch it but it’s nothing complicated
I do remember somebody from the Dev team saying that it has to be the 32-bit version of Linux. I reported some bizarre problem and I can’t remember it was a month ago
If I remember correctly there are instructions someplace. Basically you have to download it, change it to executable and it works
HI I am in the planning phase of my build. Waiting on the funding to be approved ;-). I am looking to start off with a table on wheels like many have done but to eventually build a wall mount hoist that will allow me to wheel it over and have it hoisted up and out of the way when not in use.
I am wondering if it is reasonable to think about using a raspberry pi as the attached computer and using a 10" touchscreen as the primary interface with GSender. This would be wi-fi connected and would have access to network storage locations where the files would be stored. Could most of the gsender functions be done with a touch screen or would i need to plan for a keyboard and mouse as well?
I’m using a Raspberry Pi to control my CNC (it’s a Shapeoko with a JTech laser). Several people have recommended gSender to me. I know there’s an issue with handling small screens, and I have a small touch screen on my Pi. (The screen is 1024 x 600.)
I tried to run gSender from a desktop icon and never saw it, so I ran it with output redirected to a file. Nothing in regular output, but the error output is at the end of this post. Is the screen too small? If so, is there something I can do to get it to work? And if not, what is the issue?
-------------Error output------------------
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
19:51:34.588 › Error: /tmp/.mount_gSendeDUFgp8/resources/app/node_modules/@serialport/bindings/build/Release/bindings.node: wrong ELF class: ELFCLASS64
at process.func [as dlopen] (electron/js2c/asar.js:140:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1196:18)
at Object.func [as .node] (electron/js2c/asar.js:140:31)
at Module.load (internal/modules/cjs/loader.js:981:32)
at Module._load (internal/modules/cjs/loader.js:881:14)
at Function.Module._load (electron/js2c/asar.js:779:28)
at Module.require (internal/modules/cjs/loader.js:1023:19)
at require (internal/modules/cjs/helpers.js:77:18)
at bindings (/tmp/.mount_gSendeDUFgp8/resources/app/node_modules/bindings/bindings.js:112:48)
at Object. (/tmp/.mount_gSendeDUFgp8/resources/app/node_modules/@serialport/bindings/lib/linux.js:2:36)
at Module._compile (internal/modules/cjs/loader.js:1145:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1166:10)
at Module.load (internal/modules/cjs/loader.js:981:32)
at Module._load (internal/modules/cjs/loader.js:881:14)
at Function.Module._load (electron/js2c/asar.js:779:28)
at Module.require (internal/modules/cjs/loader.js:1023:19)
(node:1441) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:1441) UnhandledPromiseRejectionWarning: TypeError: Message must be a string
at messageBox (electron/js2c/browser_init.js:45:3307)
at Object.showMessageBox (electron/js2c/browser_init.js:45:4196)
at _callee4$ (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:359:37)
at tryCatch (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:51:2404)
at Generator._invoke (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:51:1964)
at Generator.throw (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:51:3255)
at asyncGeneratorStep (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:59:103)
at _throw (/tmp/.mount_gSendeDUFgp8/resources/app/main.js:61:291)
(node:1441) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v25.6.0 Documentation). (rejection id: 3)
(node:1441) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403
[1441:0723/195134.695505:FATAL:gpu_data_manager_impl_private.cc(442)] GPU process isn’t usable. Goodbye.
@Tango Welcome to the group, Hal.
I have no knowledge at all about your setup and the issues, but I’m confident that someone on the gSender team at Sienci will be able to help. Stay tuned. 
I just loaded gsender (gSender-1.1.2-armv7l.AppImage) on a Raspberry Pi, 3b. It throws up the splash screen and just sits there.
Looking at it, it looks like it is just throwing the splash screen gif up and it just stays there like I opened and image and not an app.
I did see an entry for a windows user with a similar issue, but nothing on a Pi.
Any suggestions would be appreciated.
I am having the same issues. I have even tried to load the Pi OS 64 bit and it does not work either. I went back to an older version and it does not work. I am getting the same thing with just the splash screen.
I did have an older version working on my Pi, but had not used it for a long time because I didn’t have a display. When I got my new display, I re-imaged the Pi and now it does not work. I will have to see if I still have the version I had working.
1 Like
It looks like it broke when they went to 1.1. I have loaded multiple versions pre 1.1 and they seem to load just fine. I guess since my PC was on 1.06 I should be fine with my Pi on the same version, but I am hoping to take advantage of some of the new functionality especially for the laser.
I wasn’t sure if it was best to post here or to go through feedback or some other option. I didn’t want to contact support directly, since I’m just using the software and not buying their CNC. On the other hand, speaking as a part-time programmer, I know a newly installed program should generally run, so I’m sure the developers want to know about an issue like this.
okay everyone I have tried everything i can think of and I still cannot get gSender to work on my Pi4. I have tried with a 32 bit and a 64 bit OS. I have done all updates and upgrades. I have tried older versions of gsender to no avail. What else does anyone have?
Well, there might not be an issue. They’re having a time of it getting gSender features to all work at the same time on a PC let alone all the other variations. 
I really like the program but may have to switch back to UGS for now. Hope they get it worked out. It is a great program. Also would like to know if any one has a macro go-by. I do a lot of repeated cuts in the same starting point and would love to be able to automate some of the things I do.
We’ll take a look at this shortly - it looks like the pi build was released with incorrect serialport bindings (64 bit instead of 32 bit)
Thanks for the report - I’ll follow up when we get a fixed build out.
Kevin
Thank you!
I hope the crash report included enough info to help you!
1 Like
Cool, thanks. Looking forward to having this work on the PI. Even on the older code, I am having issues with it fitting on the screen, and for some reason I can’t change resoution