cmcgrath5035

Forum Replies Created

Viewing 15 posts - 1,756 through 1,770 (of 1,771 total)
1 2 3 … 117 118 119
  • Author
    Posts
  • October 11, 2013 at 11:02 am in reply to: Errors running test GCode woth tgFX and TinyG #4746
    cmcgrath5035
    Moderator

    Riley – Ignore this for the moment. I realized that the parameters posted at 8:28 am above were defective. I am working on a better set, will repost with updated results.

    October 11, 2013 at 8:28 am in reply to: Errors running test GCode woth tgFX and TinyG #4744
    cmcgrath5035
    Moderator

    A Putty logfile is here in my dropbox

    Seems better than trying to screen scrape from here using a code block.

    The log window in tgFX seems to be always double spaced (row of output, then blank row), is that intentional?

    Is it possible to capture a logfile (write to log during session) from tgFX?

    October 10, 2013 at 10:32 pm in reply to: Install script error (maybe?) #4742
    cmcgrath5035
    Moderator

    I just verified that build 2072 32bit from Dropbox also loads and runs under Win7-64bit as well,. So it runs on both WinXP_64bit and Win7_64bit.

    October 10, 2013 at 10:26 pm in reply to: Linux Builds – some feedback #4741
    cmcgrath5035
    Moderator

    OSX – I looked again and can’t figure out why I thought it did load to /opt/tgfx. I must have been digging in the wrong archive (the .deb).

    Fix? I didn’t expect you too, just wanted something for you to use when you run out of sheep to count at night. 🙂

    libglass.so – I understand. It is looking for javafx in /opt/tgfx/amd64, which does not exist.

    October 10, 2013 at 10:06 pm in reply to: Install script error (maybe?) #4740
    cmcgrath5035
    Moderator

    The first time I tried it did not, but build 2072 did.

    I am thinking that perhaps the first time the serial link was hung up due to prior aborts, etc.

    October 10, 2013 at 9:04 am in reply to: Errors running test GCode woth tgFX and TinyG #4730
    cmcgrath5035
    Moderator

    Riley
    Info requested is at top of first post, repeated here:
    TinyG (hw V7, FW 0.96)
    tgFX is “tgfx_windows-x32 v.95 – build 2072.exe” from dropbox.
    The GCode file is from ShapeOko site

    I’ll try to figure out how to attach it, but at the moment do not see how

    I have run it now on two separate machines
    1. WinXP 32 bit Virtual Machine (VBox on openSUSE 12.3)
    2. Win7 32 bit Virtual Machine (VBox on openSUSE 12.3)

    ((Note that in another post I reported the dropbox 64 bit tgFX build 2072 does not install properly on my 64 bit machines))

    The results are similar on both, mangled S, h and a characters then OK for the rest of peOko. Results slightly different each run. I’ll also note that I do occasionally get a ‘clean’ run of the job.

    Observation: I opened Windows Task Manager (ShiftCtl-Esc) and watched as the GCode is executed. CPU pegged at 98% or more for the entire run. Phys Memory runs around 50%. Something in the java implementation seems terribly inefficient or slow to “get started”? Not at all clear to me why Sha would be more difficult to process than peOko.

    I’d be happy to run some test GCode you might have to compare.

    I would expect you to question the VMs I am running. I am not sure what metric would be helpful, but will comment that both machines (one a desktop, one a laptop) both provide the ‘spiffiest’ response I have ever experienced with Windows.

    The only native Win7 machine I have is 64 bit. I’ll try to run the 32 bit on that, but as I said I believe there is something wrong with the 64 bit build 2072 package on dropbox.

    • This reply was modified 11 years, 2 months ago by cmcgrath5035.
    October 9, 2013 at 10:10 am in reply to: Errors running test GCode woth tgFX and TinyG #4725
    cmcgrath5035
    Moderator

    To speed the discussion, I’ll add that my errors look similar to those posted by LTMNO in this ShapeOko post

    although in my case “h” and “a” get somewhat mangled as well.

    I interpret from the discussion there that these are somewhat known bugs in tgFX and my assumption is that they still exist in tgFX 32bit build 2072.

    October 4, 2013 at 9:11 am in reply to: First steps? #4694
    cmcgrath5035
    Moderator

    Alden – I just looked at the above wiki page

    And I am confused.
    a. Motor 4 seems mapped to Z axis, not Y, ….?
    b. Polarity – seems $4po should be 1 OR there should be an explicit statement that the wiring is physically reversed

    September 30, 2013 at 6:48 am in reply to: TinyG and tgFX – need some help/suggestions #4652
    cmcgrath5035
    Moderator

    I think you will find the 2077 Build from

    works as well, it is 64 bit “Experimental”

    I have WinXP32 and WinXP 64 machines. Later I will try the 32 bit app (Build 2072) on 64 bit machine, it does work on the 32 bit machine.

    September 29, 2013 at 4:03 pm in reply to: TinyG and tgFX – need some help/suggestions #4648
    cmcgrath5035
    Moderator

    jcl5m1 – Which 64 bit version did your try? Build 2077 from Experimental did work for me on a WinXP64.

    Are you running the 32 bit app on a 64 bit machine or 32 bit machine?
    What Win? (XP, 7, 8,…)?

    Riley – this prompts me to ask; why you are maintaining both 32 and 64 bit apps – since (I believe) all (?) 64 bit machines will run 32 bit apps?

    September 26, 2013 at 8:52 am in reply to: TinyG and tgFX – need some help/suggestions #4615
    cmcgrath5035
    Moderator

    OK, my TinG V7 has Firmware 0.96 Build 380.05
    I loaded tgfx_windows-x32 v .95-build 2072 (from Dropbox above) into my WinXP(32) VM (VBox on openSUSE 12.3).

    I confirm that this combination works similarly to the x64 build previously tested (above in thread). THANKS!

    Riley – an additional observation w.r.t. Task Manager/Program not shutting down properly

    A. After loading the tgFX software, I powered up my TinyG and started the txFX software. I went to select my COM3 port on the txFX page, nothing showed and I realized that I had not connected that USB port to the VM. I made the connection, but COM3 not visible so I shut down tgFX.
    txFX disappeared from Windows Task Manager.
    B. I restarted tgFX, COM3 was now selectable and txFX connected to TinyG.
    I could view parameters in tgFX windows and I could interact with TinyG via the cli interface at bottom of tgFX window. I then closed the tgFX window with the upper right corner “X”. The txFX window closed but process tgFX.exe remained active in Task Manager.
    C. I killed the tgFX.exe process, then restarted it. Connected to COM3, communicated with TinyG, all was good.
    I then “Disconnected” from COM3 on the txFX window, then closed the window with upper right “X” and see that txFX.exe disappears from Task Manager.

    I can only assume that you would be able to execute a disconnect from all COMx before shutting down the window, but have never programmed such myself so leave this meaty bone for you to chew on.

    September 22, 2013 at 9:19 am in reply to: Mysterious Serial communication in custom software #4567
    cmcgrath5035
    Moderator

    I can’t help directly, but you mention application handling XON/XOFF.
    User Makerboost made this comment relative to a post I had made
    Also, I understand that tgFX doesn’t use XON/XOFF like a normal terminal client, but controls TinyG differently. This has caused my TinyG’s $ex value to revert to 0 every time I start up tgFX.

    September 21, 2013 at 6:42 pm in reply to: TinyG and tgFX – need some help/suggestions #4565
    cmcgrath5035
    Moderator

    OOps, just noticed type in last post, it’s Build 2077 that properly runs as 64 bit.

    HOWEVER, I still see the tgfx.exe process active in task manager after closing the window. Killing it in Task Manager allows a restart.

    September 21, 2013 at 6:04 pm in reply to: TinyG and tgFX – need some help/suggestions #4563
    cmcgrath5035
    Moderator

    OK, after reading another thread I downloaded tgfx_windows-x64 v.95-build 2077.exe from Experimental and IT WORKS!!

    More testing and familiarization ahead.

    Also, I note that this Build 2012 is properly identified by WinXP_64 as a 64 bit application and installed in C:\Program Files\tgfx and runs as 64 bit per windows Task Manager.
    I am not sure why build 2012 did not.

    September 21, 2013 at 11:51 am in reply to: TinyG and tgFX – need some help/suggestions #4562
    cmcgrath5035
    Moderator

    Interesting, user InPhase seemed to have good luck with a v8 TinyG and 0.96, but only with 64 bit computers.

    My tinyG is v7.

    Did you see the note about setting the hardware version properly with the new FW? Apparently there is a HW difference between v6(and earlier, I guess) and v7 and v8. See Alden’s comment on the top post where the URL to current FW is presented.

    Perhaps Alden or Riley can better explain what flow control settings are required

  • Author
    Posts
Viewing 15 posts - 1,756 through 1,770 (of 1,771 total)
1 2 3 … 117 118 119