MADCAM broken with latest version

[JRS_CNC]

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:

• Problem- madCAM crashing Rhino5 after latest Windows 10 update
• Problem- Latest madCAM making 4 Axis Drive Surface
• Will latest Madcam work with Rhino 4.0
• Madcam pocketing and profiling bug in latest update?
• madcam locked up after latest release DL

[svenakela]

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

[JRS_CNC]

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

[curtdutt]

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?

[curtdutt]

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

[curtdutt]

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.

[JerryKosters]

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?

[JOM]

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

Thanks,
Joakim

[curtdutt]

I just verified it that this release solved my problem

Thanks Joakim!

-Curt