Advanced Search

Can you tell me how you did it? where did you put the folder? I'm still new to Linuxcnc, I'm having a little trouble understanding it

Kamran,
Thanks, I will take you up on your offer.

Powered up the system at 15 degrees C this morning and got for ping "not reachable".
Went through menu-config, changed nothing.
Then ping and got 86 packets through, frozen count, stats 45% lost.

Earthing looks good, card power is 5.07 V.

John.

Hi folks,

Does anyone have access to the mesaflash source files for v2.10.1 ?

I have been trying to attach a 7I80HDT board but my 2.9.0 mesaflash gets upset, it looks like they have a specific mesaflash that does not include certain boards... I can make the 2.9.0 mesaflash from source but it does not support the 7i80HTD...or 7i92t both of which i wish to use.
The latest version from git need dependencies (libmd-dev)  that don't seem to exist for pathpilots version of linux so that won't work for either...

Any help would be greatly appreciated I don't want to be unable to use these boards...

Thank you 

Dorro
 

thankyou aciera, i think i understand what you did there and it sorted that part out, so i can call multiple post_gui.hal files that way, very cool. now im back to this error

PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=
DISPLAY=axis
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYYZ kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Found file(REL): ./PRINTNC.hal
Found file(REL): ./Probe_preload.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
Shutting down and cleaning up LinuxCNC...
task: 214 cycles, min=0.000032, max=0.014714, avg=0.009666, 0 latency excursions (> 10x expected cycle time of 0.010000s)
INFO CLASSICLADDER---I/O modbus master closed!
Failed to open serial port /dev/ttyUSB0...
INFO CLASSICLADDER---I/O modbus master Data bits 8 Stop bits 1 Parity 0
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=1/1) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=2/2) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=3/3) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=4/4) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=5/5) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=6/6) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=7/7) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=8/8) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=9/9) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=10/10) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=11/11) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=12/12) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=13/13) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=14/14) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- Error initializing classicladder user module.
config string '0 out'
creating ladder-state
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
Unexpected realtime delay on task 0 with period 35000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.

(classicladder:1113): Gtk-CRITICAL **: 22:35:07.063: IA__gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
note: MAXV max: 146.670 units/sec 8800.200 units/min
note: LJOG max: 146.670 units/sec 8800.200 units/min
note: LJOG default: 30.000 units/sec 1800.000 units/min
note: jog_order='XYZ'
note: jog_invert=set([])
custom_postgui.hal:23: Pin 'parport.0.pin-15-in' was already linked to signal 'probe-input'
1092
1134
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

so i uncomment the
net probe-input motion.probe-input <= parport.0.pin-15-in
line in my hal file and i get
custom_postgui.hal:31: Pin 'halui.mdi-command-00' does not exist
i need to understand why im getting the probe pin error and then why im getting the second error for the hal ui command

I had the polarity of the leads backwards. This was the initial issue, the invert would have been my next. Thanks for the help!

there is a section in the bergerda manual that im having trouble understanding the purpose. section 2.6. the digital input and out put interface. what are they referring too? i know i probably don't need to worry about it. im having trouble understanding what they are trying to purvey. this bergerda servo has been a negative experience for me and i don't recommend anyone put themselves through that. and forget about customer service. if they even answer at all, their responses are limited. as always, thank you, i appreciate your expertise and tutelage.

I think I have asked this before but couln't find the question or the answer...

Still running debian 10 with linuxcnc 2.8.4.
I have a python hal component (hal_serialtoolchange) which I wrote quite long ago for my lathe tool changer.
I don't remember which version of linuxcnc was used in the development but then everything printed from code (stdout) was prionted to terminal if linuxcnc was started fron command line. Maybe it was 2.7 or 2.6
Now I need to make some changes to the code but the output is not visible so it's quite hard to debug. If linuxcnc crashes the output can be seen but that does not help.
Is there some flag or other setting to enable output ?
Of course it's possible to open a file from python and write an own log...

You are welcome. I'll push the fix to linuxcnc.
Thanks for testing.

Können Sie Ihre hal an ini-Dateien posten?
 

Servus strahlensauger.

Ich habe die Endschalter montiert. Es sind Induktive Endschalter an Minimum und Maximum jeder Achse. Das Homing funktioniert (noch) nicht. Ist aber für den Moment auch nicht so wichtig. Viel mehr beschäftigt mich die Spindel, die ich nicht ins Laufen bekomme. Ich habe es über PWM versucht. Aber da rührt sich rein gar nichts.

Hast du mir einen Tipp?

LG

Hans Peter

Yes they are, but worse as this/we need direct hardware access.
Look for boards with very small chips, so far that is what i noticed, they seem to be the same thing as USB>parallel.

The issue I can fathom, just out of interest, is that ret isn’t being defined for a 32 bit platform, it’s defined for x86_64, amd64 as well as 2 arm platforms.
Are you sure the driver supports a 32 bit platform ? Not that it’s going to be needed.
Wheezy is only 32 from memory.

You and Rod have both mentioned these software emulated cards, for the life of me I can’t find an example.
Are these similar to the “winmodems” of the 90s ?

I have a 7i96 brand new and unused, You are welcome to contact me in the Sydney area and Cornholio has my contact.

Cheers
Kamran

pin out bit motor_lowspeed     = 0  "MESA 7i84 OUTPUT 0: 28X1-8";

The pin created here by this component will be '<componentname>.motor-lowspeed' and is preset to FALSE.
"MESA 7i84 OUTPUT 0: 28X1-8" is just a comment, presumably the output of the 7i84 used by the author in his particular setup. This has no impact on the pin name or location whatsoever.