Advanced Search

For someone that has several machines with touchscreens, maybe i was a bit quick on the draw, but i always have keyboards on them so i never though about it.
Valid reason, thank you for pointing it out.

This is where i started back then, although i can not find a recent version of it not the exact one i used, but i had this printed and on my desk at all times for months
linuxcnc.org/docs/2.6/pdf/LinuxCNC_Integrator_Manual.pdf
The exact procedure was, i downloaded the 6.04 or 8.04 ISO, installed it, used the stepconf wizard, powered on the machine and it happily engraved EMC2 (that was LinuxCNC back then) on the table, albeit mirrored, so a bit of reading and found out i can edit the hal file and just add minus sign to scale to reverse the offending motor, opened the hal file and had a quick glance for about 10 seconds where my brain went boom thinking this is just like wiring stuff with wires!
Love at first edit.

Does your encoder have index?

I use it quite often, for example drilling a number of holes, I can just enter the list of G83 positions in MDI.

Editing a file with a touchscreen and no keyboard isn't something I want to do, but entering a bunch of MDI commands in the Touchy MDI interface is easy.

And I am far from convinced that there is any applicable standard that prohibits MDI queueing.

I do not think so, nor do i aim to do that.
This post was explicitly because of you as i vividly recall back when you did a post with only "10000" in it and i asked you what was that, and all this was triggered by a friend a few days back when he was browsing through the forum and told me i have nearly 20000 posts.
Maybe if i did not delete so many of my replies to keep topics clean ...
Thank you for the patience with me, i am sure i messed up on more than one occasion.

Thanks! will do.

Looks like you are likely to catch me up some time soon, then.

irwinger wrote:

Not that I would ever 'bite the hand that feeds me', I have to ask if you were coaxing me in to discovery? I mean - how much more effort would it have been to state something like "the line in you HAL 'net spindle-on      => parport.0.pin-09-out' does not initiate the spindle. It defines or assigns a pin to use (pin 9), but it doesn't actually make the pin 'do anything'. What you need is a line that connect the assigned pin to a function like this: 'net spindle-on spindle.0.on => parport.0.pin-09-out'"

Yes that would have been more helpful for sure, in the long run.
I insisted on making a new config as i have seen way to many wander of in the depths oh hal and getting utterly lost and dazed and confused, subsequently giving up on LinuxCNC altogether, so my main aim for new users is to make the machine work first and foremost, then we can chat about options and bells and whistles.
I am glad you are one of the more analytical types and jump head first into problems, will try to keep in mind that next time i reply.
And, no, i am not deleting this, nor do i want you to delete it, it is a valid and respectful response.

tommylight wrote:

Rod, drives should be mounted vertically, as noted in their manuals.

Yeh, that is due to a bigger stuff up. The enclosure is 400 x 400. I removed the backing plate and I carefully marked out all mounting bolts and inserted nutserts everywhere to mount everything. Then mounted everything only to find the backing plate was not square like the enclosure! So the plate is rotated 90 degrees from where I planned.
400 x 400 is really too small but it was what I could get at the time due to COVID. Made for a really messy install because of no room for slotted conduit

linuxcnc.org/docs/html/hal/intro.html

Is a good starting point

OK - I now have spindle control...

@tommylight - your post(s) about 'no spindle' configurations and suggestion to make a new config finally helped my 'through the forest'.

Not that I would ever 'bite the hand that feeds me', I have to ask if you were coaxing me in to discovery? I mean - how much more effort would it have been to state something like "the line in you HAL 'net spindle-on      => parport.0.pin-09-out' does not initiate the spindle. It defines or assigns a pin to use (pin 9), but it doesn't actually make the pin 'do anything'. What you need is a line that connect the assigned pin to a function like this: 'net spindle-on spindle.0.on => parport.0.pin-09-out'"

First - I am just 'making this up' because I really do not understand the structure and syntax of the lines in the HAL file (something that I really think would have helped me in my discovery). Please feel free to delete this post or tell me to do so because I certainly do NOT want to confuse anyone else.

If this kind of documentation already exists somewhere - I certainly did not find it, but if you point me to it, I will be certain to explore. Meanwhile - thank you both again for your assistance and direction to resolving my issue!

Regards,
Arden

Also could you explain how your physical setup for homing of the C axis / spindle? It is something I am having trouble with after modifying your HAL and INI (which I will attach here).

here is a picture of my physical manual, its slightly different than the online manual. However, do you think it actually does work and this physical copy of the manual is wrong?Also just to clarify - are you also saying that because my current encoder is not 1:1, that it will not work?I can go ahead and try to solder on the wires to my servo driver and test it out 


Currently using a 1024 p/r pulley mounted encoder

I wrote that because of your argument that referencing MDI_COMMANDS explicitly would make the ini file "more standards compliant".

Ideally every GUI should provide it's own hal pins to handle the functionality of 'halui' (which is actually a separate user interface).

Domi wrote:

yes?how?
 

pyocd reset --target mimxrt1050_quadspi
pyocd erase --chip --target mimxrt1050_quadspi
pyocd reset --target mimxrt1050_quadspi
pyocd flash remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi
pyocd reset --target mimxrt1050_quadspi