Advanced Search

hmmmm you didn't accidently have caps lock on when changing the passwd ?

Technically the RPi4 does support both frequencies. There are many articles dealing with this when using an official RPi image.

Since the most recent RPi image is a custom image, most of those articles are not of much use unless of course you are able to extrapolate the information.

You could try a USB to wifi dongle or a usb to ethernet adapter to connect to your local lan if you have available lan ports in the vancity.

Or you could start with a Raspberry Pi OS and install the RT kernel and Linuxcnc, which does work and gives you access to the official RPI tools to setup the system.

The issue I can see is that Rod, the guy who puts the images together, has neither a working RPi4 or Rpi5 and relies on others to point out any issues. Unfortunately it is a bit of a mess ATM, even the download page claims the RPi5 image works with mesa SPI boards but that is not so.

Thanks cornholio.

My first RPI purchase was an 8GB, not used because of reported problems with LCNC (at the time).

Powered the 8GB Pi up near the CNC cubicle without the steppers energised.
Loaded LC 2.9.2, and could not get the WiFi to work.

Took RPi into house not far from router.
It would not connect to router on the 2.4 GHz channel, but would on the 5 GHz channel.

Back in workshop re-configured the WiFi Extender to operate on the 5 GHz channel.
Tested two old laptops, an IPad and a Surface.
Both laptops operate from the extender when configured 2.4 GHz, but neither when configured 5 GHz.

Complete incompatibility !

So, my fear of damage to the RPi WiFi from interference appears unfounded.
And, my current equipment will not route WiFi to the RPi.

John

Ok lets try again. Seems I picked the wrong file then erased it...

same thing as before - rename to qtdragon_hd.ui  etc

The pin names will be
qtdragon.btn-usr-1 etc
qtdragon.led-usr-1 etc

Oh and don't pull in new changes from the repo or the ui file will need to be modified again.

Chris

If you are using the master branch, I have added code for translation ability to QtDrgaon/hd, using the same process as QtPlamac - I basically copied there code/docs

Probably the mesaflash version is to old, so try upgrading it or download the latest version from github.
github.com/LinuxCNC/mesaflash
More importantly, why are trying to flash it?
If you do not need some special function, there is no need to ever flash it.

I just spent the day finding possible solutions in the forum and attempting them. I have reinstalled the linuxcnc os several times to ensure previous attempts to fix the problem didn't interfere with other attempts.

The card is new. Only 5v power is being supplied. The PC is a fresh install of linuxcnc 2.9.2. The PC is only connected to the mesa 7i97t by ethernet. The PC's ipv4 is set manualy to 10.10.10.11
Mesaflash 3.4.9 is being used.

When pinging 10.10.10.10 in the terminal it works. I can even watch the led's on the mesa act like a filling progress bar.
When attempting "mesaflash --device 7i97t --addr 10.10.10.10 --verify FPGAFILE.BIN" the terminal returns "unsupported ethernet device 7I97T at 10.10.10.10 No 7I97T board found"
When attempting "mesaflash --device 7I97T --readhmid" it returns "lbp16_access.send_packet: Network is unreachable Aborted"

I have attempted to use the 192.168.1.121 header on the board with even less luck. It is unable to be pinged.
Preferably I would like to get the card working on the 10.10.10.10 address. 
Do I need to attempt to use the fallback? No red leds are lit.

Any suggestions are appreciated.

I'd probably leave it in custom.hal since that has almost
all the mpg connections

(and perhaps rename custom.hal to mpg.hal or some such)

It makes sense now. [HMOT](CARD0).encoder.02.count was not really connected to axis.N.jog-counts. I think I finally understand the working principle of mux4 and how to adapt it to my setup and wiring. I rechecked the wiring and the output of the MPG on my oscilloscope. The switches also go high (+24V) when selected and the enable button is pressed.

Should I link the final motion function axis.N.jog-counts somewhere in the main HAL file ?

AFAIK the initial search for the home switch is done at HOME_SEARCH_VELOCITY
and any further moves (until index is detected in your case) are done at HOME_LATCH_VEL
and then the final move is done at HOME_FINAL_VEL.

upgraded to 2.9.2. now spindle and probe dont appear at all or classicladder.

The script uses quadrature mode so puts out "step" pulses on both pins

Thats what I thought too, but with Peters script and a rate=0x40000 in that script, the motor is moving correct...

hardware_crash wrote:

When I press the jog button for that axis, I get movement on the stepper motor but just one step regardless of how long i push the jog button. When I release the button the motor makes a step, but it should continuously move ..

That points to having step and dir pins to drive reversed, try rewiring them.

I have a question . When the index pulse is read. Can I set a fast speed for HOME_SEARCH_VEL and low speed for HOME_LATCH_VEL The pulse from the encoder is read at this speed HOME_LATCH_VEL ?

Just the encoder is with lag