All Activity

Here is an Autorun guide I worked on at my last job. Hope this helps! AutoRun_Guide_2019.pdf

Hello. I hope information I will provide will clarify some problems. After upgrading Calypso to 7.6 or newer to use old custom report is still possible to small extend. First you have to copy all of your userfields.ini and protocol folder you are using to same location in new calypso. This will allow to keep header settings and "re-connect" inspection plans to your custom report. And now there is important information you CANNOT TOUCH ANYTHING ON REPORT OUTPUT. You cannot trigger multiple-printout (on/off). Basically do not do anything regarding report output. Just run program and if you copied report folder from old protform location to new location in new Calypso - it should connect and output results using Custom Report. When you will try to do anything with report output - Calypso will cut off connection to custom reports and you cannot restore it anymore unless you close inspection plan without saving, or you will get it back from backup. The only thing that stops working is outputting plots and/or any graphical outputs - as old reporting is not supported. If you need plots you have to re-work programs to use PiWeb reporting. Positive thing is that if you were using custom report output in Multiple-Printout you can add plot report to output and this should not affect you. Bonus advice - If you were using syntax to save reports in custom location - remove this syntax before editing program in new calypso especially this is important for systems that were not using Multiple-Printouts as access to this syntax is impossible in New Calypso versions. I hope that help in some cases.

Excuse me Felix, I've just read now your post. In the dialog box there are 3 choices, the first for if you want to divide the mesh into parts or stages, the second for the surface and the third if you want to use a CAD for alignment. It's possible to remove the whole dialog box, but in this case you can't do the other choices. Do you want to remove the whole dialog box?

Hello Ravi, you can try and build a new configuration.

Okay, thanks for the helpful answers. In section A-A, nothing is defined for my datum C, so I created an axis through the two holes.

Have a look here, where the same problem is solved:

@Chuck Swanson If drawing is not demanding (M) / (L) in tolerance band, then don't use it. If you are speaking about protocol, then you should know, that this information is only used for SPC

Although I do agree that reporting the basics can be helpful, Most of the parts we make have hundreds of holes in them, and typically have wide open positional tolerances of like .014. I fall back to this, if the customer model shows all of the basics, then lets report them. If their model only shows the positional tolerance , then that's what we should give them. Unfortunately, our engineering and planning teams want them all included all the time. So, they give me a print with 200 dimensions bubbled that I then have to add the the program I'm writing, when we could have a print with only 35 dimensions to record. typically quadrupling my programming time. 😫

Hallo Messdiener, bei uns steht demnächst auf unserer 6130 ein Retrofit von Atos III auf Atos V an, die Software wird auch auf Inspect 2025 hochgezogen. Nun frage ich mich, welche Einstellungen für die Inspektionen geändert werden müssen, damit ich hier geschmeidig und ohne großen Aufwand aus der Sache komme, um die Messungen annähernd nahtlos im neuen System weiter laufen zu lassen. Ein Austausch und Änderung des Sensorkonfiguration (mit Roboter) im Messaufbau, ist klar; neue Kalibriermessreihe, ist klar; aber welche Parameter müssen noch geändert werden? Es soll ja ein Skript geben, dass das alles ins neue System integriert. Könnt ihr mir da etwas mehr Imput geben? Grüsse Ulrich

I'm new to Calypso software, this one has me very confused as well. I ended up turning off M unless I needed it. 😟

Kyle explained it well. I'd recommend following his suggested strategy.

Could you also measure those radii as partial cylinders instead of circles? You should be able to get an intersection between those. You may also need to add some constraints depending on the size of those radii for accuracy and repeatability.

You can't intersect the circles because technically they don't intersect, at least nominally. They are tangent to each other, which the Calypso intersection constructions doesn't count. Best option, especially without curve, would be to measure the circles at the same height, use recall in a 3D line to make a line connecting their centers and then intersect that line with either circle. You WILL get slightly different values depending on which circle you select, but the difference does give you an idea of how good the part is there.

Jeff, the problem is Calypso cannot make a nominal intersection and I don't have curve. How would you tackle it?

Hi. I've seen this type of situation occur. Usually, it means that the actual result calculated that there was in fact no intersection between the two calculated circles. Instead, I usually evaluate via curves or by intersecting a line from the center of one of the two circles to the other at the nominal intersection. There are a few ways to handle it.

I'm trying to find the intersection of two radius doing offline programming but Calypso said no result

For "Measurement" categorized variables, the supplied argument (the second number in the sequence) dictates which recorded measurement the page will access and display. If you used 3, it would always display the shift value for the fourth measured part. -1 is usually what you want for stuff like this, since it accesses and displays the last (i.e. the most recent) measured value.

If it worked exactly as I've described (cyclically), choosing 3 for the index would return a value of "Day", since "Day" is the zeroth entry, "Night" is the first entry, and "Weekend" is the second entry. So following the logic, the "third" entry would be "Day". However, it's not actually cyclical in that way. I described it that way because I think that makes seeing why -1 returns the final option easier but if it were implemented in this way, lots of things might break. For instance, if a new shift was added (call it "Weekend 2") suddenly, calling the third element of the list returns "Weekend 2" and not "Day". What will happen if you select an index that doesn't exist is raise an error that goes more or less like "Index out of range", which just means there is no corresponding value for that index. In general, for a list of length n you have 2n valid indices. One index counting up from 0 for each element in the list and one index counting down from -1 for each element in the list.

Very interesting, does that mean if I was to instead use 3 instead of -1, it would always display "Night" due to it being the second one in the list? (in the photo i posted earlier in this topic) or would it recall the second time the variable was used? Or am i just misunderstanding lol.

This was answered, but I can offer specifics. Imagine a list of numbers representing measured values: [1, 2, 3, 4, 5]. In most programming languages (that I am aware of), lists and other data structures are "zero indexed" meaning if you were to reference a value at a specific index, you start listing from 0. In my example, we would say that 1 is the 0th element, 2, is the first element, and so on. By using -1 as your index, you look at the value that is before the 0th index. If you think of the list as being cyclical, then it is easy to see that the index before the 0th will be the last element in the list which, for our purposes with PiWeb, is the most recent measurement. So for any place that you see a -1, you could replace it with whatever number you want and retrieve the value at that index. I am doubtful of the applicability of this in most cases, but the option does exist.

Alright, thank you very much for all your help!

When you havee this window, then move mouse pointer onto correct row ( what you want to add ) and column with "?" - it will popup a hint, what you need to write into PiWeb template. Or in that link what i reposted or somewhere in forum you can find a way with usage of context menu.

I am trying to come up with a method to scan Spheres that could range from .100 to .750 (estimated range), these are ground and then lapped. At both grind and lapped, they have to be .00005 max roundness. Looking for speeds, filters, outliers, etc. Right now, I am using a Ø1mm stylus tip. In some cases, my results are on target with a RondCom or about .000001 to .000002 more than the Rondcom. The Rondcom typically gives results in the .00003+ to max (Its slow, cumbersome and easy for an "operator" to make a mistake, I need a better solution). If any users have information that may be of help in this, please post, email or message me.

I think that tells Piweb to fetch the recorded value from the most recent entry in the database. Most of the predefined stuff in the standard report uses that format as well.

I was hoping to use "select report header parameters"option and add additional field to pi web report. Would You know what hardcoded text i would need for that. Sorry I haven't dealt with pi web much. Never needed to make changes to report