584,833 active members*
5,293 visitors online*
Register for free
Login
IndustryArena Forum > CAM Software > MadCAM > MADCAM broken with latest version
Results 1 to 9 of 9
  1. #1
    Join Date
    Apr 2018
    Posts
    14

    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

  2. #2
    Join Date
    Mar 2004
    Posts
    1661

    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
    Join Date
    Apr 2018
    Posts
    14

    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
    Join Date
    Mar 2013
    Posts
    10

    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
    Join Date
    Mar 2013
    Posts
    10

    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
    Join Date
    Mar 2013
    Posts
    10

    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
    Join Date
    Feb 2018
    Posts
    7

    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
    Join Date
    Feb 2006
    Posts
    183

    Re: MADCAM broken with latest version

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

    Thanks,
    Joakim

  9. #9
    Join Date
    Mar 2013
    Posts
    10

    Re: MADCAM broken with latest version

    I just verified it that this release solved my problem

    Thanks Joakim!

    -Curt

Similar Threads

  1. Replies: 18
    Last Post: 08-03-2017, 11:53 AM
  2. Latest madCAM making 4 Axis Drive Surface
    By Mauri R in forum MadCAM
    Replies: 0
    Last Post: 05-21-2017, 04:29 AM
  3. Will latest Madcam work with Rhino 4.0
    By brian257 in forum MadCAM
    Replies: 1
    Last Post: 03-31-2015, 09:37 PM
  4. Replies: 5
    Last Post: 03-27-2014, 08:13 PM
  5. madcam locked up after latest release DL
    By williamsmotower in forum MadCAM
    Replies: 10
    Last Post: 12-04-2011, 12:45 PM

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
  •