Advanced Search

Hey Guys,

If you have a moment. This video as well as the code is super rough, but I wanted to raise a bit of attention for those that are interested:
I have a modified Ender3 3d printer with two rotational axes. It is controlled by a raspberry pi and an cotopus board 1.1 with remora linuxcnc.

github.com/bbo-git/5AxisSlicerBlenderAddon # indexed slicer with cura engine backend
github.com/bbo-git/5AxisKinSlicerBlenderAddon # spiral toolpath creator and Gcode generation



with kind regards,
Jairo

Hi all. I am trying to figure out the last step of configuring my machine. For background, I am using a Raspberry Pi 4b with the current LinuxCNC image from the downloads section. The RPi is connected to a Byte2Bot parallel hat which is in turn connected to a parallel port breakout board. I have managed to figure out all of the step, direction, and limit switch stuff and now have a machine that moves, homes, etc.

The final thing I want to do is define an input to LinuxCNC to stop motion if one of my closed loop stepper motors throws a fault. Essentially like hitting the E-stop. The stepper drivers each have a fault output pin and all of these fault outputs from the drives are wired to parallel port pin 10 of the BOB. This should be GPIO 25 (GPIO connector pin 22). For everything else I have done I have used templates and just been able to change pin numbers. I believe the hal entries would look something like this:

net driver-fault <= hal_gpio.GPIO25-in
net driver-fault => iocontrol.0.emc-enable-in

I believe this would result in a stepper driver fault essentially tripping the emergency stop.  I don't have a way to test this right at the moment and was wondering if someone could take a look and see if my thinking is correct?

Thanks,

John B 

If you are using the byte to bot supplied files they won't work .
The images you supplied aren't really readable.
What I would suggest is read the docs for the hal_gpio driver and modify your files to suit.
Then loudly complain to byte2bot their files are useless for the raspberry pi .
Also when asking for help attaching your hal & ini files is most helpful.
Also attaching the error files rather than photos of the screen helps as well.

No, it has nothing to do with the kernel module, disabling the kernel module won't stop the service running. The messages are coming from the service systemd is attempting to start.
One option is to mask the service and have no swap available.
The second option is as I've described and have a little swap if needed.
But it's not the kernel modules that are issue.
Not to be unkind but I didn't pull the solution out of my backside, I spent some time researching the issue, as to what was causing the issue, how to fix the issue and what was supposed to be happening.
The service is for setting up swap in compressed ram. Whilst there is a little overhead in compressing and decompressing the speed for accessing ram is far far quicker than accessing a drive of any sort. If no swapping occurs it will have no affect on latency.
And even before I offered up my solution I ran a few tests to make sure I had the method correct and there were no issues with latency or anything else.
And yes I should have been more vigilant when initially putting everything together.

PLEASE NOTE
all references to zram.service should be zramswap.service

That would work if network manager was the method used to manage the interfaces and network-manager-gnome was installed. But that's not the way the images are built.
And honestly if you don't setup a firewall as well.....

Question should be
How to set a hotspot on Linux?
Any Linux distro that uses network manager = easy, it goe something like:
-right click on the network icon located up or down on the right side close to the clock
-choose "edit connections"
-double click on the wifi connection
-go to "Wi-Fi" tab
-select "hotspot" from the drop down menu and add info as neede like BSSID etc
-click save
-close
left click on network manager and select the wifi network to reconnect
done.

zram is a kernel option which can be disabled by adding zram.enabled=0 to boot.txt
Do you guys want to try that?
The Debian tools are not really necessary. The kernel docs explain how to configure it manually.
www.kernel.org/doc/html/latest/admin-guide/blockdev/zram.html

No and if you want to you're on your own. Totally beyond the scope of this forum.
And not a good idea for too many reasons.

Hello did anyone tried to set up a hotspot on raspberry pi to connect remotely?