About MarvinW

MarvinW · ‎11-19-2024

I am a little confused right now and would like to know if the following behavior is intentional. I am using CPS 5.9.2 and have not tested this with other versions. Peripherals must explicitly state that they support ("yes") or maybe ("NotTested") support a peripheral. If they don't support ("No") or don't state a platform type at all then they will not be compatible with the PLC platform. What I mean that a peripheral with this .ood will not be compatible in ctrlX: <SupportedPlcTypes> <PlcType name="BTC" supported="Yes" /> <PlcType name="RIL" supported="NotTested" /> </SupportedPlcTypes> On the other hand, it seems that objects (units, handlers, add-ons, bases ...) do not have this requirement. If a platform is not found in the ood it is allowed to be used in CPS anyway. Is inconsistency an oversight or intentional? Strictly speaking, if it's not state then a platform should probably be treated as incompatible for both objects and peripherals. However, it is probably a lot more convenient to treat them as "NotTested" for both types. Maybe a warning when reloading STD or adding such an object/peripheral would be nice for a certain grace period whenever a new platform is added. In my books, CXA still counts as a new platform 🤣

MarvinW · ‎11-14-2024

When is this flexible amount decided? Is this during runtime of the machine or during export/compile time of the project? For the latter there are maybe some more options with export template. For the first case, at runtime, I think the grid that you are using is probably the best way. That is, if your 8 parameters fit comfortably into 8 columns. You can link a variable to the Smart Control property VisibleRows (or something like that) to determine how many of your items will be visible. The grid itself can have scroll bars that become available automatically if the number of rows is too big. Another approach that I’ve seen and implemented myself is to have a single view with all the information about one item at a time. Then you supply next/previous buttons to navigate through all the items or maybe even a grid with just a single column from which the operator can select the item they want to look at. This method is most useful if your items contain either too much data to fit into columns on a grid control or if the data can’t be displayed in a gridcell, for example charts.

MarvinW · ‎08-15-2024

In BMG we implemented Modbus with a base object that provides IModbus as a channel. You can get such a channel by either using ModbusRtu which takes IOpconSerial and converts it into IModbus or you can use ModbusTcp which needs an IP address+port and creates IModbus from these parameters. Objects can then use IModbus as a channel parameter. If there is no existing objects then we have ModbusUniversalTemplate which makes programming a unit with Modbus interface quite easy. If you are a Bosch employee then you can contact me through Outlook/Teams (Marvin Werner) to get access to these objects and an introduction depending on your use case. If you are an external user that is working on a project for Bosch then you can try asking your Bosch contact person to contact me, if you think it's worth it. Alternatively use the solutions provided by Thorsten_Brach. That's how I was doing Modbus, too, before I created those objects.

MarvinW · ‎05-14-2024

Hello, I have been using Windows 11 for a few weeks now and haven't encountered any problems that stopped me from working. I am mostly using OES 4.11 and TwinCAT 4022 though and only sometimes CPS (5.5) and TwinCAT 4024. Yesterday I used my Win11 laptop as a TwinCAT runtime to test something locally. After the upgrade I had to run Win8SetTicks again but beyond that everything worked as before. I wouldn't refer to my experience as an in-depth test though. Just doing some station tryout and object development.

MarvinW · ‎04-30-2024

I also encounter the "hanging" mode change quite frequently recently. CANCEL is definitely the most likely candidate for the problem every time. You can check the StateOverview to see which unit is not READY. Also, I think INIT may cause the problem, too. A unit may easily get stuck in this OpconExecState if you use SqX_Init and somehow the chain doesn't finish proberly. But this case needs confirmation from the Nexeed developers or somebody who knows for sure.

Bosch Shared

About MarvinW

Peripherals without explicit platform support entry are treated as not supported

Re: Display Flexible amount of items HMI

Re: How to use Modbus RTU TF6255 with SerialDataStream

Re: Windows11 update

Re: HMI-Can't change the mode of operation

About MarvinW

Peripherals without explicit platform support entry are treated as not supported

Re: Display Flexible amount of items HMI

Re: How to use Modbus RTU TF6255 with SerialDataStream

Re: Windows11 update

Re: HMI-Can't change the mode of operation

Still looking for something?