PathPilot V2 with 7I80DB-16 + 7i76

More
07 Mar 2019 05:04 - 07 Mar 2019 05:07 #127949 by mjoconr
Hi All
I'm trying to get PP 2 working with a 7I80DB-16 + 7i76 and I've gotten to the point of getting the correct bit file flashed during PP boot but it shutdown after the following in the log.

I assume that 7i80db_16_7i76x3.bit is the correct bit file, but I wonder about the config of HOSTMOT2 DRIVER_PARAMS
[HOSTMOT2]
DRIVER=hm2_eth
BOARD=7i80
DRIVER_PARAMS="board_ip=10.10.10.10 config=num_encoders=0 num_pwmgens=1 num_3pwmgens=0 num_stepgens=5 "
BITFILE0=mesa/7i80db_16_7i76x3.bit
DPLL_TIMER_NUMBER = 1
DPLL_TIMER_US= -100
Starting HAL User Interface program: halui
halcmd loadusr -Wn halui halui -ini /home/operator/tmc/configs/tormach_mill/tormach_1100-3_7i92.ini
halcmd -i /home/operator/tmc/configs/tormach_mill/tormach_1100-3_7i92.ini -f tormach_mill_mesa.hal
Note: Using POSIX realtime
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10 config=num_encoders=0 num_pwmgens=1 num_3pwmgens=0 num_stepgens=5 : Hardware address: 00:60:1b:10:00:50
hm2_eth: discovered 7I80DB-16
hm2/hm2_7i80.0: Smart Serial Firmware Version 35
Board hm2_7i80.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i80.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i80.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i80.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
board fails HM2 registration
hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
tormach_mill_mesa.hal:12: waitpid failed /home/operator/tmc/bin/rtapi_app hm2_eth
tormach_mill_mesa.hal:12: /home/operator/tmc/bin/rtapi_app exited without becoming ready
tormach_mill_mesa.hal:12: insmod for hm2_eth failed, returned -1
Shutting down and cleaning up LinuxCNC...
Last edit: 07 Mar 2019 05:07 by mjoconr.

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 13:39 #127972 by pl7i92
the tormach has changed its pathpilot software many times so it is better to ask this around the trormach owned forum
as Pasthpilot now has gone its own way apart and way beond linuxcnc
there may be alot of differences

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 15:33 #127983 by PCW
Its hard to tell what the real error is but it looks like the driver
doesn't like something about the 7I80DB:

"board fails HM2 registration"

Unfortunately the actual error is not printed

One thing thats a possible issue is the age of the bitfile, can you try again with this current bitfile:

freeby.mesanet.com/7i80db_16_7i76x3d.bit

(you need to power cycle the 7I80DB after writing this new bitfile)
The following user(s) said Thank You: mjoconr

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 17:33 #128006 by smgvbest
This looks to a a hardware init issue, nothing to do with pathpilot.

Also possible is if you let PP flash the card originally with the PP bit file then you would need to power cycle the card and afterwards flashing the 7i80 bit file then and power cycle. the card may be confused.

And to clarify something I see often stated here, PP is a gui frontend to linuxcnc. highly customized yes and does not show everything Linuxcnc does but all Linux cnc features are available or can be made available. it is designed to support the features Tormach wants to support and provide a user experience for their machines.

Going to a Tormach forum with non Tormach equipment will likely get you refereed by here as Tormach does not support non-tormach installs officially

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 18:05 #128009 by PCW
The first thing I would do is _DISABLE_ any automatic flashing in startup scripts.
Since the 7I80DB is not a pathpilot supported card, letting pathpilot flash anything is probably a very bad idea

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 20:48 - 08 Mar 2019 04:22 #128028 by mjoconr
The flashing is just a config option which I’ve got worked out. That was fixes before I ran linuxcnc for the first time.

And a change to there scripts could introduce its own issues.

Mike
Last edit: 08 Mar 2019 04:22 by mjoconr.

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 20:57 - 08 Mar 2019 08:15 #128030 by mjoconr
Thats a good idea, I’ll give that a try this morning.

As has been said PP is just a UI, and any issues with getting it going will always be a LinuxCNC issue.

I’m only using PP because it has a nice interface. I actually hope to create my own UI. Just need to learn more first.

Mike
Last edit: 08 Mar 2019 08:15 by mjoconr.

Please Log in or Create an account to join the conversation.

