Bill are u using an external usb dvd to install PP? That may be an issue if not using a Sata drive?
Thanks Guys;
I did review the link addressing motherboards that work with Pathpilot and my Gigabyte board "is" listed as compatible. That's one thing that keeps me banging away to find an answer. On item addressed in the thread had to do with the listing of the "H6" type boards and the way the USB is embedded in the chip set. Apparently it has problems dropping packets of information during communication with USB type devices. So, as suggested in the thread I ordered a usb interface card to plug into the system and use for interfacing all the peripherals required for communication. The new board should be here tomorrow so I'll test first chance and report back!
If not, I most likely will purchase the system Leeway identified and put this whole issue to bed!
Many thanks for the help folks.
Bill
billyjack
Helicopter def. = Bunch of spare parts flying in close formation! USAF 1974 ;>)
Bill are u using an external usb dvd to install PP? That may be an issue if not using a Sata drive?
I saw somewhere that someone figured out how to make a bootable USB stick copy of Path Pilot.
I'll look for that and post the link.
Post number 6 here.
http://www.cnczone.com/forums/tormac...6-tormach.html
Lee
That would be cool. May solve the issues w the uuid errors
Thanks Guys;
I'll give a try prior to installing the new usb card that should be waiting on me today after work!
Bill
billyjack
Helicopter def. = Bunch of spare parts flying in close formation! USAF 1974 ;>)
Ok Folks;
This will be my last update on this thread. I'll start a new thread in the future and may cut and paste part of this for future reference.
This weekend I tried the following;
Installed a new card that provided new usb inputs (4 each).
Disconnected all peripherals from the existing motherboard and routed them through the new device.
Rebooted and - Same Message. No Joy!
I was using an external DVD drive as discussed by Brain so I created a flash drive from the disk and attempted to install PP from it. No Joy.
I took a couple of days off to wrap my head around all that was attempted to assure that I'm not missing anything.
Next - New motherboard to be installed in a different thread as mentioned above.
First, a couple of weeks off to rest my head (lol).
Thanks Guys for all the suggestions and help!
Bill
billyjack
Helicopter def. = Bunch of spare parts flying in close formation! USAF 1974 ;>)
Well.......I think you pinpointed the source of the problem. At least I am hoping that is what this all means.
Good luck with it and I'll keep watching your progress and rooting for Bill to win out over technology in the end.
Lee
Hello everyone, I just received my Torus Pro, and instead of setting it up and learning Mach3, then relearning Path Pilot, I just decided to go ahead and install Path Pilot from the get go. I followed the instructions on the first page, PathPilot installed fine on a new SSD drive, and it flashed my 6i25 just fine. I then copied the 3 files over to the listed directories (although there was 5 in the zip file). After rebooting, it flashes the card as expected. Once that is done, it never advances to any type of window manager, so after about 10 minutes, I open up a terminal and halt it via the command line. Upon reboot, it pops up an error "Machine Control Software Eperienced an Error" and prompts me to install a Path Pilot update. I looked in the messages log, there were definitely entries in their for the 5i25 but nothing that appeared sinister, or otherwise made me say a-ha! I've tried this a couple of times to make sure it wasn't a process error or some other kind of flukey thing. I have tried on the original 1.9.3 iso that I have, and I also tried after installing the 1.9.13 software update first. The system has a 5.2 BOB if that matters. I'm comfortable working in Linux, if anyone has anything I should try taking a look at let me know. Is there any chance that the jumpers on the 6i25 are set wrong? Edit: I just verified that all the jumpers were in the default locations per the 6i25 manual. It flashes just fine, and I haven't changed anything since taking it out of the ESD bag and installing it. I did take a peak at the BIOS, and nothing there looked out of place. I shut of HD Audio, but otherwise there wasn't much to fiddle with.
Last edited by WTFover; 12-06-2017 at 06:17 PM.
Hey WT;
I have been attempting to install PP on my pro without any success. It just does not want to install as described here and on other threads. On one of the other Tormach threads, there is a mention of a new issue of PP labeled as PP2.0 and is suppose to be an enhanced versions. Also, it addresses issues with installation and USB ports which I think is my problem. So, I'm on hold until version 2.0 is issues and (hopefully) Tormach will sell me the upgrade for use on my Novakon. I'm literally hundreds of $$ into this conversion and am still running Mach.
Good luck and I'll keep watching to see what you come up with.
Bill
billyjack
Helicopter def. = Bunch of spare parts flying in close formation! USAF 1974 ;>)
If the 6I25 card gets flashed that pretty much guarantees that its OK
I suspect that to debug these issues you will have to find out the actual error message from Pathpilot startup
have you tried looking at the kernel log (with dmesg) after attempting to start PathPilot?
Can you launch PathPilot from the command line? that may also yield some clues
I think the chief issue is that you are flying blind, where the smallest error say in the hal file only gets a generic "Oww" error
without any hint of what actually is wrong, This make sense for Tormach where the hardware is all standard but is really a pain
with different hardware/firmware
There's a great video on YouTube that shows you how to make a bootable flash drive with a piece of software called R-Drive If you have the iso file. That's what I did, after dicking around with things like Rufus and Linux USB creator without much success. It worked like a champ. I suggest giving that a shot.
Jason --CNC Newbie--
Jason --CNC Newbie--
WT;
I've already tried the r-drive/flash drive approach. Didn't work for me! I do have a question for the experts though. If I change to a new motherboard and use the processor from the original, will it still be compatible with the original windows on the Novakon SSD which I am not making changes to? If memory serves me, back in yesteryears windows married itself to the motherboard/bios of the computer it is installed on. I want the ability to switch back to the original novakon configuration if troubles still haunt me!
Thanks.
Bill
billyjack
Helicopter def. = Bunch of spare parts flying in close formation! USAF 1974 ;>)
I'll echo what PCW said above. If you open a terminal window and run PP from the command line you will get a lot more information as to what is happening during the load process. That always got me on the right path.
PCW_MESA I had some similar flukiness with the firmware that you made for me. I never really got to the bottom of what the problem was cause it went away. Initially I had the exact same problems where it would boot and tell me that I needed to install a new version of PP. I had to reflash about 3 times then it magically worked. I believe that KVOM had exactly the same prob. Not sure if you could re-create the firmware and let me do a binary diff.
Also, I would check to make sure that the flash actually worked. I'm not at the mill, but I think the command to check the pins is this. (Brian or PCW, please correct me if im wrong)
sudo mesaflash --device 5i25 --readhmid
################################################## ###############################################
# 5i25 Pin out for NOVAKON Torus bit file
#IO Connections for P3
#Pin# Mill Fxn I/O Pri. func Sec. func Chan Pin func Pin Dir
# 1 X step 0 IOPort StepGen 0 Step (Out)
#14 Spindle Dir 1 IOPort PWMGen 0 Dir (Out)
# 2 X Dir 2 IOPort StepGen 0 Dir (Out)
#15 ProbeIn(act low) 3 IOPort None
# 3 Y Step 4 IOPort StepGen 1 Step (Out)
#16 Spindle Step 5 IOPort PWMGen 0 PWM (Out)
# 4 Y Dir 6 IOPort StepGen 1 Dir (Out)
#17 Charge Pump 7 IOPort StepGen 4 Step (Out)
# 5 Z Step 8 IOPort StepGen 2 Step (Out)
# 6 Z Dir 9 IOPort StepGen 2 Dir (Out)
# 7 A Step 10 IOPort StepGen 3 Step (Out)
# 8 A Dir 11 IOPort StepGen 3 Dir (Out)
# 9 Flood Relay 12 IOPort None
#10 E-Stop In 13 IOPort None
#11 All Limit Sw 14 IOPort None
#12 ?spindle home 15 IOPort None
#13 Timing/Touch pl 16 IOPort None
If it doesnt output something with the same pin config, specifically the PWMgen part, you likely dont have a flash that worked.
Scott...
Last edited by sagreen; 12-07-2017 at 06:29 PM.
Instructional Videos for CNC Guitar Building
http://www.rmgvideos.com
You do need to power cycle (or use the mesaflash --reload option)
before the FPGA will reload itself from the flash memory
So, just a quick update. starting the operator login script from the command line gave me something to chase. Here is the error message:
postgui_tormach_mill.hal:6: Pin 'zbotatc.config-number' does not exist
Error: something failed running halcmd on 'postgui_tormach_mill.hal'
Shutting down and cleaning up LinuxCNC...
Not exactly sure where to go from here. I'm going to keep digging but if anyone has any ideas, let me know.
Jason --CNC Newbie--
That is getting some where. That is saying that there is an error on line 6 of 'postgui_tormach_mill.hal'. That file is in the same directory as the config files if I recall.
I'm going to take a wild guess and say that you are using a newer version of PathPilot and the postgui_tormach_mill.hal is looking for a variable that doesnt exist in the files that you got from me. i.e. tormach added this to the config between our versions. Pretty easy to fix, you just have to track down where that is set in the original distribution files and copy it over to where it may need to be in the files you got from my install.
Make sense?
Scott...
Instructional Videos for CNC Guitar Building
http://www.rmgvideos.com
So for Posterity's sake, and to save someone else some grief along the way: I initially had attempted this on 1.9.3 which is pretty old, but that is what was on the iso they sent me. It was too old in fact, as I was commenting out lines in the postgui hal it would complain about a module missing in rtlib. So I figured the version that you were on was somewhere higher than that, but not the latest, so I did the upgrade to 1.9.12 and started there. After the upgrade, the new module that was absent previously did appear so I started commenting out lines in the postgui hal file. I can now successfully boot in to PP, after commenting the following lines below. Overall the 4 things it appears to be complaining about are the tool changer, digital height gauge, USBIO and Smart Cool. Does anyone see anything important in the list below that I need to put back or work on sorting, otherwise it seems to be working now. I am going to go reinstall in the mill later today and see how it behaves. Thanks to everyone for all the help!!!
Edit: I also just did the update from 1.9.12 to 1.9.13 and applied the same fixes to the postgui hal file with complete success.
#net config zbotatc.config-number
#net config zbotschnozz.config-number
# digital height gauge
#net thg-net-height tormachheightgauge.net-height => tormach.hg-height
#net thg-zero-offset tormachheightgauge.zero-offset => tormach.hg-zero-offset
#net thg-button-pressed tormachheightgauge.button-pressed => tormach.hg-button-pressed
#net thg-button-changed tormachheightgauge.button-changed => tormach.hg-button-changed
#net thg-mm-mode tormachheightgauge.mm-mode => tormach.hg-mm-mode
#net thg-set-zero-offset tormachheightgauge.set-zero-offset => tormach.hg-set-zero-offset
#net thg-present tormachheightgauge.present => tormach.hg-present
#net thg-debug tormachheightgauge.debug => tormach.hg-debug
#net thg-enable tormachheightgauge.enable => tormach.hg-enable
#net thg-has-zero-button tormachheightgauge.has-zero-button => tormach.hg-has-zero-button
# Z-Bot ATC Pins to motion contoller DIO , AIO stuff
#command and control
#net atc-request-ngc motion.analog-out-04 => zbotatc.0.ain.0.request
#net atc-data-ngc motion.analog-out-05 => zbotatc.0.ain.1.request_data
#net atc-status motion.digital-in-16 <= zbotatc.0.dout.5.exec_status
#net atc-status tormach.atc-hal-busy <= zbotatc.0.dout.5.exec_status
#net atc-retcode motion.analog-in-05 <= zbotatc.0.aout.0.request_rc
#net atc-retcode tormach.atc-hal-return <= zbotatc.0.aout.0.request_rc
#hardware status variables
#net atc_tray-in motion.digital-in-17 <= zbotatc.0.dout.0.tray_status
#net atc_tray-in tormach.atc-tray-status <= zbotatc.0.dout.0.tray_status
#net atc-vfd motion.digital-in-18 <= zbotatc.0.dout.1.vfd_status
#net atc-vfd tormach.atc-vfd-status <= zbotatc.0.dout.1.vfd_status
#net atc-draw-bar motion.digital-in-19 <= zbotatc.0.dout.2.draw_status
#net atc-draw-bar tormach.atc-draw-status <= zbotatc.0.dout.2.draw_status
#net atc-pressure motion.digital-in-20 <= zbotatc.0.dout.3.pressure_status
#net atc-pressure tormach.atc-pressure-status <= zbotatc.0.dout.3.pressure_status
#net atc-slot motion.analog-in-06 <= zbotatc.0.aout.1.tray_position
#net atc-slot tormach.atc-tray-position <= zbotatc.0.aout.1.tray_position
#net atc-tray-tools tormach.atc-tools-in-tray <= zbotatc.atc-tools-in-tray
#net atc-vfd-rpm zbotatc.vfd-rpm
#hardware status variables
#net atc-device motion.digital-in-21 <= zbotatc.0.dout.4.device_status
#net atc-device tormach.atc-device-status <= zbotatc.0.dout.4.device_status
#net atc-loop-back zbotatc.0.aout.2.request_ack => motion.analog-in-07
# USBIO
#net usbio-enabled tormach.usbio-enabled => usbio.enabled
#net dig-out-0 tormach.usbio-output-0
#net dig-out-1 tormach.usbio-output-1
#net dig-out-2 tormach.usbio-output-2
#net dig-out-3 tormach.usbio-output-3
#net dig-in-0 tormach.usbio-input-0
#net dig-in-1 tormach.usbio-input-1
#net dig-in-2 tormach.usbio-input-2
#net dig-in-3 tormach.usbio-input-3
#Smart Cool keyboard override pins
#net sc_override tormach.smart-cool-man-auto => zbotschnozz.man-auto
#net sc_up tormach.smart-cool-up => zbotschnozz.cool-up
#net sc_down tormach.smart-cool-down => zbotschnozz.cool-down
Last edited by WTFover; 12-08-2017 at 01:43 PM.
Jason --CNC Newbie--
No just comment those out - you can always come back to them once you get things running.