Am i the only one thats impressed by the way work visual always manages to keep exactly 10 log files stored ?
Never 11, always 10.
THAT part of dnWV works every time.
Am i the only one thats impressed by the way work visual always manages to keep exactly 10 log files stored ?
Never 11, always 10.
THAT part of dnWV works every time.
I think that is because of the ring buffer cycle configured.
They do it often to avoid filling disk with error reports.
Normally such ring buffers numbers can be changed based on user needs.
KUKA should be the best place to get further info.
Heh. Many years ago (KRC1As), I had something happen where an entire line of robots began quitting with blue-screen Windows errors and failing to boot properly. Took me forever to track down what was happening: an error log file was growing at an incredible rate (several MB/hour) and eventually filling all space on the C: drive. Deleting the file fixed the problem for a few hours, but I could watch the files growing at warp speed.
Took me another several hours to determine the root cause. A plant electrician had plugged two port on the network hub (not switch) into each other, generating a storm of network errors. It didn't break the network, but it did trigger the crazy growth in those log files.
So, yeah -- no log file system should be allowed to grow without limit. Limiting a log system to a certain number of files, and a certain number of lines per file, in a FIFO type arrangement, is pretty standard.
I think that is because of the ring buffer cycle configured.
They do it often to avoid filling disk with error reports.
Normally such ring buffers numbers can be changed based on user needs.
KUKA should be the best place to get further info.
Possibly. Or to camouflage that dnVW chrashes about 25 times a day, if you actually use it to go online.
I'm impressed that it's possible to make a stable robot program working with it.
what is dnVW and what logs you are talking about?
and why is it impressive that someone chose base 10 to do something when base 10 is what everyone learns since childhood? sure one could choose to change this to 9 or 17 if one needed but unless there is a very specific reason for that - why bother?
btw. i am speaking from experience. i was making multithreading applications that did tons of things in real time. and once you push things to the extremes everything needs attention to detail. then logging is no longer just a matter of opening file, appending line and closing the file. choosing how to handle volumes of data becomes an issue. working with smaller files is faster so splitting things can make sense. and using ring buffer to write one of N files is not unheard of. and making N value change dynamically would make things more complex and slower.
what is dnVW and what logs you are talking about?
and why is it impressive that someone chose base 10 to do something when base 10 is what everyone learns since childhood? sure one could choose to change this to 9 or 17 if one needed but unless there is a very specific reason for that - why bother?
btw. i am speaking from experience. i was making multithreading applications that did tons of things in real time. and once you push things to the extremes everything needs attention to detail. then logging is no longer just a matter of opening file, appending line and closing the file. choosing how to handle volumes of data becomes an issue. working with smaller files is faster so splitting things can make sense. and using ring buffer to write one of N files is not unheard of. and making N value change dynamically would make things more complex and slower.
Ahh sorry. Miswritten. Dnwv. Does not work visual. It's a childish coping mechanism for the frustrations of working with something that just keeps crashing. I'm not necessarily impressed with the number 10. I'm impressed that one feature of that software actually works.
Things that doesn't work would include things like creating shortcuts, having internal shortcuts mapped to multiple things, crashing the syntax checker, chrashing on going online, chrashing just because its Tuesday (or the wind turns, or god knows why) ,not being able To change some inline formulas. And that's just the ones I remember from the too of my head.
Being able to create a workable robot program in this is nothing short of a miracle
yes... WoV is big and buggy... it crashes a lot... which frustrates me as well.
and yet, somehow we all keep on performing miracles.
yes... WoV is big and buggy... it crashes a lot... which frustrates me as well.
any yet, somehow we all keep on performing miracles.