Advanced Search

What happens if you use `nomodeset` on the kernel cli?

forum.linuxcnc.org/plasma-laser/38974-di...rything-in-one-place

forum.linuxcnc.org/plasma-laser/35349-cn...lding-info-and-guide

sudo apt install linux-headers-$(uname -r)

here are my config files for the machine
Due to the problems I have disconnected the motors. As a test, I had one motor rotating freely on the controller - no difference. I now have an oscilloscope and can check the output of the motor signals if necessary. Currently, only the Ethernet cable and the power supply are connected to the Mesa 7i96s.

Created with PnConf Standard with minimal settings. No limit switches and no sensors. Settings for my JMC cl stepper (microsteps, 5mm/rev ...)

Maybe I have a fundamental error in the configuration? 

 

Hi Guys.
Well the problem is i want to retrofit a plasma, current motors and electronics are not working correctly.
I will put NEMA 34 whit a 1:5 gearbox -> rack and pinion , only on X,Y axis, Z will be driven with a NEMA24 (using the existing lead screw)
Still not sure , open loop or closed loop steppers (more cabels more chances of EMI)
So all I/O <-> (HOME ,LIMIT , THC , USER BUTTON) will be optically isolated with a relay and additional optocoupler (machine <-> MEASA )
The current setup has an braded cable sleeve around the plasma cable in a drag chain besides all the other cables.
My question is what should i do about HF/HV arc start of the Hyperterm max 100?
I know grounding is imperative.  The CNC electronics box will well away from the plasma transformer.
Add an aditional ground rod?
Kind regards Marko



 
 

Please post you hal/ini files
something basic is wrong with them

Hi Tommylight,
I installed your iso
Without any changes I get these Results 
 

In a short test without Watchdog error 
 

Next step is define the grub Parameter. But there's no grub customizer 

Regards 
Erwin 
 

Maybe wiring? Enable?

A couple of comments

There is no base period.

The maximum velocity is not dependent on the servo thread period.

You should get no latency dependent following errors unless"

1. The latency is so bad that a whole servo cycle is skipped

2. The DPLL does not have enough headroom to account for
linux's baseline timing drift (fix by setting the timer to a larger
negative number say -200)

I made some breaker bars out of alu to test it. about .001" springy with as much force as i can comfortably apply. not terrible at all. i had to lightly clamp it since its surprisingly easy to back drive. 







 

Sorry so slow but massive interruptions and a few train wrecks to clean up...

I have the 7i95t working completly now and would like to share what I've learned about getting this board to work with linuxcnc 2.10pre. MesaCT tool 2.1.7 doesn't currently support the 7i95t and neither does pncconf as compilied with 2.10pre however using the information in the file Under ADDING_A_MESA_CARD.md along with lots of searching and some trial and error I managed to create a good working entry for the private_data.py file. Pnccconf can now use this information to create a working configuration. I've attached this information in "pncconf for 7i95t".

I didn't include the P1 expansion connector as the 7i95t has sufficient resources for all my needs. It would be very easy to add however if you need it.

Now when you run pncconf you can select the 7i95t and properly configure it as required however the ~/linuxcnc/configs/<config name>.hal file needs a minor tweak before linuxcnc can use it. It seems pncconf translates inmux to inm and that needs to be fixed (thanks to user merongi on the forum). To do this I simply created a one line script since this must be fixed everytime you run pncconf. Basicly you need:
sed -i 's/inm.00/inmux.00/g' ~/linuxcnc/configs/<config name>/<config name>.hal 

Now you can run linuxcnc.

I also wanted to add a joystick for X & Y axis that will provide the same function as the Up/Down. Left/Right arrow keys of the keyboard. While HAL overall and creating the necessary entries is well documented finding the right inputs took me a lot of study/trial and error with halshow to find the right signals. First assign inputs to each switch using the drop down selection Axis Rapid -> Jog xx in pncconf as appropriate. Pncconf will create the necessary entry in your <config name>.hal. To connect these inputs you need to map them appropriately. Here's the custom.hal contents I created to accomplish this (this implies X is joint 0 and Y is 1):

setp halui.joint.jog-speed 6500
net jog-x-neg => halui.joint.0.minus
net jog-x-pos => halui.joint.0.plus
net jog-y-neg => halui.joint.1.minus
net jog-y-pos => halui.joint.1.plus

The last item I spent time on was getting clarity on proper setup to eliminate Following Errors. Following some comments from andypugh and PCW I was able to clean this up. Here's a quick recap of the knowlege shared:
base period max velocity > stepgen max velocity > machine max velocity
Each step requires headroom (say 5-25% each)

My interpertation is in the Screen section of pncconf you set Min linear velocity and Max linear velocity. They become in the <config name>.ini file:
[TRAJ]
...
DEFAULT_LINEAR_VELOCITY = xx
MAX_LINEAR_VELOCITY = xx        which is machine max velocity in the equation above

Under each Axis you set Max Velocity which becomes MAX_VELOCITY in the <config name>.ini file. STEPGEN_MAXVEL is automatically calculated by pncconf at 125% of the MAX_VELOCITY (which is required also).

If I'm correct, the base period max velocity can be computed by ACTUAL SERVO PERIOD / highest STEPGEN_MAXVEL used by any motor. You need to allow head room here so I multiply it by 0.75.

Now you have all three components which allows you to avoid following errors, or at least it works for me. While not clearly stated, the max jitter value could also be a factor. If it's excessively high you will likely need more than 25% headroom.

Comments and corrections always welcome.

Mike

For those who may be interested. I've updated the remora-spi component to now interrogate the device tree to determine the hardware being used.

github.com/scottalford75/Remora/tree/mai...omponents/Remora-spi

I thought EINT might be the issue, there's a 1k pullup to 3.3v, the top 8 data lines have a 1k pull down.

Might be C5 around the L1 inductor, I installed a 100nf cap instead of a 4.7uf.

I don't know if that will make a lot of difference.

I've run a config, no hardware connected to the board yet, but no errors. Tho I assume writing to the flash is more of a load. It's bound to be something stupid on my behalf.

The major difference is the WP on the flash is just held high, any chance that the circuit around the WP on the flash is causing the issue, there's no reset device connected. Tho the EPP & SPI based on the 7c81 have been the same.

Thanks for the response!

I used some of the settings from the following page:
www.centroidcnc.com/dealersupport/tech_b...tins/uploads/295.pdf

I have Pn000 at 0010H and Pn002 at 0100H PN200 isn't set as in the document, it is set for positive pulse and direction input.
I've also gone through the sigma II manual especially the trial procedure and tried to go through the settings that seemed relevant.
I'm aware of the power reset to make some settings take effect.

I'm pivoting my design since I just ordered a CSF 45 harmonic drive for the B. The 40 will be the 4th axis on the table. I put a 10ths indicator on the harmonic drive. It has no backlash, which is crazy cool, but does have maybe 0.0001 of "flex" backlash if I put lots of stress on it with a wrench. Seems pretty sweet.