Advanced Search

Yes, because the FPGA cards have pullup resistors on all I/O pins to +5V
Simple grounding a I/O pin will work for input signaling

For outputs, because of the pullups, the initial state of all I/O pins will be high
so its best to use active low outputs (and best to the the 7I75s 5V output)

So for say driving a SSR or OPTO:

7I75 5V --> SSR+ or OPTO Anode
7I75 I/O --> SSR- or OPTO Cathode

In HAL you need to set the is_output and usually
invert_output parameters for GPIO pins used as outputs.

As an update this will no longer be an issue with Trixie, as the live build process blacklists the raspi-firmware from being installed.
And just be 100% clear the source of this issue was the live-build utility prior to Debian Trixie.
Unless new Bookworm ISOs are released built with the live-build utility built from the Trixie source it will forever be an issue.
Having delved into this issue and built new ISOs using the live-build that comes with Trixie ( and repackaging and installing on bookworm ) I can say this issue is fixed. It took a bit of delving into the various scripts that do the hard lifting to find the issue.
It could of been fixed a couple of ways, the above mentioned modification to the preseed file on the ISO, but the raspi- firmware would have still been present on a live session, or individually picking the firmware to install, unfortunately I do not think the cause of the issue was fully understood.
From Trixie on this is fixed.

Habe mir eine MESA 7i75 gekauft und bin unsicher bezüglich Beschaltung.
Als Eingang muss ich nur den IO  Port mit dem nebenliegenden GND verbinden durch z.B. einen Taster oder Schalter?
Als Ausgang gehe ich mit den 5V auf z.b. ein Relais und dann auf den IO Port? 

Danke
Harald
 

cnc@raspberrypi:~$ % halrun
halcmd: loadrt cia402pv names=cia402pv.Spindle
Note: Using POSIX realtime
halcmd: show all
bash: fg: %: no such job
bash: halcmd:: command not found
bash: Note:: command not found
bash: halcmd:: command not found
cnc@raspberrypi:~$ halrun
halcmd: loadrt cia402pv names=cia402pv.Spindle
Note: Using POSIX realtime
halcmd: show all
Loaded HAL Components:
ID Type Name PID State
4 RT cia402pv ready
2 User halcmd2602 2602 ready

