Advanced Search

I can take a look at this next week, now that there's a way to re-create the issue.

 

Depends on how you look at it, i did read Aciera's post and went back to read mine as i though i messed up, but it is OK, i am talking about homing direction, he is talking about motion direction.
I'll try to explain, hopefully i do not make a bigger mess:
Look at it as the table is not moving but the head is moving, then translate that to table motion.
Does this make things easier or worse? I would like to know, thank you.

Hi

I'm just trying to clean up the ini file reads for the Manualmatic wrt setting default values & min/max velocities for jogging, overrides & spindle(s) etc.

As an example, since 2.9 some of the spindle options have now moved to asection so variousoptions have been deprecated.

However, there seems to be some ambiguity between the options that relate to hardware (eg min/max velocities) and those that are solely related to display (eg increment or default velocity). There are also at least some  options (egthat have been deprecated with a reference to thesection but the 'new' options do not appear in that section.

Just to add a little more zest, the generated ini files currently create options that do not match the ini file documentation

Is there a roadmap or similar document that can help me understand what options I need to prioritise and should I raise an issue for the missing deprecated options?

 

want to use HSM Advisor to manage my tools it has a xml export, is there a linuxcnc converter or xml plugin ?

Only the stepgen 00 shows this issue, at least from what I have seen:
 

Is there something I can do to further help debugging/troubleshooting? I am no programming god, but I can get my way around some c code if it's of any use. I'm currently on the "stock" iso 2.9.2, if that makes any difference.

I think I have see that before and it looks like a bug in the mesa_modbus driver.
(the 1 Hz is the modbus timeout/retry period) In my testing, it went away mysteriously
and I was not able to re-create it. Looks like maybe request/reply mismatch in some
circumstances.Can you retry the test with the stepgen position not at 0?
(that would provide a bit more information.)

There are a number of already known bugs in mesa_modbus:

 

Here are the hal and ini files. Thanks for the reply!

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.