Advanced Search

If someone in the future wants to make the panel color match the gui theme. It just needs to load this file with panel

 

works with the new version of linuxcnc 2.9.3

I am attaching edited python file to run on version linuxcnc v2.9.3  .Now, the color of the panel will automatically align with the color specified in the GUI settings.
in .ini file put
EMBED_TAB_NAME = timer
EMBED_TAB_LOCATION = box_custom_4
EMBED_TAB_COMMAND = gladevcp -x {XID} -u timer_hu.py -H timer_4.hal timer_4.glade



 


 

Im still confused, Mr Aciera is says the first post is correct, Mr Tommy says X and Y are opposite , which is correct or what should I set?

Does the spiethconfig work for anybody?
I tested a lot, but i don't find the problem.
I insert printf commands in the code and get strange outputs. I change from picocom to putty, the same.

The command in short and long version:
spiethconfig -s 19 -i 23 -c 18 -e 0 -t 4
spiethconfig --miso 19 --mosi 23 --sck 18 --csenable 0 --interrupt 4
The output:
Invalid or missing Chip Select pin (0>128)
Command returned non-zero error code: 0x1 (ERROR)

I insert some printf-commands ( bold my changes):
            printf("argc: %d\r\n", argc);     

            if (result.count("s")) { miso_pin = result["s"].as<int>;(); }
            printf("MISO pin: %d \r\n", miso_pin);
            if (miso_pin < 0 || miso_pin > 128 ) { printf_P(PSTR("Invalid or missing MISO pin (0>128)\n")); return EXIT_FAILURE;}
            
            if (result.count("i")) { mosi_pin = result["i"].as<int>;(); }
            printf("MOSI pin: %d \r\n", mosi_pin);
            if (mosi_pin < 0 || mosi_pin > 128 ) { printf_P(PSTR("Invalid or missing MOSI pin (0>128)\n")); return EXIT_FAILURE;}

            if (result.count("c")) { sck_pin = result["c"].as<int>;(); }
            printf("SCK pin: %d \r\n", sck_pin);
            if (sck_pin < 0 || sck_pin > 128 ) { printf_P(PSTR("Invalid or missing SCK pin (0>128)\n")); return EXIT_FAILURE;}

            if (result.count("e")) { cs_pin = result["e"].as<int>;(); }
            printf("CS pin: %d \r\n", cs_pin);
            if (cs_pin < 0 || cs_pin > 128 ) { printf_P(PSTR("Invalid or missing Chip Select pin (0>128)\n")); return EXIT_FAILURE;}

            if (result.count("t")) { int_pin = result["t"].as<int>;(); }
            printf("INT pin: %d \r\n", int_pin);
            if (int_pin < 0 || int_pin > 128 ) { printf_P(PSTR("Invalid or missing Interrupt pin (0>128)\n")); return EXIT_FAILURE;}

and get the result:
argc: 7
MISO pin: 19
MOSI pin: 23
SCK pin: 18
CS pin: 255
Invalid or missing Chip Select pin (0>128)
Command returned non-zero error code: 0x1 (ERROR)

After that i change the sequence of the variables, the problems stay at the forth position. i saw that the out from argc stay at maximum 7 (in my opinion it should be 11).

Does it work for anybody?
If yes, what does is made wrong?

Thanks and best regards
michaeln

Not that I'm aware. But you could of course implement a counter using your own parameter value.

When the table is moving to the left, closer to the lathe the X should increment?
When the machine is moving toward the light blue wall the Y should increment?
When the table is moving down, closer to the floor, the Z should increment?

That is correct.

I'm setting my home positions and to order to:
1st: Z all the way down, nearest to the floor at value 0.0
2nd: X all the way to the left, nearest the lathe at value 0.0
3rd: Y all the way back, nearest to the wall at value 0.0

The home position is up to you. There is nothing wrong the way you have it.

Hi,

it did not, I stared a lot over the milling machine picture and just got more confused, I'm missing some concepts

I reduced the config files from ~700 lines down to the ~10 lines included in the first post, which are needed to reproduce the issue. As such, I can post the full configs if you think it is necessary? But the full configs are currently a work in progress, and I think its more likely to lead us astray than help. Part of the reason I reduced it to the above test case was to make sure I had nothing else in the configs that could be the cause of the issue.

If you get an error compiling the LinuxCNC component, rename the containing folder and remove empty spaces in the name.
You will also get an error when compiling for ESP as there is something with 2 letters in upper case but the other file has it in lower case, forgot what file and where.
Use serial monitor and
github.com/SybexX/ESP32_LinuxCNC_MotionC...in/SerialCommands.md
to check what pins are in use for W5500 as in most config files one pin is 5 while on esp32 it shows as 0, so had to rewire that.

Config files?

Yes, yes and yes.
I might be a bit biased as i have twice retrofitted fully working machines, so i do not care what was, i know what it will be when i get my hands on it = LinuxCNC.
We have 15 ton machines working with it, no idea how heavy was one i saw on youtube but a human was puny standing in it.
It just takes time and effort and you will be left with huge knowledge you gathered on the way.

I also have a 1980s toyoda horizontal machining center complete with pallet changer and tool changer. Would this be another machine that's a good candidate for retrofit is linux cnc able to control the tool changer and pallet changer? Can you account for tool wear in Linux cnc? It's currently on a fanuc 11m control. It's a beast of a machine just little lacking in capabilities compared to modern machines and all coding is done by hand due to lack of memory.

@tommylight
i had the same way and problems.

It is a pity that wez apparently no longer works on this project and finish it. But he made a good job. Thanks to him.
Hal2UDP is plug and play.
But this is not so easy to get it working.
For me first i need a lot of time to see what is future and what is working with this code.

Please have a look to the for from SybexX: github.com/SybexX/ESP32_LinuxCNC_MotionController_RealTime
He fixed the Linux compile errors and added the ESP32_WROOM_DEV board.

What is not working for me, is it the configuration for the spi-ethernet. First i want to change the configuration for the Hal2UDP wiring, but it is not working and seems there is a bug. You have to change the wiring to the default and it should work.

Hello,

I am using the 7i95t_1pktv2d.bin firmware for my Maho MH600T for controlling the spindle VFD. After I got the Modbus communication to the spindle working I started getting following errors, and this is still without using encoder feedback. There are jumps in the stepgen.xx.position-fb while everything is idle. I condensed the setup as much as possible to try to pinpoint the issue, and this is outlined below.

Using 7i95t_1pktv2d.bin firmware:
I use this minimal test.hal which I run with "halcmd -f test.hal":
With this maho_vfd.mod:
I get these jumps in hm2_7i95.0.stepgen.00.position-fb:
 

Currently I don't have the VFD connected, and the jumps occur every second plus some. This occurs more frequently with the VFD connected and communication working. I imagine the jumps occur on every Modbus request. Strangely enough, I don't see the issues if leave the num_stepgens undefined for hm2_eth. And I could do just that and go ahead with my life. But I fear this will come back to bite me if I do.

Any ideas what may be causing this? Some problem with my setup? A bug in the Mesa driver or firmware?

It is a heavy gantry, so adding 10-15KG of other stuff will not change much in mobility, so yes, mount everything on the gantry, including the PC. You do not want to run 15 meters to press ESC when needed!
Also, plasma so a lot of interference, and shorter wires help a lot in mitigating that.
Use existing cabling, usually very high quality and good shielding.
Here are some ideas
forum.linuxcnc.org/show-your-stuff/47357...sma-cutting-machines