Component Pins:
Owner Type Dir Value Name
4 float IN 0 cia402pv.Spindle.acceleration
4 u32 OUT 0x00000000 cia402pv.Spindle.controlword
4 float IN 0 cia402pv.Spindle.deceleration
4 s32 OUT 0 cia402pv.Spindle.drv-acceleration
4 s32 IN 0 cia402pv.Spindle.drv-actual-position
4 s32 IN 0 cia402pv.Spindle.drv-actual-velocity
4 s32 OUT 0 cia402pv.Spindle.drv-deceleration
4 bit OUT FALSE cia402pv.Spindle.drv-fault
4 s32 OUT 0 cia402pv.Spindle.drv-quickstop-deceleration
4 s32 OUT 0 cia402pv.Spindle.drv-target-position
4 s32 OUT 0 cia402pv.Spindle.drv-target-velocity
4 bit IN FALSE cia402pv.Spindle.enable
4 bit IN FALSE cia402pv.Spindle.fault-reset
4 bit I/O FALSE cia402pv.Spindle.home
4 s32 OUT 0 cia402pv.Spindle.opmode
4 bit OUT FALSE cia402pv.Spindle.opmode-cyclic-position
4 bit OUT FALSE cia402pv.Spindle.opmode-cyclic-velocity
4 s32 IN 0 cia402pv.Spindle.opmode-display
4 bit OUT FALSE cia402pv.Spindle.opmode-homing
4 bit OUT FALSE cia402pv.Spindle.opmode-no-mode
4 bit OUT FALSE cia402pv.Spindle.opmode-profile-velocity
4 float IN 0 cia402pv.Spindle.pos-cmd
4 float OUT 0 cia402pv.Spindle.pos-fb
4 float IN 0 cia402pv.Spindle.quickstop-acceleration
4 s32 OUT 0 cia402pv.Spindle.read-all.time
4 bit IN FALSE cia402pv.Spindle.run
4 bit OUT FALSE cia402pv.Spindle.stat-at-speed
4 bit OUT FALSE cia402pv.Spindle.stat-fault
4 bit OUT FALSE cia402pv.Spindle.stat-homed
4 bit OUT FALSE cia402pv.Spindle.stat-homing
4 bit OUT FALSE cia402pv.Spindle.stat-op-enabled
4 bit OUT FALSE cia402pv.Spindle.stat-quick-stop
4 bit OUT FALSE cia402pv.Spindle.stat-quick-stop-valid
4 bit OUT FALSE cia402pv.Spindle.stat-remote
4 bit OUT FALSE cia402pv.Spindle.stat-switched-on
4 bit OUT FALSE cia402pv.Spindle.stat-switchon-disabled
4 bit OUT FALSE cia402pv.Spindle.stat-switchon-ready
4 bit OUT FALSE cia402pv.Spindle.stat-target-reached
4 bit OUT FALSE cia402pv.Spindle.stat-voltage-enabled
4 bit OUT FALSE cia402pv.Spindle.stat-warning
4 bit OUT FALSE cia402pv.Spindle.stat-zero-speed
4 u32 IN 0x00000000 cia402pv.Spindle.statusword
4 float IN 0 cia402pv.Spindle.velocity-cmd
4 float OUT 0 cia402pv.Spindle.velocity-fb
4 s32 OUT 0 cia402pv.Spindle.write-all.time

Pin Aliases:
Alias Original Name

Signals:
Type Value Name (linked to)

Parameters:
Owner Type Dir Value Name
4 bit RW TRUE cia402pv.Spindle.auto-fault-reset
4 bit RW TRUE cia402pv.Spindle.csp-mode
4 float RW 1 cia402pv.Spindle.pos-scale
4 bit RW FALSE cia402pv.Spindle.pv-mode
4 s32 RW 0 cia402pv.Spindle.read-all.tmax
4 bit RO FALSE cia402pv.Spindle.read-all.tmax-increased
4 float RW 1 cia402pv.Spindle.velo-scale
4 s32 RW 0 cia402pv.Spindle.write-all.tmax
4 bit RO FALSE cia402pv.Spindle.write-all.tmax-increased

Parameter Aliases:
Alias Original Name

Exported Functions:
Owner CodeAddr Arg FP Users Name
00004 7fff005c2a20 7fff005f0120 YES 0 cia402pv.Spindle.read-all
00004 7fff005c1e04 7fff005f0120 YES 0 cia402pv.Spindle.write-all

Realtime Threads:
Period FP Name ( Time, Max-Time )

halcmd: Note: Using POSIX realtime
cnc@raspberrypi:~$

The easiest way is to use pncconfs  "Discovery" option

You need to select "Show Advanced Option Pages"
on the first pncconf page for the discovery option
to be available.

added. no error but also no apparent change?
What is expected to happen here?

thanks!

If you are using the DIR+ and STEP+ do not connect the DIR- nor the STEP- to ground. When using the - signals do not connect the + to 5v.
When I installed my VFD the wiring diagram included an AC line reactor, which I duly installed.
Generally the shielding is only connected at one end, this is to prevent ground loops.

Personally I wouldn't supply any voltage than 3.3v to the input of an RPi. If 5v signal was required I would either using a 74lvc245 or an opto isolator, with the opto isolator being the preferred choice, and despite what some schematics suggest do not connect the grounds and do use seperate power sources for each side of the opto, otherwise you are not getting any isolation.
Any grounds should be connected to a single point, aka star, once again to prevent ground loops.
Make sure to use quality power supplies, Meanwell from a reliable supplier, are a good choice.
Simple things such as using bootlace ferrules is good practice instead of bare wires into screw terminals. When using crimp connectors do not solder the joint, the solder will which up the wire and any movement will cause the wire to break. A proper crimp will cold weld the wire and crimp connector. This is the same thing that happens when wire wrapping, ask NASA about the effectiveness of a quality wire wrapped connection .

