Advanced Search

Would need the hal, ini files and to verify the firmware with mesaflash  to trouble-shoot

I have a 7i92t connected to a 7i77. All of the I/O seem to be functioning properly. The analog 0 works properly and the encoder for that axis reads properly. The problem is the remaining joints, and their encoders are not working. Is there a setting that I might be missing to get all of the axis to work? Currently I only have the X axis in linuxcnc working and I can't seem to find the problem with the remaining 5. Any suggestions on what the problem is would be appreciated. I will try to post the hal. and ini. later, but I can't right now.

Rod recommends Balena Etcher.

Victory! (of step 1, now I move on to step 2, building my HAL  )

I am using the Raspi build (forum.linuxcnc.org/9-installing-linuxcnc...erry-pi-4b-5?start=0), but after recompiling mesaflash from git it worked flawlessly!

Thank you so much for guiding me along!

What type of hardware do you have?

 

Where did you get the image from?
Is there a file or a long string of numbers/letters with something like md5sum or sha256 where you downloaded the image?
Did you check if those numbers/letters are the same?

There is no way of knowing without actually testing it.
There are probably hundreds of NUC's versions.

natholego11 wrote:

and here is a link to the probe I have.
 

I don't have a solution, but I have the same probe that I will soon be integrating into LinuxCNC, however mine is NC, not NO. I also have the toolsetter accessory that goes with an identical second probe, which comes with a slightly weaker spring, so you can set the spindle probe length with the toolsetter. There's even a magnet on the bottom.

If it helps, here is an electrical breakdown of the board on the probe. The reverse is just contacts to the pogo pins. The important part - and the point of this reply - is the pinout of the type-c port, so you can make your own cable . I will use shielded microphone cable. The solution could be that simple.

A5-CC1 & B5-CC2, are tied on the probe PCB. The little plug PCB's larger pads are +24v & gnd, and while there are passives on the little plug PCB, I don't know one way or the other if they affect the signal. It seems easy enough to remove them and bridge their pads if it comes to that.

That most likely means you don't have a very recent mesaflash installation.

The bin file header parsing was changed on more recent mesaflash versions
to accommodate longer path-names (the build path-name is embedded in
the .bin file header)

Sorry @PCW, I need to request your help once more... I tried flashing the bin file with
and I get 
Error: Wrong bitfile destination device: Trion, should be T20F256

Should I have set somewhere in Efinity the type of board used? I started simply from the 7i92t.zip, taking the 7i92t_G540x2_34 file as basis...

I download the filewhen I try to use the pi image i get this errorwhat am I doing wrong?thanks      

So  I just did a Linux watch on the linuxcnc.var file for each change. 
Immediately after I loaded the NGC file the #5223 changed to the -364.743 value. I had previously set
the value to zero before I started linuxcnc.

This is the NGC file that I loaded is as follows:
%
G90 G94 G17 G91.1
G21
(G53 G0 Z0.)
(FACE1)
T36 M6
S12000 M3
G94 G4 P8.
G17 G90
G54
G64 P0.001 Q0.001
M8
G0 X188.156 Y-1.472
Z15.
G0 Z5.

G17
M5
G53 G0 Z0.
(Move Z all the way to the top)
M30
%

Hi PCW,

I was able to get 2.10 installed which I have posted about on the other post.  The output of periodm pins is as follows (just copied and pasted and I tried to clean up some):

    38  u32   I/O            0x00000001     hm2_7i96s.0.periodm.00.averages
    38  float OUT               59.1607       hm2_7i96s.0.periodm.00.duty_cycle
    38  float IN                      0               hm2_7i96s.0.periodm.00.duty_cycle_offset
    38  float IN                    100             hm2_7i96s.0.periodm.00.duty_cycle_scale
    38  float IN                      1               hm2_7i96s.0.periodm.00.filtertc_us
    38  float OUT              102354.1      hm2_7i96s.0.periodm.00.frequency
    38  bit   OUT                  TRUE        hm2_7i96s.0.periodm.00.input_status
    38  bit   I/O                 FALSE           hm2_7i96s.0.periodm.00.invert
    38  float IN                      1               hm2_7i96s.0.periodm.00.minimum_frequency
    38  float OUT                  9.77          hm2_7i96s.0.periodm.00.period_us
    38  bit   OUT                  TRUE        hm2_7i96s.0.periodm.00.valid
    38  float OUT                  5.78          hm2_7i96s.0.periodm.00.width_us

I think the pin I am looking for is 'hm2_7i96s.0.periodm.00.duty_cycle'.  This should let me read the duty cycle of the input PWM cycle into pin 29 (which is actually TB2 Pin 13,14 as the naming convention is not complex enough here...).  Do you agree with the assessment? 

Best,
-Dylan