Advanced Search

NCAM or Native CAM
forum.linuxcnc.org/nativecam/53492-nativ...inuxcnc-2-9-3#310608

Yes.
Do check if the ralay has one already, some do but mostly do not have it.

freeby.mesanet.com/95tinit.tgz

Not sure about the executables (might be too old a libc version),
but you can get by by just programming the FPGA via JTAG
and running the two mesaflash commands.

Here is the FTDI4232 --> 10 pin header connection:

freeby.mesanet.com/pdf/parallel/4232efin.pdf
 

That way, correct?

 

These are basic with just the X axis.

First thing you want to find out is what kind of signal interface the axes and spindle drives use (ie analog +-10V, step/direction, serial interface) that will then largely dictate the options to go forward.

links are now fixed!

"Should I move this thread over to the Gmoccapy section?"

Yes

I think that's a locale bug on pncconf:

forum.linuxcnc.org/27-driver-boards/5145...ettings-issue#291810

As I wait for my 7I96s to arrive I’m playing with the PcConfing trying to set it up and I keep getting stopped at this point.
im using a Rasberry pi 4
XY lathe
Gmoccapy
7i96s -internal data
Firmware 7i96s_7i74 
When I go to apply the stepper config I get this error.
what am I entering wrong or missing? 

 

Hi all!

I was asked by friend to help him modernize the above mentioned machine.
It is still fully operational but programming it is PITA.
We would like to use something modern and not break the bank.

That's what got me here.

I am IT guy with some basic CNC understanding.
I also have available Advantech PPC-L106 R70-XE industrial panel PC we could use but that might be an overkill.
Laptop on the side would be perfectly acceptable.

I am 100% confident I could install LinuxCNC but configuring it to work safely with that machine might be a steep learning curve.

Any pointers in ht right direction are highly appreciated.

And now excuse me, I have reading to do.
linuxcnc.org/docs/stable/html/getting-st...#sec:config-launcher



Best regards from Croatia!

A SCFFIFO error means too many (>16) transmit frames are queued

Perhaps triggered by a xxxx.mod or hal error

It might also be this bug:

 Current Mesa Modbus issues:

    
    BUGS:
    At startup there can be "call/response function number missmatch"
    error popups or sig11 (segv)s due to the fact that the PKTUART is
    not cleared at startup, so random numbers of garbage characters
    may be present in the RX FIFOs, leftover from the last LinuxCNC run.
    
    A temporary workaround is to run this before launching linuxcnc:
    
    mesaflash --device cardname --addr ipaddr --wpo 0x6800=0x00010000
    
    (writing 0x10000 to 0x6800=pktuartr_mode_reg clears the RX FIFOs)

    If you ever set the update rate to 0 (maximum), changing to a
    non-zero rate will not work (communication stops)
    
    There is a check for TX overflow in the PKTUART code that's
    in the wrong location (TX section) so will print bogus error
    messages with particular outgoing messages.

Yeah, JTAG is the only easy way out if you flashed the fallback area of a  7I95T
with incorrect firmware. (Really,  you should never update the fallback area)

I use a FT4232H USB --> JTAG adapter for programming

The way it's done when manufacturing is to program the FPGA (not the flash)
With the Efinity tool and then use mesaflash to re-write the fallback and user
flash areas.

(This is about 30X faster than writing the flash via JTAG)

I can upload or make available the (linux/bash) initialization scripts/directories
used later today. You may need to edit the paths in the script to match your Efinity
installation.

Doing some more probing on this. It looks to be related to the QtPlasmaC native hole/radius sensing. If I set it to "#<holes> = 0" mode everything seems to behave. I was trying to leverage the native hole sensing to implement overcut. Guess I'll have to work through having Sheetcam handle that logic and workflow.