Serial Timeout
Hartmut Eger
Is there a solution for this?
mark maker
Look at the log at trace level.
_Mark
What is causing a serial timeout?
Is there a solution for this?--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/977b7f83-9550-4a34-bbd6-b55628258d06n%40googlegroups.com.
Hartmut Eger
Hartmut Eger
at org.openpnp.machine.reference.driver.GcodeDriver.sendCommand(GcodeDriver.java:1074)
at org.openpnp.machine.reference.driver.GcodeDriver.sendGcode(GcodeDriver.java:1041)
at org.openpnp.machine.reference.driver.GcodeDriver.sendGcode(GcodeDriver.java:1023)
at org.openpnp.machine.reference.driver.GcodeDriver.actuate(GcodeDriver.java:899)
at org.openpnp.machine.reference.ReferenceActuator.driveActuation(ReferenceActuator.java:270)
at org.openpnp.machine.reference.ReferenceActuator.actuate(ReferenceActuator.java:260)
at org.openpnp.spi.base.AbstractActuator.actuate(AbstractActuator.java:318)
at org.openpnp.gui.ActuatorControlDialog$1.lambda$actionPerformed$0(ActuatorControlDialog.java:85)
at org.openpnp.util.UiUtils.lambda$submitUiMachineTask$0(UiUtils.java:38)
at org.openpnp.spi.base.AbstractMachine$1.call(AbstractMachine.java:571)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2021-12-23 15:32:31.261 MessageBoxes DEBUG: Error: java.lang.Exception: serial://COM8 timeout waiting for response to M801
2021-12-23 15:32:35.311 ReferenceActuator DEBUG: Top Light.actuate(false)
2021-12-23 15:32:35.312 GcodeDriver DEBUG: [serial://COM8] >> M800, 15000
2021-12-23 15:32:50.315 AbstractMachine TRACE: Exception caught, executing pending motion: java.lang.Exception: serial://COM8 timeout waiting for response to M800
at org.openpnp.machine.reference.driver.GcodeDriver.waitForConfirmation(GcodeDriver.java:1093)
at org.openpnp.machine.reference.driver.GcodeDriver.sendCommand(GcodeDriver.java:1074)
at org.openpnp.machine.reference.driver.GcodeDriver.sendGcode(GcodeDriver.java:1041)
at org.openpnp.machine.reference.driver.GcodeDriver.sendGcode(GcodeDriver.java:1023)
at org.openpnp.machine.reference.driver.GcodeDriver.actuate(GcodeDriver.java:899)
at org.openpnp.machine.reference.ReferenceActuator.driveActuation(ReferenceActuator.java:270)
at org.openpnp.machine.reference.ReferenceActuator.actuate(ReferenceActuator.java:260)
at org.openpnp.spi.base.AbstractActuator.actuate(AbstractActuator.java:318)
at org.openpnp.gui.ActuatorControlDialog$2.lambda$actionPerformed$0(ActuatorControlDialog.java:96)
at org.openpnp.util.UiUtils.lambda$submitUiMachineTask$0(UiUtils.java:38)
at org.openpnp.spi.base.AbstractMachine$1.call(AbstractMachine.java:571)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2021-12-23 15:32:50.315 MessageBoxes DEBUG: Error: java.lang.Exception: serial://COM8 timeout waiting for response to M800
Hartmut
mark maker
you need to attach the whole log, to see where it comes from.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/aa40503f-1e3e-49a9-9fa9-028af87d91efn%40googlegroups.com.
mark maker
There is nothing suspicious there. The controller simply seems to
not respond, or the serial connection is lost.
All I can tell you is to check cabling and grounding issues.
I always recommend using an USB isolator on the controller, and
to make sure the camera PCBs are not grounded to the
machine.
https://makr.zone/grounding-the-machine/283/
What controller are you using again?
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/f7e3764d-b418-4396-84db-f34b31e4c507n%40googlegroups.com.
Hartmut Eger
mark maker
>Smoothieware Smoothieboard 5XC V1.1 32 bit (China Clone)
I will not spend my spare time trying to support a board
from a manufacturer that is known to be a bad parasite of Open
Source projects and uses sup-par components to save a few
cents, knowing it will cause problems down the road.
I assume you didn't know when you bought it and you are now
a victim too. I'm sorry about this. But please buy one of the
products adhering to Open Source principles. These principles
are very important to me, they are the only thing that "pay"
for my efforts here.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/7fa3de63-7e8d-4732-9c7a-51d5648578b7n%40googlegroups.com.
Hartmut Eger
Sorry for your efforts, but I didn't know until I found out that it was a clone and not an original smoothie board.
mark maker
Hi Hartmut,
All the very best in 2022 to you too!
> I have now installed an original Smmothie Board but the timeout problem has not been solved.
Well, that is unexpected. 🙁
A few approaches:
- Just to exclude an OpenPnP related effect, can you please do the same using Pronterface or similar?
- What is the welcome message of Smoothie in Pronterface?
- What is the response to M115?
- Does any of the M8xx commands
actuate something that might create large electrical
interference? The pump perhaps? Does it help to leave out that
command?
- Have you mounted a flyback
diode on the pump and valve?
- Do you use an USB isolator on the controller?
https://www.adafruit.com/product/2107 - Alternatively, can you use a notebook that is not earthed (two-pin power plug), or running on batteries?
- Sad question: How sure are you that the German dealer has
provided you with a genuine board?
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/b4b4c4c8-ae49-49cf-8449-dad870038c63n%40googlegroups.com.
Hartmut Eger
Printer is now online.
SENDING:M115
FIRMWARE_NAME:Smoothieware, FIRMWARE_URL:http%3A//smoothieware.org, X-SOURCE_CODE_URL:https%3A//github.com/markmaker/Smoothieware/tree/feature/best-for-pnp, FIRMWARE_VERSION:feature/best-for-pnp-23a1f0db, X-FIRMWARE_BUILD_DATE:Feb 15 2021 20:34:17, X-SYSTEM_CLOCK:120MHz, X-AXES:5, X-PAXES:5, X-GRBL_MODE:0, X-CNC:0, X-MSD:1
M801 Top LED on
M802 Up LED off
M803 Up LED on
M804 Vacc. Pump off
M805 Vacc. Pump on
M810 switch.vacnoozleleft off
M811 switch.vacnoozleleft on
M812 switch.vacnoozleright off
M813 switch.vacnoozleright on
I am currently using a USB cable with a ferrite core on both connectors. I will probably have to get a USB isolator
7. Alternatively, can you use a notebook that is not earthed (two-pin power plug), or running on batteries?
I also checked all the chips again using Arthur Wolf's parts list.
Hartmut Eger
mark maker
> Can there be any improvement if I control the machine via a TCP connection?
It would help with isolation, but unfortunately TCP is way too
slow on the Smoothie.
> All M and G commands tested in Pronterface no problems I don't get a timout error. all movements of G28, G0 X480 Y450, M800-M813 no problems
To make this more realistic, please write all the same commands
your OpenPnP would send into a file. You can enable Gcode logging
on the Driver to automatically create such a file. Then "play" the
file using Pronterface, so the serial exchange would probably be
as seamless as with OpenPnP. Specifically, the electrical noise or
ground bounce that is created by actuating something would overlap
with the next serial/USB packet being sent immediately.
Just to be sure: did you accept Issues & Solutions suggestions, like for serial flow control? Any other serial settings that might be different?
This is really getting strange.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/8135d3aa-5153-4337-9753-6de07a0874a2n%40googlegroups.com.
Hartmut Eger
When the machine is switched off via the open pnp software, there are also timeouts for the following M commands:
M804
M810
M800
M812
M802
mark maker
> M commands have a time switch of 5 seconds and this also seems to provoke a timeout if the command sequence is too fast.
I don't understand that sentence, but it somehow sounds
suspicious.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/89ac38a0-e44c-4be1-b829-7c1262de2a43n%40googlegroups.com.
Hartmut Eger
2022-01-03 22:31:48.822 GcodeDriverConsole DEBUG: Gcode console error: java.lang.Exception: serial://COM4 timeout waiting for response to M802
mark maker
I'm really at a loss here.
I wrote:
> Just to be sure: did you accept Issues & Solutions suggestions, like for serial flow control? Any other serial settings that might be different?
This question is still open, or have I missed something?
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/b639e66a-4db0-462d-81fb-d8d47cf473fen%40googlegroups.com.
mark maker
I just re-watched your video. The machine speed is very
"conservative" 😉.
It is well possible that it takes more than 5 seconds for some of
these moves. Please simply try with a higher timeout value.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/5b7ee218-c9ea-2865-d43b-e06ff7f06825%40makr.zone.
mark maker
Or better yet, crank up the speed. I'd really love to watch this nice-looking machine at three, four, five times the speed, I'm sure it can take it, if my cr** Liteplacer can.
https://makr.zone/pick-place-machine-first-simulated-small-test-run/66/
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/bb50904e-6f74-2b7d-8d97-16e876944852%40makr.zone.
Hartmut Eger
is the speed better now?
I fixed 3 contact errors, maybe this was the solution.
Everything will be fine.
Now I have to write about my problems with the configuration of the open pnp machine and the associated software. I just have too little idea to understand what is required of me, even with Issues & Solutions I don't really get to my goal.
Enclosed the problem with Dynamic Safe Z or Fixed Safe Z I can't decide which is right.
Thanks and regards
Hartmut
mark maker
I recommend Dynamic Safe Z and then setting Safe Z as low as
possible for each of the nozzles. This will minimize the Z
movements and speed up operations. Given your machine has a large
Z headroom, you'll get a large Safe Z zone, which means you
nozzles will move around quite lopsided. When the nozzle is
switched, you'll have see-saw movement. This is normal and much
more efficient. And cool-looking, if you ask me.
The other things I can't explain "auf Vorrat". You need to ask
more specifically. Be sure to have read the Wiki linked by the
blue [i] buttons.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/93fef2a6-f8e8-43a1-92c0-08b1e12f9057n%40googlegroups.com.
Hartmut Eger
I think I understand how Issues & Solutions works.
I will now work through the open points.
Hartmut Eger
I do not fully understand in which context SoftLimitLow, SafeZoneLow, SafeZoneHigh and SoftLimitHigh.
OpenPnPCaptureCamera Up Camera
Hartmut Eger
Thanks was done, I found the solution.
Hartmut Eger
Hi Mark,
Unfortunately the OpenPnP Capture Camera Up camera does not work.
The error message "Subject not found."
mark maker
Hi Hartmut,
You should optimize Nozzle Safe Z handling & Zone using Issues
& Solutions. You'll get more optimized performance.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/8dc2877a-3ab5-4250-96a8-1b6dc27a883bn%40googlegroups.com.
mark maker
Hi Hartmut,
The red indicator looks like a ellipse. It seems you might have Units per Pixel set (manually?) on the bottom camera, that are completely uneven.If in doubt, set the X/Y Units per Pixel on the bottom
camera to zero and retry the Issues & Solutions step
you have in your screen-shot.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/622eff3f-c6eb-4cb3-91c8-5f99916a8386n%40googlegroups.com.
Hartmut Eger
I have been solving this problem for 2 days now, but I still haven't found the point how it could work.
mark maker
WTF! (sorry, but this is really a case for the F word)
At 0:33 you see what looks like an Auto-Focus movement. But Auto-Focus Vision starts only at 0:38.
Frankly, I don't know how this is even possible.
The first thought is that there is something wrong with your flow
control (OpenPnP does not wait for the motion to complete). But
then it would be reversed, i.e. vision would come too early
(not waiting for the machine), not too late.
But then you get a second Auto-Focus move at 1:01. And I know for
a fact, there is only supposed to be one, and this code is
really a simple multi-pass loop! These are also Machine tasks;
there is a central entity queuing tasks, so even if you press the
Accept button twice, it should just do it twice, one after the
other, not somehow "interleave" it.
WTF!
Please send the machine.xml
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/77c06072-cdee-430a-ae46-535669a04b9en%40googlegroups.com.
Hartmut Eger
Hi Mark,
would it make sense to reset my configuration of the PnP machine and start all over again?
I'm not sure if I really did everything right at the beginning of the configuration.
Thanks and regards
Hartmut
mark maker
Hi Hartmut,
You need to deal with these Issues & Solutions that you dismissed and/or left open, or that are useful (I mean the ones selected in the screen-shot below):
NOTEs:
The create nozzles for this head issue will create the vacuum valve actuators for you, so the two warnings (orange) further below will vanish. Furthermore, it should likewise solve the Nozzles N1 and N2 have the same Z axis error (red) for you.
The most important one is the MOVE_TO_COMPLETE_COMMAND
suggested issue. You should really
not "dismiss and forget" important commands like these 😭
This command is responsible for OpenPnP to wait for motion to
complete, if you remove it, nothing will work.
The suggestions further below about the camera preview FPS etc. might in-deed create the strange delayed vision feedback. Your cameras have a whopping 30 FPS preview set, and are not suspended during tasks, so they might create frames faster than what the GUI can handle and perhaps create the strange effect that vision frames from the task appear long after the preview frames (the task being starved out of capture frames), the effect perhaps being amplified in the exotic combination with a missing MOVE_TO_COMPLETE_COMMAND!
In the future, please do not dismiss Issues & Solutions unless you really, really know what you are doing. You have a Smoothieboard, so you can trust Issues & Solutions to generate good and extensive solutions for you. Ask here, if unsure. Please open new discussion threads for each of them.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/a5ef4ed3-21af-4283-a77c-3c8690c291fan%40googlegroups.com.
mark maker
No, just see the mail I sent you.
Note, for the most part, Issues & Solutions keeps
its eyes on your configuration during the whole life-time of your
machine. So if things are not good, they are reported, even after
having manually (mis-) configured them.
... unless you dismiss them, of course 😭
There are exceptions from this rule. Things that Issues &
Solutions cannot safely propose for you, will be
reported as missing is empty, but as soon as it or you filled in
something, Issues & Solutions is happy. Like the
CONNECT_COMMAND, HOME_COMMAND. You can empty them to get a
proposal. For Actuator read and actuate commands, you are on your
own, as these can be highly individual.
Other solutions can be re-opened, like the calibration steps.
Just switch on the Include Dismissed and Include
Solved switches in the Issues & Solutions tab.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/d7804957-cdfd-44e4-bd1b-6214280542c0n%40googlegroups.com.
Hartmut Eger
The first success has already set in.
Open PnPCaptureCamera Up Camera is completely processed and done.
the info from Issues & Solutions links to Smoothieware but I really can't find a solution.
mark maker
Read here, starting from...
"Please make sure your Smoothieware is configured to
use true axes, i.e. A B
C, not extruders..."
https://github.com/openpnp/openpnp/wiki/Motion-Controller-Firmwares#smoothieware
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/772fc843-0f2d-46e5-90e3-2bf06a698403n%40googlegroups.com.
Hartmut Eger
I hope that the error messages are less and less.
At the moment it is "FIDUCIAL-HOME no matches found"
This message comes after switching on the Open PnP machine and carrying out the reference run. At the end, the error message is displayed.
as soon as I want to switch off the machine, I get the timeout error message for M800, M802, M804, M810 and M812 again.
attached is the link to the video.
I have attached my machine.xml
mark maker
I need a log. I don't understand what the video is supposed to show, frankly.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/93dc5ee0-c0f2-416b-be2c-bc04b01e498bn%40googlegroups.com.
mark maker
Hi Hartmut,
WARNING: I assume your machine is
still fresh, and you have not yet captured many locations or your
visual homing has never worked before, i.e. your homing fiducial
can still be defined. If this is not true,
please do not proceed, and report back.
- Upgrade to the newest OpenPnP 2.0 testing version (while we're
at this, you can learn about and help test the new Vision
Settings feature):
https://openpnp.org/test-downloads/
- Go to the Head and switch Homing Method to None. Press Apply.
- Go to Issues & Solutions and press Find Issues & Solutions.
- There should be an entry "Enable Visual Homing":
- Follow the instructions carefully.
- This will automatically create/modify a FIDUCIAL-HOME Package
and Part and assign the no-tuning DetectCircularSymmetry
stage/pipeline, which so far has worked very well. For
background, you can read about the DetectCircularSymmetry
and that
specific pipeline in the Wiki, but the idea is that users
no longer need to care about this.
- You can go to the FIDUCIAL-HOME Part and see, how the Fiducial Vision Setting were assigned. Please send a screen-shot, you'll help the testing effort that way 😁.
- Exit OpenPnP, power cycle the machine, and re-start and
re-home. Report back if everything went well.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/070a2f00-8d20-4b35-9505-a3f1ef1062efn%40googlegroups.com.
Hartmut Eger
all 8 points carried out conscientiously but no improvement.
After I turn the machine back on and click on the yellow house in the jog, it works exactly like in the previous video.
mark maker
Please send the machine.xml
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/cdd50ffd-caf1-429a-9573-db27383bfe77n%40googlegroups.com.
mark maker
Ahh, and I forgot: send the new
vision-settings.xml too, please.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/3889504e-7310-4cf3-a7ab-47c5b5719c71n%40googlegroups.com.
mark maker
Ahh, sorry, and I need the packages.xml
and parts.xml too.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/0a835c24-5681-4b98-a333-b2385de6ecb0n%40googlegroups.com.
mark maker
- Go to the cameras and make sure Auto is off on Exposure. Then
set the Exposure manually.
- Reading this section can also help understand and get the
camera settings right:
https://github.com/openpnp/openpnp/wiki/Camera-White-Balance#prepare-the-device-settings
(you can also read the hole Wiki page and get the White Balance done too)
- Go to your lighting actuators and switch off coordination
Before Actuate, and keep After Actuate switched on.
This will switch your lights on earlier and give the camera more
time to adapt (even if you switch off all Auto settings,
I believe that some adaptation to changed lighting
still takes place in most camera models).
- After homing fails, go to the Head and press Visual Test. Does it nail the fiducial reliably?
- Jog around a bit and try at different distances, it should
still work from a few Millimeters away.
- If it still does not work, have a look at Camera Settling:
https://github.com/openpnp/openpnp/wiki/Camera-Settling - If your manual camera Exposure settings is higher that -9 on
an ELP camera, it means the LED light may be rather weak, which
means the exposure may take longer and require a longer settle
time and make the machine slower. You might need to improve
lighting. Read this:
https://makr.zone/camera-fps-cpu-load-and-lighting-exposure/519/
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/0a835c24-5681-4b98-a333-b2385de6ecb0n%40googlegroups.com.
Hartmut Eger
Hi Mark,
here are my answers to the 7 points.
1. done
2. doen
3. done
4. after the reference run, the head
moves over the fixed fiducial and displays the error message
"FIDUCIAL-HOME no matches found".
The Nozzle 2 stays at -20. With a click on (1) the two nozzles move back into
the neutral position.
5. Done. Works very well and no error messages.
6. I'm missing the Vision tab in the
openpnp software under the point listed in your link.
so I don't really know how to proceed.
Hartmut Eger
I had spent the last two days dealing intensively with my machine and the open PnP software.
The problem arises as soon as I open the Issues & solutions item "ReferenceHead H1" "Enable Visual Homing." perform and accept.
Then the homing method is set to "ResetToFiducialLocation" (1) under Maschine Setup-Heads-ReferenceHead H1 and from then on my machine goes crazy.
If I now click on Homing (1), the head moves to the 0 positions of X and Y and Z. Then the head moves to the position of the fixed fiducial, switches on the top light and sets the Nozzle N2 to Z 20. Then comes the error message
mark maker
Hi Hartmut
No offense, but could it be that this is a language problem?
Unfamiliar terms like "reference run" keep reappearing, we seem to
keep misunderstanding each other... 😭 so I suspect you are using
translation software. Right?
Darum ausnahmsweise in Deutsch... ich hoffe das kommt dir jetzt
nicht in den falschen Hals, es ist konstruktiv gemeint.
Ich sehe Einstellungen in deiner machine.xml die ich beim besten
Willen nicht nachvollziehen kann. Es sei denn, du verstehst die
Anweisungen von Issues & Solutions (und im Wiki) auf Englisch
nicht?
Benutzst du Übersetzungssoftware? Welche? Ich empfehle DeepL,
das kommt noch am ehesten sinnvoll raus. Du müsstest aber immer
noch kontrollieren, ob zum Beispiel keine falschen Negationen
reingerutscht sind. Zum Beispiel wundere ich mich schon sehr,
warum du in diesem Screenshot alles auf Auto gesetzt hast, nachdem
ich dir doch geschrieben (und eine Wiki Seite angegeben habe),
alles NICHT auf Auto zu stellen:
Ein anderes Beispiel: du hast die Soft Limits (Begrenzung des
Bewegungsbereiches) der Z Achse und die Safe Zone (Bereich, wo die
Z Achse auf sicherer Höhe zurückgezogen ist) auf denselben Werten.
Selbstverständlich kann so überhaupt nichts funktionieren. Ich
kann mir aber kaum vorstellen, wie man so was falsch machen kann,
es sei denn, du hast die Issues & Solutions Anweisungen (in
Englisch) nicht verstanden...?
Tipp für die Zukunft: man kann die Text-Blöcke in den
Issues & Solutions mit der rechten Maustaste anklicken,
sie blinken dann schnell auf Grau, als Zeichen, dass sie in die
Zwischenablage kopiert wurden. Dann kannst du sie DeepL füttern.
Zu deiner Konfig:
Der schlimmste Bock ist in der Kamera. Du hast die reguläre Z Achse zugewiesen, statt die Virtuelle Z Achse. Komischerweise moniert das Issues & Solutions bisher nicht (war eigentlich überzeugt, dass es dies tut). Ich habe das nun hinzugefügt, kommt in einer nächsten Version.
> I'm missing the Vision tab in the openpnp software under the point listed in your link.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/f16dad55-dbcb-4f29-92a9-eb075a12a6ben%40googlegroups.com.
Hartmut Eger
partly I use the translation database TEX-L from Autodesk to understand the connections better. Yes, my English is certainly not excellent, but somehow I get to my goal.
For better understanding I will make my contributions now bilingual so that there are no more misunderstandings.
The "reference run" comes from my CNC milling machine and is the control around the X Y Z zero point.
As for my camera settings, the picture was a mistake on my part, I briefly set everything to auto and then disabled again. Real the settings look like this:
zum Teil nutze ich die Übersetzungsdatenbank TEX-L von Autodesk um die zusammenhänge besser zu verstehen. Ja mein Englisch ist sicher nicht ausgezeichnet, aber irgendwie komme ich schon an mein Ziel.
Zur besseren Verständniss werde ich meine Beiträge jetzt zweisprachig gestalten damit es zu keinen Missverständnissen mehr kommt.
Die "Referenzfahrt" kommt von meiner CNC Fräsmaschine und ist die Kontrolle um den X Y Z Null-Punkt.
Was meine Kameraeinstellungen angeht war das Bild ein Fehler von meiner Seite, ich habe kurz alles auf Auto gestellt und danach wieder deaktiviert. Real sehen die Einstellungen so aus:
Hartmut