Recently active
Bosch ConnectedWorld Blog
Please join us at PTC LiveWorx Europe 2015, November 17-18, Stuttgart, Germany. At this event, you will join the fastest-growing network of IoT professionals responsible for product innovations and new business models for creating, connecting, analyzing and servicing “smart products”. At PTC LiveWorx Europe, you will:Learn from Experts - Access dozens of sessions hosted by customers, PTC product experts and business leaders sharing vital best practices to accelerate your IoT journey and help you drive tangible business results. Be Inspired - See visionary keynotes up close and personal. PTC will host a series of engaging keynotes featuring industry luminaries, leading manufacturers, customer spotlights and much more.Connect with Partners - Learn how to leverage solutions and innovations, and engage in meaningful conversations in the Partner Pavilion and IoT Solution Showcase.Experience Breakthrough IoT Technologies – In the first of its kind IoT Solution Showcase, you will
If you're going to run 2D, make sure your surface is in the positive XY plane, or you will get an error.
Try making a surface region to represent the area where the collar would make contact with the pipe and apply the load on that surface.
From Mike Mahoney's blog:"There’s a few pieces you need in place to do a file transfer. Transfers can be executed in either direction: edge->platform or platform->edge. To do a transfer the edge component must be configured with a set of virtual directories. For the EMS, the configuration section would look like this:"file": { "virtual_dirs":[ { “In" : "./in" }, { “Out": "./out" }, { "staging": "./staging" } ], "staging_dir": “staging"}This is important because you will need to virtual dir names in the parameters to the Copy call. In the above example assumes that there are three directories in the same location as the EMS executable: ‘in’, ‘out’, ‘staging’. You can specify absolute paths as well.For the example I’m about to give, assumer the following:A RemoteThingWithFileTransfer named RT1.That the files a
"The scanRateResolution setting controls the frequency at which the main loop of a thing script executes in the LSR. Once a ‘thing’ script is started it enters into a loop that executes until the script resource is shutdown. Each iteration of this main loop takes a number of actions. At a high level it does the following:Goes through all your configured properties. If each property’s ‘scanRate’ amount of time has expired, then the property is evaluated to see if it should be pushed. To do this, the property handler read method for each property is called and the new value is compared to the old (if necessary). If the property needs to be pushed to the server its is added to a temporary list of properties to be pushed.The temporary list of properties is pushed to the server. If no properties have been evaluated, or no properties need to be pushed, then this list will be empty and nothing is pushed.The thing’s registration with the EMS is checked
"During edge testing we ran into the bug PLATFORM-1841. When a connection was lightly loaded and had little or no activity, a multipart message sent from the server to the edge would fail to send the last chunk until it received a message of any sort from the edge. The end result would be a message timeout on the server. Quite often the timeout would be avoided because of the fact that the edge regularly sends pings to the server, but since the default ping rate is longer than the default message timeout you would often see multipart messages from the server to the edge timing out.We were able to resolve this issue by modifying the SO_SNDBUF value that Tomcat uses for sockets. This controls the size of the output buffer used by TCP. Setting it to something larger than our message chunk size of 8192 prevented the timeouts and ensured that all the chunks were delivered as expected.This config option can be set in the Tomcat Connector configuration in y
Reposted from Mike Mahoney's blog:"'Pings' are the mechanism that our websocket clients (both EMS and SDKs) use to maintain an active connection with the server. There are two primary reasons for pings:Proxies/routers between our clients and server might automatically disconnect idle connections after some period of time.In some cases, if a TCP connection is dropped the client or server might not immediately become aware of the lost connection. If the server expects a ping within some predefined amount of time, but does not receive one, then it can assume the connection is dead and close it. Similarly, if a client sends a ping and does not receive a response within some amount of time, then the client can assume the connection is dead.The server, by default, has an Idle Connection Timeout of 60 seconds (found in the WSCommunicationSubsystem). This means that any websocket that has been inactive for 60 seconds will be closed. Therefore, clients must send so
Reposted from Mike Mahoney's blog post:The EMS creates the config.json.booted file after a successful startup and connect. It writes out its current configuration as a backup. If, on later restarts, the config.json is corrupted for some reason the EMS will fall back on the config.json.booted.A common problem is that a user will edit their config.json and inadvertently insert an error. Then, on startup, the EMS will fall back on the config.json.booted. This will often go unnoticed unless you are closely watching the error log of the EMS. During initial development and configuration it is usually a good idea to delete the .booted file if you are trying different configuration settings.
Reposting Mike Mahoney's blog post:"There’s two Lua properties in tw_server that you can use to discover information about the EMS's availability and connection status:tw_server.available – set to true if the script resource can connect to the EMS.tw_server.online – set to true if the script resource detects that the EMS is connected.Here’s how they work. Everytime the tw_server API is used to make a HTTP request to the EMS it checks the EMS status:If the HTTP response is 200, it considers the EMS available and onlineIf it is a an error, is calls the new isConnected propertyIf the result is a 200:Set tw_server.available to trueChecks the result of the response to set tw_server.onlineIf the result is a 503 with a JSON response:Set tw_server.available to trueChecks the result of the response to set tw_server.onlineIf the result is a 503 without a JSON response:Sets tw_server.available to falseSets tw_server.online to falseKeep in mind that these variables can be stale if the LSR ha
Reposting Mike Mahoney's blog post:"The 5.0 version of the Lua script resource has improved support for InfoTables. By using the tw_infotable library you can create and manipulate InfoTables:---- Create a DataShape. This definition will place the DataShape into-- the global 'DataShape' table. This definition would typically be-- found in your template file.--dataShapes.MeterReading( { name = "Temp", baseType = "INTEGER" }, { name = "Amps", baseType = "NUMBER" }, { name = "Status", baseType = "STRING", aspects = {defaultValue="Unknown"} }, { name = "Readout", baseType = "TEXT" })-- Lock around this chunk of code. Must always lock around-- access to the global DataShape table.tw_mutex.lock()---- Access the DataShape we want to use and then clone it. DataShapes-- must always be cloned before being used to create an InfoTable.--local ds = DataShape.MeterReading:clone()---- Create an InfoTable based on the DataShape. If this fails the -- function will return nil plus an error message.
Re-posting Mike Mahoney's blog post:"Websockets disconnects can happen by choice, or due to exceptional/error conditions. Here is some information about what happens in each case:Clean disconnect: During a clean disconnect, the user or application will initiate a disconnect sequence. This has two steps. First, if one or more things are bound to the websocket, the client will send an UNBIND message to the PLATFORM. This will cause Things bound to the websocket to appear as offline (their isConnected property will be set to false). Then, the client will close the websocket according to the websocket protocol.Exceptions/Errors: In many cases, the underlying network interface will be aware of unexpected disconnects. For example, if you forcefully kill an EMS, the Platform's network interface will be notified, the websocket will be closed, and Things will be cleanly unbound. In those cases, the updating of the isConnected property will o
Re-posting Mike Mahoney's blog post:"I've explained the connection process for 5.x web socket based clients a lot of times, so I thought it would be useful to just write it up. The SDKs and the EMS both follow a three step process when connecting to the Platform:Establish the physical websocket: The client opens a websocket to the Platform using the host and port that it has been configured to use. The websocket URL exposed at the Platform is /Thingworx/WS. If configured, TLS will be negotiated at this time as well.Authenticate: The client sends a AUTH message to the platform, containing either an App Key (recommended) or username/password. The AUTH message is part of the Thingworx AlwaysOn protocol. If the client attempts to send any other message before the AUTH, the server will disconnect it. The server will also disconnect the client if it doesn't not receive an AUTH message within 15 seconds. This time is configurable in the WS
What training or additional knowledge do you need to improve your product development? What trends or issues will have the greatest impact on your work over the next few years?Please tell us so we can build a 2016 conference agenda that meets your needs! Complete a brief survey that will be used to help shape next year’s program content!Everyone who completes the survey by September 1 will be entered into a raffle for a complimentary pass to the 2016 event in Boston.Access the survey here.We look forward to seeing you next June in Boston!
The attached 2-page document helps clarify the differences between h-elements and p-elements.
Nice sweep, but the start/stop is on the same plane? Or is it?
Hi Antonius,I just wanted to show that PTC does have 3D curve sketching, but its' for Elements/Direct Modeling. Notice all the capability it has in the ribbon tab for 3D curves.
The attached model image was made with just three curves and no points. The orginal post stated that you had to make the curves through a series of points. Even if you sketch a spline, you don't have to make a curve through previously created points, but I do like the idea of having 3D sketch capability.
PTC does have 3D sketch capability in Elements/Direct Modeling. Watch the attached video.http://learningexchange.ptc.com/tutorial/3493/creating-3d-curves
Are you talking about the attached video?https://m.youtube.com/watch?v=mKFNHX3OlIU
Can you upload an image of the SW sketch?
Steve,DId you resolve the problem? Did you try the model I uploaded? Take the model I uploaded and delete the mirrored group then try to remirror. Try it in a clean directory. M030 should handel a simple mirror task as this. You could make a simple blend to connect the two ends of the rod and not worry about mirroring.
Vaibhav,You will find some useful tips in the attached file from Urs Simmler for roller-bearing constraints. Start on Page 23 and work your way through Page 27. Weighted Links: "Tips & Tricks" starts on Page 19. The whole document is 40 pages.
Die PTC LiveWorx Europe ist in diesem Jahr die wichtigste Veranstaltung in Europa, die PTC ausrichten wird. Hier werden Sie all das wiederfinden, was Sie in Stuttgart in den letzten Jahren bereits kennen und schätzen gelernt haben und auch dieses Jahr wieder erwarten – nur noch größer und noch besser - und einiges mehr. Merken Sie sich den Termin jetzt schon vor: PTC LiveWorx Europe17.-18. November 2015ICS Messe StuttgartDas Beste der PTC Live:Erfahren Sie mehr über unsere neuesten Produktinnovationen und die bewährten Geschäftsmodelle im gesamten PTC Lösungs-Portfolio. Highlights hierbei sind PTC Creo, PTC Windchill, PTC Integrity (inklusive Atego), und ThingWorx sowie die PTC Service Lifecycle Management-Lösungen einschließlich der neuen ServiceMax-Partnerschaft.Das Wissen für Ihre Entscheidungen: Erfahren Sie in Vorträgen und Beispielen, wie Sie das Potenzial vernetzter Architekturen greifen können. In der System- und Prozessgestaltung, in neuen Geschäftsmodellen,
Steve,The default setting is Dependent Copy in M050 and you should have been able to do this in M030, I mean mirror the features without any problems.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.