CNC troubles after update

Home › Forums › TinyG › TinyG Support › CNC troubles after update

Tagged: , , ,

Viewing 7 posts - 31 through 37 (of 37 total)
1 2 3
  • Author
    Posts
  • November 17, 2015 at 4:36 pm #8953
    Derrick
    Member

    Anything new???

    November 17, 2015 at 4:41 pm #8955
    alden
    Member

    I have a version that corrects the issue, but am still testing. I’ll post a test version later. Thanks for your patience.

    November 18, 2015 at 5:46 am #8956
    alden
    Member

    Here’s a hex for firmware build 441.03 in the edge branch. It should address your issue. I am not ready to release this to master yet without a lot more testing. If you run into any problems please let us know.

    https://www.dropbox.com/s/3w4op9cr8qxrzxl/tinyg-edge-441.03.hex?dl=0

    November 20, 2015 at 7:03 pm #8960
    Derrick
    Member

    Quick question before I update the firmware… is there any way to save the configuration of my machine?

    ie… steps per rev, axis motors/directions/speeds?

    I have had to go through and manually reconfigure these one by one a number of times now through this process and I really don’t want to do it again. Is there a faster/easier way?

    November 22, 2015 at 7:35 am #8961
    cmcgrath5035
    Moderator

    Have a read thru this wiki item:

    Recognize that these procedures are driven by the results of a $$ command.

    Always check the parameter list as new FW builds are installed – sometimes new parameters are introduced(more so with tinyG2 than tinyG)
    The restore from archive will replace parameters on the list with same $name, will do nothing for $newnames.

    By the way, since you run often in inch mode: put your machine in mm mode before launching the backup option, inch mode will fail. Also make sure parameter $tv=1.

    December 6, 2015 at 11:33 am #9083
    Derrick
    Member

    OK, I wanted to tag up now that I have ran a number of parts with the new firmware. Everything is cutting as it should, small holes, arcs, and large holes and arcs too. I am however still having issues with jogging the machine with both keyboard commands as well as mouse commands too.

    The machine registers and commands sometimes… and sometimes it does not. It also sometimes stores the move commands and then sends them all at once. This is a “new feature” that started happening since I updated the firmware form my original posting. I can see the commands being sent in the serial port console, they however don’t make it to the TinyG. This also occurs when typing in commands, sometimes it takes them, other times I have to reenter then commands for them to be taken. Have you experienced this?

    I am running JSON Server Version 1.83, I don’t think that this has been stated to this point, not sure if it matters. Is there a setting that I may have messed up? Maybe a priority or machine access setting that is causing this problem?

    December 6, 2015 at 1:45 pm #9084
    cmcgrath5035
    Moderator

    I would try the updated SPJS 1.86.
    Overall, 1.86 is much more cpu efficient and targeted some issues with ‘stalling’, but not necessarily as you describe; more often the issue was with very long Gcode runs (hours long)..

    I would suggest you gather a before and after benchmark as to CPU utilization for the serial-port-json-server application. Method depends on OS.

  • Author
    Posts
Viewing 7 posts - 31 through 37 (of 37 total)
1 2 3
  • You must be logged in to reply to this topic.