It's like cia402pv isn't loaded.
Try a new thing. The halrun utility, load the cia402pv component manually.This hopefully should work and produce a long list of pins and functions.

Hi
I installed the received **.bit file on the card from the command line.
When I read it back from the card, everything is fine.
How can I insert the custom config into Pncconf?
 

Add num_spindles=1

1. No 7I96S step/dir pin should ever be wired to 5V or ground.
This directly shorts out the drivers and if done for more
than a short time will damage the driver chips.

2. Not sure what you mean by this:
I wired them to Raspberry Pi GPIO using external 10k pull-ups.

3. Are the pins you have trouble with encoder pins (TB2 pins)
or isolated input pins?

P1 pinout is standard header pinout
pin one is marked with the Square

1 2
3 4
5 6
7 8
 etc

Note that mesaflash show equivalent DB25 pins
(if you use the latest mesaflash you can show HDR26 pins
with the --dbname hdr26 option)

Hello everyone,

I'm looking to buy some boards from Mesa Electronics:

1x 7i73

1x 7i74

1x 7i97T

1x 7i84U

I'm located in Argentina, but when I try to order from the Mesa US website, Argentina isn't listed as a shipping option.

Does anybody know if there are any official resellers in South America, or if there's a way to purchase directly from Mesa and get them shipped here?

Thanks!

Maybe this helps:
linuxcnc.org/docs/html/gcode/o-code.html...outine_return_values

Hello everyone
I am encountering an issue that appears to be EMI-related despite applying the usual mitigation steps.
EMI / System Setup:
VFD in steel enclosure
Input EMI filter
Ferrite rings on VFD output and all related cables
Shielded spindle/motor cables (grounded both ends)
AC/VFD cabling physically separated from DC lines
High-current DC cables are shielded and routed separately
Control Setup:
I am using the 7i96S encoder pins for MPG inputs (I have no motor or spindle encoders).
I do not have any unused OUT pins and only 4 available IN pins.
To get X, Y, Z, X1, X10, and X100 signals, I wired them to Raspberry Pi GPIO using external 10k pull-ups.
Issue
After wiring the MPG inputs, some of the pins intermittently remain latched HIGH or LOW, making jog selection unreliable. This problem has occurred twice, and both times it started after spindle-speed testing.
Earlier in setup, I believe I damaged one of the 7i96S step/dir channels. After that, instead of wiring STEP- and DIR- to GND and STEP+ / DIR+ to the respective inputs, I reversed them — STEP+ and DIR+ to +5V and STEP- / DIR- to the Mesa pins.I have since added additional ferrites and shielding, Ferrites on servo lines, data cables, and MPG cable
Steel mesh added to enclosure ventilation fans but the issue persists.
I am now planning to use the P1 pins on the 7i96S for X/Y/Z and X1/X10/X100 inputs instead.
W6 jumper is OFF.
Questions

1. The MPG has extra wires that appear intended to power LEDs or similar features. Can these be safely powered from the 5V rail, or is that risky for the inputs?
2. Where exactly are pin 1 and pin 2 physically located on the P1 expansion header?
3. Which P1 pins are appropriate to use for these MPG signals?
4. May I safely use 5V for the MPG input power in this configuration?
5. Any recommendations to avoid EMI issues when using these inputs on the 7i96S?
   
   Thank you for your help.
   
   
   

Hmm I wonder why apt purge worked in my situation ?

And why did it work when I created a new ISO and added a line to pressed that ran apt purge to remove the rasp firmware at the end of the installation process ?