Advanced Search

Had a bit of time to go through the forum and noticed we did not give any usable info here, shame on us!
Use clonezilla, it is free and works perfectly for saving full images of anything from HDD/SSD/NVME.
So:
-install Linux Mint, any flavour
-use KIAUH to install Klipper and MainSail and everything you need
-set your printer properly and make sure everything is working
-use CloneZilla to save an image of that drive
-
This requires a USB stick with CloneZilla, and another drive to save images to, preferably not FAT/FAT32 formated as FAT32 can only store up to 2GB file size. I use EXT4.

OK that indicates either a problem with the 7I33, the connecting cable, the FPGA card
or the firmware.

Note that this test will only work if the 7I33 is jumpered for TTL encoder mode.

PCW wrote:

2. Leaving the TTL option enabled, can you check that grounding the INDEX+ input (encoder disconnected)
changes the state of the hal index pin (hm2_7i80.0.encoder.00.input-index for X)

 

This was just a copy of your questions- sorry, the "2" is missing in my copy and below I wrote the answer to the question you asked.

Andy;

Some time ago I was poking around my LCNC install and ran across a python file that had default key mappings. Within that file I found the "I/i" key mappings which seem to toggle the current jog rate based on the list established in the ini file. I tried to invoke these key in the AXIS interface, but no change was noticed in the jog speed.

I also noticed that there were keys that were mapped to the functions set_feedrate() and set_rapidrate(). What I would like to do is map the '<' key to a very slow rate, say 1mm, and the '>' key to a very rapid rate, say 100mm. To do this I suspect that I would need a function like set_jograte(). I did notice in the documentation, I believe it is the QtVCP section that there was a set_jograte() function, but it appears to specific to QtVCP. Just hoping there is an equivalent function for GladeVCP.

Regards,

With these two keys, I can use my wireless mini keyboard to jog the laser to the program origin of any job quickly rather than from the normal keyboard which makes it hard to watch the laser and jog simultaneously. 

I think there are square brackets required
#<value> = [30 * #<factor>]


setting to read values from ini file

[RS274NGC]
INI_VARS = 1 

There is a difference versus the doc linuxcnc.org/docs/html/gcode/o-code.html#ocode:subroutines
Use o100-style instead of o<mytest2>?
o100 sub
     g-code
o100 endsub

INDEX+ input (encoder disconnected)
changes the state of the hal index pin (hm2_7i80.0.encoder.00.input-index for X)

No it does not change in HAL-Show, it stays high (yellow) even if I short ENCX0 with GND (PIN on the 7i33)

Not sure what you mean here, to me you seem to be saying  hm2_7i80.0.encoder.00.input-index changes
when you ground the INDEX+ pin but then it does not change.


 

All;

I'm running LCNC 2.9.4 upgraded from a 2.9.3 disc image install.

I have this simple test script:

o<mytest2> sub
    #<factor> = 1
    o100 if [#<_metric>]
        #<factor> = 25.4
    o100 endif

    #<value> = 30 * #<factor>

    (LOGOPEN,mytest.txt)
    (LOG, factor: #<factor>)
    (LOG, value:  #<value>)
    (LOGCLOSE)
o<mytest2> endsub

in my nc_files directory. If I comment out the two lines with "value" in then the script runs fine in both sim.axis and sim.axis_mm profiles.  When I uncomment the lines I get this output:

emc/task/emctask.cc 68: interp_error: Bad character '*' used
Bad character '*' used

According to the documentation "*" is the multiplication operator.  Anyone else experiencing this issue? Is there a resolution?

The second issue is closely related. 

I also have this test script:

o<mytest2> sub
    #<factor> = 1
    o100 if [#<_metric>]
        #<factor> = 25.4
    o100 endif

    (LOGOPEN,mytest.txt)
    (LOG, laser-offset-x: #<_ini[LASER]laser-offset-x>)
    (LOG, laser-offset-y: #<_ini[LASER]laser-offset-y>)
    (LOG, park-offset:     #<_ini[PARK]park-offset>)
    (LOG, z-offset:          #<_ini[PROBE]z-offset>)
    (LOGCLOSE)
o<mytest2> endsub

where I try to read ini parameters defined in the axis.ini and axis_mm.ini files as follows:

[LASER]
laser-offset-x = -3.1702
laser-offset-y = 0.0568

[PARK]
park-offset = 0.125

[PROBE]
z-offset = 0.543

When the script is executed the output looks like this:

LOGOPEN(mytest.txt) -> 0x55cc4c8cee20
LOG( laser-offset-x: ######)
LOG( laser-offset-y: ######)
LOG( park-offset:     ######)
LOG( z-offset:          ######)
LOGCLOSE()

Again, is anyone else experiencing this issue in 2.9.4? Is there a resolution?

Kind regards

INDEX+ input (encoder disconnected)
changes the state of the hal index pin (hm2_7i80.0.encoder.00.input-index for X)

No it does not change in HAL-Show, it stays high (yellow) even if I short ENCX0 with GND (PIN on the 7i33)

And Sorry, I mixed it up- the jumpers W1-W4 are set to UP position so TTL/RS-422  sorry!
 

1. if the encoders have differential outputs, why in the 7I33 jumpered for single-ended (TTL) inputs
Answer: because I was told so   - I am really not ecperienced in these things and asked how to get the motors working and showed the schematics to experienced guys- and I was told how to wire the encoders and how to jumper the 7i33.2. Leaving the TTL option enabled, can you check that grounding the INDEX+ input (encoder disconnected)
changes the state of the hal index pin (hm2_7i80.0.encoder.00.input-index for X)

...ok, I will check this with disconnected encoder and report.

Thank you
Sigi

Hi all,Before I head to bed, I wanted to ask if anyone can quickly help me with my current frustration: getting this machine’s carousel working.I’ve got homing working, but there’s something odd—if the carousel is already homed and I try to home it again, nothing happens. I’ve managed to get M13 working, but I still need to sort out M11 and M12. I’ll attach my HAL and INI files here.I’m wondering if there are better ways to handle this, or if there are any good examples I could look at. My machine doesn’t have sensors for the pockets (which I would have preferred), so I’m working around that.Right now my biggest struggle is that I’m getting “unary” errors from my subroutine. When I try to trace the problem, the error messages aren’t very clear about what’s actually wrong. Is there a way to debug subroutines more effectively? At the moment the basic error messages don’t give me enough detail to figure it out.Any tips would be greatly appreciated

If you get probe tripped error during slow proving it's usually a sign that you might need to add the debounce component to your halfile and then recalibrate the probe in Probe Basic.

Yes shure.
I try to run servo in csp, i see one big problem - moror jumping on re-enable.

I try to dual ethercat-stepper, lol ok all enabled first motor running good - when i try to rotate shaft motor not showing feedback. second axis showing normal. first axis good run - second axis max spedd 500rpm if more motor jumping.

nvm, i found myself solution in axis/pyvcp example

Does GTK_Vismach exist, or has anyone attempted to embed Qt_Vismach into a GTK window?