Advanced Search

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.

The idea was that the user can also define a custom startup message like this:
[DISPLAY]
STARTUP_MESSAGE = My message is ... !

So instead of creating all this code just to alert users to a version change it could actually be used for other things.

Changing the wording of the message is trivial.

Should I move this thread over to the Gmoccapy section?

I may have a board that will convert these encoders to look like standard quadrature encoders. Can you give me specific motor model numbers or encoder model numbers?
Thanks,
Jon

@HansU - what do you think?

I think, it would be better to turn off the message in the SETUP tab in Gmoccapy, rather than in the INI file.
Or just in the Gmoccapy configuration file.
Hans was just tidying up the parameters in the INI file and therefore he wouldn't like it.

I would also add to the text that reactivating "AUTOMATIC G43" is possible using REMAP. An example can be found in any SIM Gmoccapy configuration.

Version for LCNC 2.10 will be Gmoccapy 3.5.0

Maybe something like this:

1. Insert this  at the end of the '__init__(self, argv)' method in 'gmoccapy' (ie after line 516):
2. Insert this a the end of 'lib/python/gmoccapy/getiniinfo.py':
Looks like this:
 

On Synaptic Package Manager, 2.9.0 is the latest version.

Is there another way to upgrade to version 2.10?

Hi Guys, I'm pretty new here and just getting started with LinuxCNC, I've been retro fitting a rf31 mill and have a NVEM V2 I was using with Mach3 on an old laptop. the laptop started to play up and lost all my motor settings so i decided to ditch it all and buy a Raspberry Pi 5, load it with LinuxCNC and set it up solely for this machine.
I recently got my STlink all setup and now I need to confirm which bin file I need to download from GitHub? is it the Remora-NVEM-STM32-1.0.0.bin file in the Remora-NVEM/firmware directory or the Remora-NVEM.bin file in the Remora-NVEM/Remora-NVEM-STM32/Firmware directory? 
I'm going off the Scott 3D Youtube videos, but the GitHub info seems to be a bit out of date. Is any of the info in those videos still up to date or should I be looking elsewhere?
Thanks

hello LinuxCnc Community,

i recently bought a 7i95t with a trion fpga from the company efinix on it, luckily i flashed a 7i95 bitfile to the fallback and now i bricked the firmware so im not able to get a connection to the mesa card over ethernet(CR16 is steady on after powering up the mesa card, which indicates there is something wrong with the fpga config), what makes sense...

After reading the 7i95t datsheet, chapter"Host Interfaces" it says "DO NOT write 7I95 bitfiles to the 7I95T", yeah shit happens...
now i have some questions how to get the 7i95t working again?!

So theres a connector "P2 JTAG" on the 7i95t where you can flash the correct bitfile to the fpga using a hardware interface and the efinity software (there is a free license aviable on their website)
 what kind of interface do i need? do i need a development kit from efinty or can i use other brands jtag interfaces like  410-299 | Digilent JTAG-HS3, Xilinx-Werkzeug | RS

what bitfile i have to flash? 7i95td.bin?
how to flash the bitfile to the fpga with the jtag interface adapter using the efinity software?

i hope theres someone out there, whos so deep into this topic, who can help me
thanks in advance!

best regards Marco

 

Aciera wrote:

I think a pop up window with a warning message on startup in gmoccapy 2.10 might be more helpful as there are going to be a number of users updating from previous versions to 2.10.
 

I adsolutely agree, but I dont know how make it.

I think a pop up window with a warning message on startup in gmoccapy 2.10 might be more helpful as there are going to be a number of users updating from previous versions to 2.10.

I am currently tuning a Linux CNC device to control the Ethercat motor. The motor driver I am using is absolute origin and does not require home. When I accidentally click on [home axis]  on axisUI, causing my coordinate system to be misaligned. For example, if the current point is 10.00 and the motor does not move after clicking [home axis], the current point becomes X0.0 on G53, which may cause collisions during subsequent program runs. How can I disable axisUI's [home axis] function, Either it becomes invalid after clicking, or it disappears.

If anyone knows what to do, please help me. Thank you.