More
07 Mar 2019 22:54 #128038 by mjoconr
So using a newer bit file has got me past first issue.
Now I think I have adjust the hal file to match the board.
see
'tormach_mill_mesa.hal:248: parameter or pin 'hm2_7i80.0.gpio.005.is_output' not found'
Starting LinuxCNC server program: linuxcncsvr
Starting LinuxCNC IO program: io
io started
halcmd loadusr io started
Starting HAL User Interface program: halui
halcmd loadusr -Wn halui halui -ini /home/operator/tmc/configs/tormach_mill/tormach_1100-3_7i92.ini
halcmd -i /home/operator/tmc/configs/tormach_mill/tormach_1100-3_7i92.ini -f tormach_mill_mesa.hal
Note: Using POSIX realtime
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 10.10.10.10 config=num_encoders=0 num_pwmgens=1 num_3pwmgens=0 num_stepgens=5 : Hardware address: 00:60:1b:10:00:50
hm2_eth: discovered 7I80DB-16
hm2/hm2_7i80.0: Smart Serial Firmware Version 43
Board hm2_7i80.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_7i80.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_7i80.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_7i80.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
hm2/hm2_7i80.0: 68 I/O Pins used:
hm2/hm2_7i80.0:     IO Pin 000 (J2-01): StepGen #0, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 001 (J2-14): StepGen #0, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 002 (J2-02): StepGen #1, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 003 (J2-15): StepGen #1, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 004 (J2-03): StepGen #2, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 005 (J2-16): StepGen #2, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 006 (J2-04): StepGen #3, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 007 (J2-17): StepGen #3, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 008 (J2-05): StepGen #4, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 009 (J2-06): StepGen #4, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 010 (J2-07): Smart Serial Interface #0, pin TxData0 (Output)
hm2/hm2_7i80.0:     IO Pin 011 (J2-08): Smart Serial Interface #0, pin RxData0 (Input)
hm2/hm2_7i80.0:     IO Pin 012 (J2-09): IOPort
hm2/hm2_7i80.0:     IO Pin 013 (J2-10): IOPort
hm2/hm2_7i80.0:     IO Pin 014 (J2-11): Encoder #0, pin Index (Input)
hm2/hm2_7i80.0:     IO Pin 015 (J2-12): Encoder #0, pin B (Input)
hm2/hm2_7i80.0:     IO Pin 016 (J2-13): Encoder #0, pin A (Input)
hm2/hm2_7i80.0:     IO Pin 017 (J3-01): StepGen #5, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 018 (J3-14): StepGen #5, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 019 (J3-02): StepGen #6, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 020 (J3-15): StepGen #6, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 021 (J3-03): StepGen #7, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 022 (J3-16): StepGen #7, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 023 (J3-04): StepGen #8, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 024 (J3-17): StepGen #8, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 025 (J3-05): StepGen #9, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 026 (J3-06): StepGen #9, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 027 (J3-07): IOPort
hm2/hm2_7i80.0:     IO Pin 028 (J3-08): IOPort
hm2/hm2_7i80.0:     IO Pin 029 (J3-09): IOPort
hm2/hm2_7i80.0:     IO Pin 030 (J3-10): IOPort
hm2/hm2_7i80.0:     IO Pin 031 (J3-11): Encoder #1, pin Index (Input)
hm2/hm2_7i80.0:     IO Pin 032 (J3-12): Encoder #1, pin B (Input)
hm2/hm2_7i80.0:     IO Pin 033 (J3-13): Encoder #1, pin A (Input)
hm2/hm2_7i80.0:     IO Pin 034 (J4-01): StepGen #10, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 035 (J4-14): StepGen #10, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 036 (J4-02): StepGen #11, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 037 (J4-15): StepGen #11, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 038 (J4-03): StepGen #12, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 039 (J4-16): StepGen #12, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 040 (J4-04): StepGen #13, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 041 (J4-17): StepGen #13, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 042 (J4-05): StepGen #14, pin Direction (Output)
hm2/hm2_7i80.0:     IO Pin 043 (J4-06): StepGen #14, pin Step (Output)
hm2/hm2_7i80.0:     IO Pin 044 (J4-07): IOPort
hm2/hm2_7i80.0:     IO Pin 045 (J4-08): IOPort
hm2/hm2_7i80.0:     IO Pin 046 (J4-09): IOPort
hm2/hm2_7i80.0:     IO Pin 047 (J4-10): IOPort
hm2/hm2_7i80.0:     IO Pin 048 (J4-11): Encoder #2, pin Index (Input)
hm2/hm2_7i80.0:     IO Pin 049 (J4-12): Encoder #2, pin B (Input)
hm2/hm2_7i80.0:     IO Pin 050 (J4-13): Encoder #2, pin A (Input)
hm2/hm2_7i80.0:     IO Pin 051 (J5-01): IOPort
hm2/hm2_7i80.0:     IO Pin 052 (J5-14): IOPort
hm2/hm2_7i80.0:     IO Pin 053 (J5-02): IOPort
hm2/hm2_7i80.0:     IO Pin 054 (J5-15): IOPort
hm2/hm2_7i80.0:     IO Pin 055 (J5-03): IOPort
hm2/hm2_7i80.0:     IO Pin 056 (J5-16): IOPort
hm2/hm2_7i80.0:     IO Pin 057 (J5-04): IOPort
hm2/hm2_7i80.0:     IO Pin 058 (J5-17): IOPort
hm2/hm2_7i80.0:     IO Pin 059 (J5-05): IOPort
hm2/hm2_7i80.0:     IO Pin 060 (J5-06): IOPort
hm2/hm2_7i80.0:     IO Pin 061 (J5-07): IOPort
hm2/hm2_7i80.0:     IO Pin 062 (J5-08): IOPort
hm2/hm2_7i80.0:     IO Pin 063 (J5-09): IOPort
hm2/hm2_7i80.0:     IO Pin 064 (J5-10): IOPort
hm2/hm2_7i80.0:     IO Pin 065 (J5-11): IOPort
hm2/hm2_7i80.0:     IO Pin 066 (J5-12): IOPort
hm2/hm2_7i80.0:     IO Pin 067 (J5-13): IOPort
hm2/hm2_7i80.0: registered
sysctl: cannot stat /proc/sys/net/ipv6/conf/eth0/disable_ipv6: No such file or directory
hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q net.ipv6.conf.eth0.disable_ipv6=1'
Z-Bot ATC : HAL component : started 2019-03-07 16:46:26
Smart Cool:  HAL component: started 2019-03-07 16:46:26
tormachheightgauge: starting
USBIO : HAL component starting 2019-03-07 16:46:26
tormach_mill_mesa.hal:248: parameter or pin 'hm2_7i80.0.gpio.005.is_output' not found
Shutting down and cleaning up LinuxCNC...

