MADCAM broken with latest version


Results 1 to 9 of 9

Thread: MADCAM broken with latest version

  1. #1
    Member
    Join Date
    Apr 2018
    Location
    United States
    Posts
    14
    Downloads
    0
    Uploads
    0

    Default MADCAM broken with latest version

    With the latest version of MADCAM I can no longer postprocess toolpaths.. I receive the error message: Access Violation error raised with message (than a bunch of numbers). I have never received this error message before. Can I revert to a previous working version?

    // JRS_CNC

    Similar Threads:


  2. #2
    Community Moderator
    Join Date
    Mar 2004
    Location
    Sweden
    Posts
    1661
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    yes you can, if you have the installation file.
    Before you try that, try to reinstall the latest release.



  3. #3
    Member
    Join Date
    Apr 2018
    Location
    United States
    Posts
    14
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    Thanks for the information. Turns out I changed the screen settings in WIN10 from picture/transparent to solid color/not transparent. With the latter setting I had the MADCAM problem I described. Changing back to the default settings MADCAM works fine, so false alarm, I guess. Strange the screen settings changed MADCAMs behavior but sometimes computers are strange.

    JRS_CNC



  4. #4
    Member
    Join Date
    Mar 2013
    Location
    USA
    Posts
    10
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    Quote Originally Posted by JRS_CNC View Post
    Thanks for the information. Turns out I changed the screen settings in WIN10 from picture/transparent to solid color/not transparent. With the latter setting I had the MADCAM problem I described. Changing back to the default settings MADCAM works fine, so false alarm, I guess. Strange the screen settings changed MADCAMs behavior but sometimes computers are strange.

    JRS_CNC


    I'm also having this issue. Windows 10, Rhino 6. How did you fix this?



  5. #5
    Member
    Join Date
    Mar 2013
    Location
    USA
    Posts
    10
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    I worked this out. For me madcam was pointing to older machine definitions from earlier versions of madcam in %User%\Documents\MadCAM.....

    I repointed it to %User%\AppData\Roaming\5XCNC\.... and the access violation is now gone.


    Thanks,
    Curt



  6. #6
    Member
    Join Date
    Mar 2013
    Location
    USA
    Posts
    10
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    After more working this is still cropping up and causing some pain.

    The error:

    EAccessViolation error raised, with message : Access violation at address 0000000000000041379B in module 'madCAM6.dll'. Read of address FFFFFFFFFFFFFFF.

    The read of address FFFFFFFFFFFFFFF is the problem. Somewhere madcam is getting a bad address. I suspect an uninitialized variable issue.



    I have tracked it down the the postprocessor file.When it happens, if I switch to another postprocessorit works. Then if I switch back it doesn't work. If I do that a few times then the original postprocessor works. It doesn't seem to depend upon which postprocessor it is.

    I suspect an uninitialized variable somewhere, which after switching back and forth eventually gets initialized.



  7. #7
    Member
    Join Date
    Feb 2018
    Location
    Netherlands
    Posts
    7
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    Quote Originally Posted by curtdutt View Post
    After more working this is still cropping up and causing some pain.

    The error:

    EAccessViolation error raised, with message : Access violation at address 0000000000000041379B in module 'madCAM6.dll'. Read of address FFFFFFFFFFFFFFF.

    The read of address FFFFFFFFFFFFFFF is the problem. Somewhere madcam is getting a bad address. I suspect an uninitialized variable issue.



    I have tracked it down the the postprocessor file.When it happens, if I switch to another postprocessorit works. Then if I switch back it doesn't work. If I do that a few times then the original postprocessor works. It doesn't seem to depend upon which postprocessor it is.

    I suspect an uninitialized variable somewhere, which after switching back and forth eventually gets initialized.

    I can reproduce this EAccessViolation :

    error will come with post here
    under:

    N"lnbr" (Nc generated on : "datetime")
    N"lnbr" (Documentname "documentname")
    N"lnbr" "documentname"
    N"lnbr" (Tool Path Profile "method")
    N"lnbr" Tool Number = "toolnr")
    N"lnbr" (Tool Offset Number = "tooloffsetnbr")


    in the third line there is written "document name" and not (document name)

    when I place the () around the text the error is disappeared.


    maybe there is a line likes this in your post?



  8. #8
    Member
    Join Date
    Feb 2006
    Location
    Sweden
    Posts
    153
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    This problem has been solved with SR 14, February 25.

    Thanks,
    Joakim



  9. #9
    Member
    Join Date
    Mar 2013
    Location
    USA
    Posts
    10
    Downloads
    0
    Uploads
    0

    Default Re: MADCAM broken with latest version

    I just verified it that this release solved my problem

    Thanks Joakim!

    -Curt



Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


About CNCzone.com

    We are the largest and most active discussion forum for manufacturing industry. The site is 100% free to join and use, so join today!

Follow us on


Our Brands

MADCAM broken with latest version

MADCAM broken with latest version

MADCAM broken with latest version