Advanced Search

Hey guys! Me again...

after the last thread I made I've been using Probe basic and been loving it, even made a few parts and had no issues. until today I figured I would actually set up my tool setter and touch probe since that is the whole reason I switched to probe basic in the first place. but have ran into a strange issue that my google-fu has not been able to bring anything up on. 

I'm just trying to probe the spindle nose on the tool setter, but when I send the command to perform the probe the Z axis doesn't move. The DRO starts counting off as if it is moving but nothing on the machine is actually moving and pressing the tool setter manually with my thumb for example also does nothing and then after a few seconds the machine says that it never triggered the probe (Obviously)

Just wondering if anyone has experienced this behaviour before? and where I should try to look and what I should be looking for? I'm getting ZERO error messages it just doesn't work :\ If I have set up the probe wrong thats fine I can trouble shoot that later but it seems odd that the machine never even moves to find the probe but the DRO thinks the machine IS moving...

Thank again for your wisdom guys. 

 

Hello everyone,

after a long break, I have now returned to the problem.
Specifically, I bought a Lenovo ThinkCentre M91p i5 2400 with 8GB RAM and 128GB Intenso SSD. Very reasonably priced at under 30€ including shipping.

I would recommend this to anyone who has a PC with poor performance. The old PC cost me a lot of nerves and also took away some of my enthusiasm for the project.

This gives me much better values in the latency test. The values were already significantly better without any optimizations!
 

I have now also bought a Mesa 7i96s to control it. It hurts once, but with it I can build a clean cabling right from the start without soldering cables etc.

The next steps are now to set up the controller on the desk. There are bound to be a lot of new questions about this.


Erwin

any we can exchange the mail
Keep it just here, so others can benefit.

these for sure ... no worry ... ask not for these scope.

JackRay wrote:

hello everyone,I have just received my 7i96s board, the 5 axes work correctly with my RPI 4 . but I would like to work with an XYZBC trt configuration . The construction is easy with the configurations already proposed in stepconf . but I have no idea how to convert /establish the same configuration with Pncconf which is MESA oriented but without predefined configuration. Could someone please help me?Thank you
 

Please start a new topic for configuration troubleshooting and assistance.

I'd prefer to keep this thread as specific as possible.

Quote

The plasma cutter I am using is older and does not have any of those (external connectors). 

As Tom has indicated you need to open your plasma cutter and wire a voltage divider inside the cutter. I have attached diagram with an example for cutter with 250V, yours might be different you may need to determine the proper resistors values. (Please use high voltage resistors in kilo-volts range).
For Arc OK signal we need to know the make of your cutter or even better a wiring diagram to determine the wiring points if they exist.
 

The LinuxCNC parts (kins etc) of the configuration files of a Mesa or parallel
port setup would be basically identical. The per joint low level stepgen setup is
different but that the main change.
 

Alright, now took my last attempt of building another kernel, if this one still doesn't work it should be something else. The kernel is in the Test folder.
drive.google.com/drive/folders/1r76sUsfG...6fGcz?usp=drive_link

The realtime component is on core 7 by the way, in htop you should select the one with -99 priority before you press "a'. The gui isn't realtime so no need to put that one on a isolated core. But without isolating cores the results are still good enough indeed, so if that experience is better it might be the better choice. 
Just tested without isolating a core and the latency on the servo thread went up to 40us, while when I only isolate core 7 until 3.3us. The kernel in the Test folder is with cpu governors, so I put these via armbian-config at performance and lowest frequency at the highest.
With only core 7 isolated it has no frame drops at 1440p@30fps, unfortunately there is no full (ffmpeg) hw acceleration in chrome anymore, where the cpu usage stayed below 10% @4k.
 

One obvious change is that the Z axis feedback must come from the encoder velocity
(= scaled THCAD2 frequency)

net z-pos-fb hm2_7i96s.0.encoder.velocty
 

Edit menu, preferences, see screenshot and choose what you want as default.

Then on the last tab, set the number of threads to use for rendering, i do 5 as i have a 6 core AMD and leave one free for other tasks when using the PC, you can do max number of cores (not processor threads).

Also, use OBS-Studio for screen capturing, it is much better and uses less resources, although your original video is quite OK on a 34" monitor.

I tried the bootloader you gave me and it doesn't work.

The 5 and 7 cores are isolated and linucnc works with highest priority on 0,1,2,3,4,6 cores (Htop shows this).
So nobody uses 5, 7 cores. Why isolate them if you don't put linuxcnc on them?
I noticed that my linuxcnc works better with all cores enabled. I actually watch StarTrek when the cnc is running.

I'm using Simple Screen Recorder to make my tutorials and the resulting video is good quality but when I edit it in Flowblade the video is not good quality after uploading to youtube.

This one is straight from Simple Screen Recorder and uploaded to youtube.


After processing in Flowblade and uploading to youtube the quality is 480 max.


Any ideas on how to get better quality videos to youtube?

JT
 

i only have the both octopus, and a few nucleo working, only stm32f4 stuff at the moment

No idea!
I have:
ESP8266
ESP32 wroom
Octopus <inside a Voron 2.4 so not comming out
Several St32xxx on other Vorons all yanked out of Creality printers
Trying to order SKR1.4 to play with.
What boards are being developed here for this? I have seen several, but can not recall where and for exactly what.

alright tommy! 

what board do you want it for? looks like i didnt make .bin files for anything yet

      100% solved. Grounded every component to a ground distribution block. Used tinned copper braided wire and grounded the grounding block to the chassis and the spindle to the gantry. Then added a simple debounce to my probes and limit homes. It's all good to go. Right back to .0005" tolerances. Thanks for the support