[SOLVED] 5i25 wrong mesaflash release generate flashing of INIT led

More
9 years 4 months ago #94605 by bkt
ok now I can install the right bit file from my ubu16 pc...... but the config not wont to start:
Code:
jo@jo56:~/linuxcnc-dev/src$ linuxcnc LINUXCNC - 2.8.0~pre1 Machine configuration directory is '/home/jo/linuxcnc-dev/configs/giorgio1' Machine configuration file is 'giorgio1.ini' Starting LinuxCNC... Found file(REL): ./giorgio1.hal Note: Using POSIX realtime hm2: loading Mesa HostMot2 driver version 0.15 hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7 hm2_pci: discovered 5i25 at 0000:04:00.0 hm2/hm2_5i25.0: Smart Serial Firmware Version 43 Board hm2_5i25.0.7i77.0.0 Hardware Mode 0 = standard Board hm2_5i25.0.7i77.0.0 Software Mode 0 = input_output Board hm2_5i25.0.7i77.0.0 Software Mode 1 = io_analog Board hm2_5i25.0.7i77.0.0 Software Mode 2 = io_analog_fieldvoltage Board hm2_5i25.0.7i77.0.0 Software Mode 3 = io_encoder_analog_fieldvoltage Board hm2_5i25.0.7i77.0.1 Hardware Mode 0 = standard Board hm2_5i25.0.7i77.0.1 Software Mode 0 = analogout_enables hm2/hm2_5i25.0: 34 I/O Pins used: hm2/hm2_5i25.0: IO Pin 000 (P3-01): IOPort hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort hm2/hm2_5i25.0: IO Pin 002 (P3-02): IOPort hm2/hm2_5i25.0: IO Pin 003 (P3-15): Smart Serial Interface #0, pin TxData1 (Output) hm2/hm2_5i25.0: IO Pin 004 (P3-03): Smart Serial Interface #0, pin RxData1 (Input) hm2/hm2_5i25.0: IO Pin 005 (P3-16): Smart Serial Interface #0, pin TxData0 (Output) hm2/hm2_5i25.0: IO Pin 006 (P3-04): Smart Serial Interface #0, pin RxData0 (Input) hm2/hm2_5i25.0: IO Pin 007 (P3-17): Muxed Encoder Select #0, pin Mux Select 0 (Output) hm2/hm2_5i25.0: IO Pin 008 (P3-05): Muxed Encoder #0, pin Muxed A (Input) hm2/hm2_5i25.0: IO Pin 009 (P3-06): Muxed Encoder #0, pin Muxed B (Input) hm2/hm2_5i25.0: IO Pin 010 (P3-07): Muxed Encoder #0, pin Muxed Index (Input) hm2/hm2_5i25.0: IO Pin 011 (P3-08): Muxed Encoder #1, pin Muxed A (Input) hm2/hm2_5i25.0: IO Pin 012 (P3-09): Muxed Encoder #1, pin Muxed B (Input) hm2/hm2_5i25.0: IO Pin 013 (P3-10): Muxed Encoder #1, pin Muxed Index (Input) hm2/hm2_5i25.0: IO Pin 014 (P3-11): Muxed Encoder #2, pin Muxed A (Input) hm2/hm2_5i25.0: IO Pin 015 (P3-12): Muxed Encoder #2, pin Muxed B (Input) hm2/hm2_5i25.0: IO Pin 016 (P3-13): Muxed Encoder #2, pin Muxed Index (Input) hm2/hm2_5i25.0: IO Pin 017 (P2-01): IOPort hm2/hm2_5i25.0: IO Pin 018 (P2-14): IOPort hm2/hm2_5i25.0: IO Pin 019 (P2-02): IOPort hm2/hm2_5i25.0: IO Pin 020 (P2-15): IOPort hm2/hm2_5i25.0: IO Pin 021 (P2-03): IOPort hm2/hm2_5i25.0: IO Pin 022 (P2-16): IOPort hm2/hm2_5i25.0: IO Pin 023 (P2-04): IOPort hm2/hm2_5i25.0: IO Pin 024 (P2-17): IOPort hm2/hm2_5i25.0: IO Pin 025 (P2-05): IOPort hm2/hm2_5i25.0: IO Pin 026 (P2-06): IOPort hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort hm2/hm2_5i25.0: IO Pin 031 (P2-11): IOPort hm2/hm2_5i25.0: IO Pin 032 (P2-12): IOPort hm2/hm2_5i25.0: IO Pin 033 (P2-13): IOPort hm2/hm2_5i25.0: registered hm2_5i25.0: initialized AnyIO board at 0000:04:00.0 note: MAXV max: 950.000 units/sec 57000.000 units/min note: LJOG max: 950.000 units/sec 57000.000 units/min note: LJOG default: 500.000 units/sec 30000.000 units/min note: AJOG max: 220.000 units/sec 13200.000 units/min note: AJOG default: 180.000 units/sec 10800.000 units/min waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> /home/jo/linuxcnc-dev/bin/milltask (pid 3701) died on signal 11, backtrace stored in /tmp/backtrace.3701 /home/jo/linuxcnc-dev/bin/milltask exiting waiting for s.joints<0>, s.kinematics_type<0> <commandline>:0: milltask exited without becoming ready waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> waiting for s.joints<0>, s.kinematics_type<0> halui: emcCommandSend: no echo from Task after 5.000 seconds A configuration error is preventing LinuxCNC from starting. More information may be available when running from a terminal. Shutting down and cleaning up LinuxCNC... Running HAL shutdown script hm2_5i25.0: dropping AnyIO board at 0000:04:00.0 hm2/hm2_5i25.0: unregistered RTAPI_PCI: Unmapped 65536 bytes at 0x7ff5c5162000 hm2_pci: driver unloaded hm2: unloading Note: Using POSIX realtime LinuxCNC terminated with an error. You can find more information in the log: /home/jo/linuxcnc_debug.txt and /home/jo/linuxcnc_print.txt as well as in the output of the shell command 'dmesg' and in the terminal