Please Log in or Create an account to join the conversation.

More
17 Apr 2019 19:59 - 17 Apr 2019 20:02 #131074 by mrichard
Everybody seems to get this wrong when trying to get PP2 to install. Please read Brianbone's thread from The Industry Arena forum. The key is to make the PP base file point to your .ini file. The following explains this.

I'd figure I would start a new thread for folks trying to upgrade from 1.9.x to PP 2.0 - and here are my thoughts and what I went through:

1. I had to change my motherboard because PP 2.0 didn't like my GPU which was an old GeForce 610 (Old mobo didn't have built in video). I probably could have figured it out, but I am no linux guru and couldn't even see anything on the screen - it was totally garbled. I ended up buying an old Gigabyte GA-41 with built in video, and it worked without any trouble (I wanted to still use my old E2200 dual core pentium chip that I had been using). I doubt most people will need to do this.

2. Please use a separate SSD drive, and unplug your PP 1.9.x drive for obvious reasons. Backup all settings in PP 1.9 "admin settings backup" save to thumb drive. this saves all your offsets and stuff.

3. PP 2.0 installs pretty easily from the thumb drive.

4. To get to the desktop, the Left Shift-Alt keys are supposed to work (it says so in the PP 2.0 operator_login script) but I couldn't get mine to work. So I hit Ctrl-Alt X to get to a terminal prompt. Then type in "mate-panel" This is the new desktop in PP 2.0. gnome is not installed.

5. Next go to system preferences - startup applications and deselect the PathPilot. This prevents the auto start of PP. This is important because now if PP errors out, it shuts down the computer and takes a long time to fix each error.

6. PP 2.0 still runs from the "operator_login" script. If you click that and run "in terminal" like before then you can debug it more easily.

7. When debugging, in PP 1.9.x you could look at the terminal screen to find your errors, now the terminal screen closes, so you have to open the pathpilotlog.txt which is located in the gcode folder in log files folder.

