Advanced Search

For the Linuxcnc Raspberry Pi images just don't do dist-upgrade, it will break things, this has been proven.

You get get away without doing any kind of upgrade.

If you are worried about security, updates are only a small part of the picture. The first step should always be physical security, which should be the number one priority with a computer running a cnc machine.I'd take data loss over damage to a cnc machine any day of the week, you can't back up a cnc machine.

I would still appreciate knowing how to call anyone of these routines without going through the entire program.

You can call any subroutine in a loaded program from MDI (eg 'o100 call')

Also how to set the Z after the tool change.

Do you mean the tool-length offset or the work-offset?

The currently active work offset can be changed like this:
'G10 L20 P0 z123'

What about the "rawcounts"? when i quickly had a look at them in halscope they seemed to have "0" at a fixed location, do you think that's something i could use in some way?

langdons wrote:

Is dist-upgrade ever a good idea?

Yes, when you download an ISO, it might be several months old, so that will update to the latest stuff for that distro, including kernels and stuff that "might break things".

pgf wrote:

p.s. Best tech support ever...

Yes he/it is.

The STEP/DIR output voltage will be the 7I96 5V supply voltage
if there is no load. Any load will lower the output voltage.
So it could be low supply voltage, or a load on the output
The output resistance is around 50 Ohms so a 10 mA load will drop
the output voltage by about 0.5V

ahhh thanks pete!  i just came across that just a few minutes ago. i thought that looked suspect. must be a bug in jt’s config tool because thats straight out of mesaCT. 

quick question, any reason i cant get more than 4.45v out of my pwm?  ive checked everything on the hardware side and its all good there. no matter what i do, i cant get more than 4.45v max from the pwm

Dont merge anything just yet. me and my friend have spent the last 3 days trying to figure out the shit outta this problem. we have environment configured, we can switch uart, but we are very stuck and out of ideas. We are trying to switch SPI channels from 1 to 2 and/or 4, but we just dont know what variable we are missing/not configured. It works mostly but the MOSI doesnt seem to work but the MISO does. SPI1 works fine, but we cant figure out how to switch to 2

github.com/cakeslob/Remora-STM32H7xx-PIO/tree/h723
github.com/cakeslob/Remora-STM32H7xx-PIO/tree/spi4

No outputs are GPIO

7I96 isolated output hal pins are:

hm2_7i96s.0.ssr.00.out-00
hm2_7i96s.0.ssr.00.out-01
hm2_7i96s.0.ssr.00.out-02
hm2_7i96s.0.ssr.00.out-03
hm2_7i96s.0.ssr.00.out-04
hm2_7i96s.0.ssr.00.out-05
 

If you want help, you will have to upload your hal & ini files, otherwise no one knows exactly what you are doing.

Heh. It's as if you actually know a lot about this, and have been doing it a long time.

I changed hm2_7i96.0.dpll.01.timer-us from -50 to -250, and the symptom went away. (First try, I changed all 4 dpll values by -200, but it turned out changing the others wasn't needed. I'm guessing they're not used?)

Thanks! Oh -- also, hm2_7i96.0.packet-error-total stays 0.

paul
p.s. Best tech support ever...

ok so i made it out to the shop and have a rudimentary pwm signal running. but i am sill having some problems with it. it works ok from the mesa to the pwm module, i get 2.5v-4.5v when i run the spindle. my min speed is 12k and my max is 24k, so those numbers make sense, although is there a way to get closer to 5v out for max speed?

on my module, i get a constant 8.5v out which i think might be a bad module so i have one on the he way, supposed to be here to tomorrow. 

but i still cant get either the spindle on, flood, or mist pins to work.  in hal meter, it shows the pins toggling, but physically nothing happens. out of curiosity the three of them map to gpio.00.out etc, which gpio.[00-09].in are all of my inputs. is this right on a mesa? when i changed all of them to 10-12, i get error saying pin not found. 

Hi Andy... I am muddling my way through this and have things working really well, except inputs. Gpio reads gpio13 fine in python, hal_gpio always shows high in hal scope, meter etc. Any ideas? Is there a way to set gpio characteristics with hal?

I would first try setting the DPLL read time earlier, say -200 usec

If the host has a lot of latency issues, the servo thread invocation
time can be delayed quite a bit from its nominal time and this can
cause enough baseline wander in the DPLL tracking to read before
the the DPLL trigger latch time when the delay goes away.

Also make sure that:

hm2_7i96.0.packet-error-total

is 0 (If not, the network latency is so bad that packets are being dropped)

 

And one more data point: running up to 5 glxgears while the motors are moving doesn't cause the problem. But if I drag those windows around? Lots of bad noises from the motors. I've run that many glxgears, and dragged them around, many times when doing the latency test. There's never been an effect. But there is on the actual motors.