Advanced Search

I have a .nc file with a starting point set in CAM. I load the .nc file into linuxCNC and see a blue X at my starting point, as expected. I Home All, then jog to where I want that starting point to be on the physical part, and this is where I get confused. When I touch off X and Y to zero, expecting that the cutter (on the Preview tab) to move to the starting point specified by CAM, it instead moves to the origin on the red/green axes and shows a second* blue X.

First, I don't understand why setting the X and Y touch offs to zero doesn't result in the cutter moving to my specified starting point.
Second, I don't understand where that coordinate system came from. It has to be from my CAD or CAM but I never specified any axes to be there. Not sure why the red/green axis is playing a part in this.

FWIW, I'm using Alibre for CAD and VCarve to generate the .nc file, along with my own post processor.

*It bugs me that the two blue X's appear exactly the same, as it makes determining what the represent far less obvious.

I've finally gotten a little time to work on this again!

I'm still planning to use the MR-J3-70A drives, which I have already. What is the current state of support for the copper network drives?

I'm sure its something simple that I'm over looking or not understanding I'm a new at this
thanks for the help

When i look at the mesa manual the numbers don’t match for example 30-33 in pnccofig where are those on the board it self 

That would be the 7I96S manual that lists the terminal block pins for
step/dir, analog out. encoder  and SSR channels.

These are also listed by mesaflash's  readhmid command
 

I think what I'm trying to translate pncofig to the physical location on the mesa board

Mon interface est une carte Mesa qui prescrit de ne pas activer le WiFi pour des raisons de temps réel. Alors, j'ai respecté cette consigne sans avoir osé tester si cela était vraiment utile.
Depuis ma demande initiale, j'ai trouvé comment faire en sorte que le module DS1307 s'intègre bien au système en rédigeant un petit service qui se met en route durant le boot.

Pncconf does not have pin numbers, for things like 7I96S PWM outputs
and SSR outputs (the things that are needed for spindle interfaces)
They are listed by channel number (the channel number matches
the 7I96S manual names and mesaflash listings)

Do you have a more complete spindle interface description?

It looks like the 7I96S analog output will need an external 12V or 10V source
(since unlike a normal VFD it looks like the drive does not supply a 10V source)

  the header pins on the mesa boardIt's a project that was stared a couple years ago that I'm trying to finish and now on my own its PM728v-t everything is working except the spindle that I'm trying to figure out how and where to hook up. pncofig has PIN numbers I'm trying to figure out where the number is physically on the board. attached image is what I'm trying to hook up

rodw wrote:

Its not possible to install Debian without an internet connection (hardwired is best) The Linuxcnc installer depends on internet (It uses the Debian Live INstaller).

Debian WILL install and run without internet connection, all the ISO versions except the Net version.
Your version does NOT install and run without it.
Over 2 years of never ending issues...
Remaster the Debian ISO, everything works properly.

Hello everybody!
I am new to this forum, so first I want to thank everybody for all the information posted here.
I want to replace my old 32-bit computer running a 3-axis stepper cnc via a parallel port. 
What I succeeded in:

1. I bought a Raspberry Pi 4 and a Mesa 7i90 card.
2. I used my old computer with parallel port, connected to the 7i90 and programmed the 7i90_spi_svst4_8.bit firmware using mesaflash.
3. I downloaded the LinuxCNC disk image for the RPi 4 and installed it.
4. I connected the 7i90 to the Raspberry Pi (about 3 inch flat-cable, all ground lines connected). I can read the device configuration using mesaflash without problems (well after a new install of mesaflash from the git repository).

Now I want to start ``linuxcnc linuxcnc/configs/by_interface/mesa/hm2-stepper/7i90-rpi-spi.ini``. The GUI pops up and everything seems fine.
But when I press F1 to reset the estop latch nothing happens. Up to now I did not connect any drivers or switches to the 7i90.
I changed 'DEBUG = 0x7fffffff' in the ini-file and added a 'show' to the end of the ini-file. I attach the output when running the linuxcnc. I marked what happend when I pressed F1 by '******' in the text.
If you need more information (ini-file, hal-file) let me know.
Many thanks for any support, H. Hermes

Experienced some jitter as well today while running grandixximo's fork. I doubt there is any synchronization being done while the dc-phased pin is false and all pll-*** pins are 0. Ran sudo dmesg to see what is happening in the background. Maybe someone can notice something clear in the log:

During startup:
[  801.691210] EtherCAT: Requesting master 0...
[  801.691215] EtherCAT: Successfully requested master 0.
[  801.691915] EtherCAT 0: Domain0: Logical address 0x00000000, 74 byte, expected working counter 12.
[  801.691918] EtherCAT 0:   Datagram domain0-0-main: Logical offset 0x00000000, 74 byte, type LRW.
[  801.691932] EtherCAT 0: Master thread exited.
[  801.691933] EtherCAT 0: Starting EtherCAT-OP thread.
[  801.691970] EtherCAT WARNING 0: 1 datagram UNMATCHED!

During operation:
[  807.424674] EtherCAT WARNING 0-1: Slave did not sync after 5000 ms.
[  808.944250] EtherCAT 0: Slave states on main device: OP.

During shutdown:
[  841.183382] EtherCAT 0: Master thread exited.
[  841.183401] EtherCAT 0: Starting EtherCAT-IDLE thread.
[  841.183449] EtherCAT ERROR 0-0: Failed to receive AL state datagram: Datagram initialized.
[  841.183462] EtherCAT 0: Releasing master...
[  841.183464] EtherCAT 0: Released.
[  841.188247] EtherCAT 0: Slave states on main device: SAFEOP, OP + ERROR.
[  841.196539] EtherCAT ERROR 0-0: AL status message 0x001A: "Synchronization error".
[  841.197317] EtherCAT 0-0: Acknowledged state SAFEOP.
[  841.208612] EtherCAT ERROR 0-1: AL status message 0x001A: "Synchronization error".
[  841.209116] EtherCAT 0-1: Acknowledged state SAFEOP.
[  841.220587] EtherCAT ERROR 0-2: AL status message 0x001A: "Synchronization error".
[  841.221590] EtherCAT 0-2: Acknowledged state SAFEOP.
[  841.256274] EtherCAT 0: Slave states on main device: PREOP.
[  841.828318] EtherCAT WARNING: Datagram 0000000031def7fe (master-fsm) was SKIPPED 1 time.

Rod, I literally just did exactly that. It booted and worked perfectly fine, with the caveat that the .sources list for Aptitude is empty, and you need to manually populate it.

Once manually populated, the system was able to be connected to the internet and it worked exactly as you'd expect with regard to installing new packages.

I wanted to bump this thread and inquire if anyone was using the STMBL v5 on their LinuxCNC projects? With native SS support, small size and support for straight rectified 220v I have always felt it was an amazing solution. It is pretty well documented but I'm wondering how challenging it is to tune the drive for the motors once all setup? The instructions seem fairly straightforward but it is hard to know until you try!

Also big thanks to Freak for reviving this project!