Advanced Search

STATUS appears...blank.

Weird.

Set it only to HOME, not HOME+LIMIT, that way you can technically cross the switch if the machine is not homed.

In fact, you can probably allow movement past the home switch properly in the config or stepconf or whatever.

I don't think the home switch needs to necessarily be at the end of the travel.

Mid-travel home switches should be possible.

Referencing this post forum.linuxcnc.org/29-forum-announcement...-9-6-released#336514 is there a possibility of a 2.9.7 release or something along those lines.
The reason I ask as I have been working on trying to create an ISO that doesn't suffer from the "raspi-firmware" issue. And I would like to have a dialogue with regards to releasing a 2.9.x ISO.

Yes, that’s the weird part. It is correct.




INI for Z it’s like this:



[AXIS_Z]
# MAX_VEL & MAX_ACC need to be twice the corresponding joint value
MAX_VELOCITY = 66.66666666666667
MAX_ACCELERATION = 1500.0
OFFSET_AV_RATIO = 0.5
MIN_LIMIT = -0.0
MAX_LIMIT = 250.0

[JOINT_2]
TYPE = LINEAR
HOME = 250.0
FERROR = 10.0
MIN_FERROR = 1.0
MAX_VELOCITY = 33.333333333333336
MAX_ACCELERATION = 750.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 41.67
STEPGEN_MAXACCEL = 937.50
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 3000
STEPSPACE = 3000
STEP_SCALE = -1000.0
MIN_LIMIT = -0.0
MAX_LIMIT = 250.0
HOME_OFFSET = 260.000000
HOME_SEARCH_VEL = 16.666667
HOME_LATCH_VEL = 5.000000
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_SEQUENCE = 2

So it was a mistake, that is a huge relief.
And i was not aware who did it as i did not bother to check from frustration.
Thank you.

I can absolutely understand if it was a mistake, but from a bit of reading it does not seem to.

So you think that I broke AxisGUI on purpose to fix something in Gmoccapy? Really?
I'm sorry to say but comments like these are what I would call 'plain absurdity'.
And just to warn you there is going to be yet another release because I screwed up fixing yet another bug.

Ethernet latency is the most common cause of the "Error finishing read"  fault

It basically means you have lost connection to the card, either because too
many read requests went unanswered within in the time limit  (with default settings
that time limit is 80% of the servo thread period and 5 successive requests must time out)

This may be caused by poor Ethernet latency or something more basic like power problems
on the FPGA card, host Ethernet power management issues, or Ethernet hardware problems.


What LEDs are illuminated on the 7I96S when you get the error?

Can you run this command after LinuxCNC gets the error and post the results here:

halcmd show all *.tmax

Also the CPU speed would help.

 

I have disabled all BIOS performance options:

- C-States
- Intel Turbo Boost Technology
- EIST

And so on.

But the error keeps appearing.

I have tried everything. I am quite frustrated with Mesa and LinuxCNC. I knew it wouldn't be easy, but not this complicated!

There's also 7I96S firmware to allow a parallel connected MPG to connected
the  7I96S's P1 expansion connector:

forum.linuxcnc.org/27-driver-boards/4691...ncoder-on-p1?start=0

Go to Profile and then Favorites tab.

Connected the laser mounting screw to the machine and the control board ground contact with a wire. No changes.
I connected a voltmeter directly to the wire at the laser input.
At m30, the voltage is 0.26, and at m3, the voltage is 4.7. The spindle frequency converter is connected here as well and is controlled normally.

The machine controller board indicator also responds appropriately—it turns on and off at m3 or m30.

Good question. The laser has three inputs: 
1. PWM
2. +12V
3. Ground. 

Is 3 ground or -12V?

The laser itself operates from the mechanical switch button on the laser. Logically, it needs a separate + and a separate -. I don't see a ground contact.
When attempting to connect pin 3 (ground) of the laser to the ground of the control board (instead of minus 12V), the laser does not flash and the fan does not spin.

OK, 5V TTL, so should work as is, but did you wire the GND on BOB to GND on laser?

The laser has 3 inputs. PWM, +12v and ground.

This has been already answered and promptly ignored here
forum.linuxcnc.org/10-advanced-configura...aser?start=30#336428
-

abs32 wrote:

The spindle can be controlled normally with these parameters. If you connect a laser PWM to pin 14 instead, the laser should work somehow, either via M68 or M3S24000.

But the laser does not turn on. Only with the forced activation button on the laser body, and immediately at 100% power.

You should have started with this as it clearly shows the wiring is incorrect or there is a signal mismatch, so what does your laser input work with?
How many inputs does it have?