Author Topic: CB V1.0 Message Window after creating G-Code  (Read 5295 times)

Offline airnocker

  • CNC Jedi
  • *****
  • Posts: 656
    • View Profile
CB V1.0 Message Window after creating G-Code
« on: January 29, 2021, 19:17:57 pm »
I've always known one can see how long a MOP operation can take after creating it's G-code and looking in the Message Window at the bottom of the CB screen.  And, I've always scanned the Message Window for any errors but never paid much attention to these lines except for the time to complete.

Recently, for the first time, I've created the G-Code for the Machining Part instead of each individual MOP associated with a Part. In the attached screenshots, one shows my part with its underlying MOPs and there description, the other shows the messages relating to creating that G-code.

I do not see any direct association to each message line to their respective MOP descriptions other than their being a profile or pocket.

My question is: Why do these messages appear somewhat out of sequence, where the "finish" is listed before the "rough" descriptor?

I didn't see anything in CB's Help to explain this.

Thanks in advance,
airnocker

Everything depends on everything else

Offline dh42

  • Administrator
  • CNC Jedi
  • *****
  • Posts: 7566
    • View Profile
    • Cambam V1.0 French Doc
Re: CB V1.0 Message Window after creating G-Code
« Reply #1 on: January 29, 2021, 19:31:03 pm »
Hello

Quote
My question is: Why do these messages appear somewhat out of sequence, where the "finish" is listed before the "rough" descriptor?

It's because the use of multithreading, each mop is assigned to an individual thread, so, as example, if you've a 8 thread CPU, 8 mop are calculated at a same time ; and the log is written immediately after a thread as finished is computation, so the order is depending of the time needed to compute a mop, that depend of the complexity of the job.

++
David

Offline airnocker

  • CNC Jedi
  • *****
  • Posts: 656
    • View Profile
Re: CB V1.0 Message Window after creating G-Code
« Reply #2 on: January 29, 2021, 19:35:34 pm »
David, many thanks for that explanation. I am relieved to know that it does not affect the order of MOP operations.
airnocker

Everything depends on everything else