these the backtrace:
Code:
Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operazione non permessa. /home/jo/linuxcnc-dev/configs/giorgio1/3701: File o directory non esistente. No thread selected No stack.

this my print.txt
Code:
RUN_IN_PLACE=yes LINUXCNC_DIR= LINUXCNC_BIN_DIR=/home/jo/linuxcnc-dev/bin LINUXCNC_TCL_DIR=/home/jo/linuxcnc-dev/tcl LINUXCNC_SCRIPT_DIR= LINUXCNC_RTLIB_DIR=/home/jo/linuxcnc-dev/rtlib LINUXCNC_CONFIG_DIR= LINUXCNC_LANG_DIR=/home/jo/linuxcnc-dev/src/objects INIVAR=inivar HALCMD=halcmd LINUXCNC_EMCSH=/usr/bin/wish8.6 INIFILE=/home/jo/linuxcnc-dev/configs/giorgio1/giorgio1.ini VERSION=1.0 PARAMETER_FILE=linuxcnc.var TASK=milltask HALUI=halui DISPLAY=axis COORDINATES=X Y Z A KINEMATICS=trivkins Starting LinuxCNC server program: linuxcncsvr Loading Real Time OS, RTAPI, and HAL_LIB modules Starting LinuxCNC IO program: io Starting HAL User Interface program: halui Starting TASK program: milltask Starting DISPLAY program: axis Killing task linuxcncsvr, PID=5347 Removing HAL_LIB, RTAPI, and Real Time OS modules Removing NML shared memory segments

whats happens?

regards
giorgio

Please Log in to join the conversation.

More
9 years 4 months ago #94608 by PCW
The error:

/home/jo/linuxcnc-dev/bin/milltask (pid 3701) died on signal 11, backtrace stored in /tmp/backtrace.3701

Is not related to the I/O hardware, you might look at the backtrace or dmesg for more clues to why milltask crashed

Note that there are a number of LinuxCNC things that do not work properly with 16.04, at the minimum
I would run the latest 2.7 LinuxCNC version (2.7.9) or master

Please Log in to join the conversation.

More
9 years 4 months ago #94609 by PCW
Yes, there are a number of permission issues on 16.04, these _may_ be fixed on 2.7.9 but I'm not sure
They are (at least mostly) fixed in master

Please Log in to join the conversation.

More
9 years 4 months ago #94611 by bkt
ok --- but running my config on axis-gui the intro show 2.8.0-pre1 ... and today I've downlod from git master branch ....

I make an error about ubu version : really is a 14.04 kernel 4.8.15 rt10 ... and probabily I make an other error .. last time on these pc I've install on linuxcnc-dev folder today on linuxcnc-dev/src ....but the config folder is on linuxcnc-dev ...

any how you can suggest me a better release with that kernel? So I can remove the old and install the best one

regards
giorgio

Please Log in to join the conversation.

More
9 years 4 months ago #94613 by PCW
Is it possible you didn't build LinuxCNC properly? (especially the "sudo make suid" step

Please Log in to join the conversation.

More
9 years 4 months ago #94617 by bkt
no every step ... only 4 warning on compile step ... previously I have an error from hy_vdf.c file causing from libmodbus timeout calling ... so I correct the file and re install again...

So for greater security I want to delete everything and reinstall ... what do you suggest 2.7.8? Or master is still the best?

p.s. Actually I delete the linuxcnc-dev folder than I use sudo apt-get purge linuxcnc* command and it return:

impossible to find linuxcnc_2.8.0~pre1_amd64.build

so for shure I've not Lcnc install on these pc .... If you tell me it's better to stay on master, then install master, otherwise install the version that you suggest ... rest waiting ... at least if there are problems will not be from the mesa card.

Apart from what you think of the latency on the published histogram? Is it good enough for a servo system?


regards
giorgio

Please Log in to join the conversation.

More
9 years 4 months ago #94620 by PCW
You should be able to run 2.7.9 (latest release) or 2.8.0 (master) on Ubuntu 14.04 without any issues (I've run this combo for a year or so until I upgraded it to 16.04) 16.04 works but has some minor things that don't work
You do of course need to build the uspace version when using a Preempt-RT kernel

Latency really doesn't matter much on servo systems or hardware step/dir systems
100 usec latency should be fine, and more can be tolerated with the correct firmware
(up to about 1/2 of the servo thread period = 500 usec)

You have to have a pretty bad real time system to have 500 usec latency

Please Log in to join the conversation.

More
9 years 4 months ago #94622 by bkt
sorry a minor question ... have you run mesa fpga card over vxworks recently?

said these ...
Thanks
for the support today.

(Another day of work that will end at 24 o'clock ... :pinch: )

giorgio

Please Log in to join the conversation.

Time to create page: 0.051 seconds
Powered by Kunena Forum