8. Also in PP 2.0, if you edit the tormach_1100-3.ini then PP 2.0 will RE-WRITE it upon any error. So instead I created a "novakon_mill_base.ini" file. Then I edited the "tormach_1100-3_specific.ini" file to point to the novakon_mill_base.ini file. This tricks PP into using the novakon file to build the new ini file in case of an error. So all edits to the ini file should be to the novakon_mill_base file. If anything messes up, you can delete the tormach_1100-3.ini file and PP 2.0 will create a new one from the mill base file.

9. Everything else is pretty similar to before. I posted all my novakon files that should get you going on a Pulsar.

10. To install Dropbox in the MDI window type "Admin dropbox" and it will prompt you to set that up.

11. Restore your old settings by "admin settings restore" and this will import your old tool table and settings.

*Just a side note: I had to re-write the Charge Pump code in the hal file. I am not sure why the old code worked in PP 1.9 but didn't in 2.0. I used PCW_Mesa's example somewhere in linuxcnc forums and now the charge pump works fine **

Attached Files Attached Files
I'd figure I would start a new thread for folks trying to upgrade from 1.9.x to PP 2.0 - and here are my thoughts and what I went through:

1. I had to change my motherboard because PP 2.0 didn't like my GPU which was an old GeForce 610 (Old mobo didn't have built in video). I probably could have figured it out, but I am no linux guru and couldn't even see anything on the screen - it was totally garbled. I ended up buying an old Gigabyte GA-41 with built in video, and it worked without any trouble (I wanted to still use my old E2200 dual core pentium chip that I had been using). I doubt most people will need to do this.

2. Please use a separate SSD drive, and unplug your PP 1.9.x drive for obvious reasons. Backup all settings in PP 1.9 "admin settings backup" save to thumb drive. this saves all your offsets and stuff.

3. PP 2.0 installs pretty easily from the thumb drive.

4. To get to the desktop, the Left Shift-Alt keys are supposed to work (it says so in the PP 2.0 operator_login script) but I couldn't get mine to work. So I hit Ctrl-Alt X to get to a terminal prompt. Then type in "mate-panel" This is the new desktop in PP 2.0. gnome is not installed.

5. Next go to system preferences - startup applications and deselect the PathPilot. This prevents the auto start of PP. This is important because now if PP errors out, it shuts down the computer and takes a long time to fix each error.

6. PP 2.0 still runs from the "operator_login" script. If you click that and run "in terminal" like before then you can debug it more easily.

7. When debugging, in PP 1.9.x you could look at the terminal screen to find your errors, now the terminal screen closes, so you have to open the pathpilotlog.txt which is located in the gcode folder in log files folder.

8. Also in PP 2.0, if you edit the tormach_1100-3.ini then PP 2.0 will RE-WRITE it upon any error. So instead I created a "novakon_mill_base.ini" file. Then I edited the "tormach_1100-3_specific.ini" file to point to the novakon_mill_base.ini file. This tricks PP into using the novakon file to build the new ini file in case of an error. So all edits to the ini file should be to the novakon_mill_base file. If anything messes up, you can delete the tormach_1100-3.ini file and PP 2.0 will create a new one from the mill base file.

9. Everything else is pretty similar to before. I posted all my novakon files that should get you going on a Pulsar.

10. To install Dropbox in the MDI window type "Admin dropbox" and it will prompt you to set that up.

11. Restore your old settings by "admin settings restore" and this will import your old tool table and settings.

*Just a side note: I had to re-write the Charge Pump code in the hal file. I am not sure why the old code worked in PP 1.9 but didn't in 2.0. I used PCW_Mesa's example somewhere in linuxcnc forums and now the charge pump works fine **
File Type: txt novakon_mill_base.ini.txt (7.5 KB, 3 views)
File Type: txt novakon.hal.txt (23.0 KB, 3 views)
File Type: txt postgui_tormach_mill.hal.txt (6.4 KB, 3 views)
File Type: txt tormach_1100-3_specific.ini.txt (150 Bytes, 3 views)
Last edit: 17 Apr 2019 20:02 by mrichard.

Please Log in or Create an account to join the conversation.

More
10 Jul 2019 21:09 #139022 by Derek240
Hi Mike

Did you ever get the 7I80DB working with PathPilot?

Please Log in or Create an account to join the conversation.

Moderators: cncbasher
Time to create page: 0.120 seconds
Powered by Kunena Forum