The post DMC Quote Board – February 2026 appeared first on DMC, Inc..

The SHIELD multiple-award IDIQ is a 10-year, $151B-ceiling contract vehicle designed to accelerate the research, development, testing, and integration of innovative technologies for U.S. missile defense, supporting efforts like the Golden Dome initiative. As part of this enterprise-wide framework, SHIELD enables rapid task-order awards to qualified companies delivering advanced solutions across engineering, analysis, prototyping, and test & evaluation domains.

“It is a great honor for our company to be listed as an approved vendor for the SHIELD program, and it highlights DMC’s track record of providing best-in-class aerospace and defense solutions,” stated Jesse Batche, Vice President at DMC. “We look forward to contributing to future work with the MDA.”

In the list released last month, DMC is included amongst approximately 2,100 companies qualified for future awards from the MDA.

Interested in learning how DMC can support your mission-critical project? Contact us today to learn more about our Test and Measurement expertise and how we can help your team achieve its goals.  

The post DMC Selected as Approved Vendor for the U.S. Missile Defense Agency’s SHIELD Project appeared first on DMC, Inc..

Learn more about DMC’s company culture and check out our open positions! 

The post DMC Quote Board – January 2026 appeared first on DMC, Inc..

Learn more about DMC’s company culture and check out our open positions! 

The post DMC Quote Board – December 2025 appeared first on DMC, Inc..

As a Chicago-based engineering firm specializing in embedded systems, industrial automation, and hardware-software integration, DMC has completed more than 10,000 projects across 40 countries. Our team is now focused on refining the motion systems and embedded intelligence that drive CardMill’s high-speed scanning and sorting capabilities.

We’re working alongside Beyond Design, a long-time collaborator with deep expertise in industrial design and user experience. Together, we form a synchronized team that’s fully integrated into CardMill’s development process.

Engineering for Performance and Scalability

We’re currently focused on refining the core mechanics that make CardMill powerful and reliable:

• Optimizing motion systems for smooth, consistent card movement
• Enhancing tray and feeder design for improved capacity and flow
• Evaluating cameras, motors, and processors to boost speed and reliability
• Strengthening alignment and durability for long-term performance

DMC and Beyond Design are also helping CardMill evaluate manufacturing partners to support tooling, pilot builds, and full-scale production. With over 60 years of combined experience, our teams are guiding the product toward a scalable and efficient manufacturing process.

Built for Collectors, Designed to Last

CardMill’s mission is to make high-performance card sorting accessible to everyday collectors. With DMC and Beyond Design leading the next phase, we’re confident the final product will deliver on that promise. The result will be an affordable, all-in-one scanner and sorter that’s built to last.

We’re proud to be part of this journey and look forward to sharing more updates as we move closer to delivery.

If you are charting a similar path from concept to production, connect with DMC to accelerate your project.

The post Partnering with CardMill and Beyond Design to Bring a Game-Changing Product to Market appeared first on DMC, Inc..

This library extends and simplifies the built-in Modbus functionality within Siemens TIA Portal, giving developers a more flexible and user-friendly way to work with Modbus devices. Ola Bjørnli’s provided examples and documentation, found on GitHub, do a great job breaking down how to use the library. 

How the Extended Modbus Library Works With Modbus TCP 

Here is an example of how to set up a Modbus TCP client. 

Block Interface 

To maximize reusability, we have set up our inputs to include: 

• Connection ID – Unique identifier for each Modbus Client instance 

• Hardware interface – The hardware interface to which the Modbus Server is networked 

• TCP port – Typically 502  

• IP address – The IP address of the Modbus Sever 

This allows the block to be reused for multiple field devices, provided they have the same Modbus interface. 

The static data elements are: 

• mb_query – This is used to define the Modbus queries; one instance can be reused multiple times 

• mb_tcp_ctrl – The function block that establishes connection runs and sequences queries 

• mb_delay_between_queries – Spaces out queries to avoid overloading the server 

• modbusRegisters –  A custom UDT containing the data to be read from and written to the Modbus server. 

The only constant we have defined is the clientNumber, which is the station address. This is usually 0 or 255.  

The Code 

This is taken almost exactly from Ola Bjørnli’s example, but it is broken up so we can walk through each step.  

The initial setup is straightforward: 

• Call the mb_tcp_ctrl block  
  • Map in the interface, connection ID, IP address, and TCP defined in inputs
  • Set your timeout to whatever is needed for your application  
  • Point mb_query to mb_query we set in the static memory 

• Call mb_delay_between_queries  
  • Tie in the same mb_query from static memory 
  • Set the delay needed for your application 

After this initial setup, we need to build our queries. First, looking at the read queries, below are reads for all four types of Modbus registers. Again, the Extended Modbus Library makes this very straightforward: 

• Call mb_query for each query you want to run; there is no limit 
  • data_addr corresponds to the register of the address you are trying to read from 
  • Data_ptr should point to where you want the data to be stored in 
    • Here we have a custom UDT in the static memory, this can either be an array of data points or to an individual point 
  • Mb_addr is the station address we defined as a constant earlier 
  • Mode is used to tell the query what kind of operation we are performing 
    • These modes are defined as constants within the static memory of the mb_query we are calling 

To write to either the output coils or the analog output holding registers, you set up your query calls as shown below. The only difference is that mode is pointed to the “c.write” struct in mb_query instead of “c.read”, and the data_ptr points to the data on your PLC that you want to write to the Modbus device. 

With just these three sections, your code can read and write to any register on a Modbus TCP device! 

How It Works With Modbus RTU 

Using this library, the code to connect to a Modbus RTU device is almost the exact same as a Modbus TCP device.  The only difference is: 

• Call mb_rtu1200_ctrl or mb_rtu1500_ctrl instead of mb_tcp_ctrl 
  • Choose the FB that matches your PLC 
  • hardware_id should be connected to the port your device is connected to 
  • buad_rate should be set to match your RTU device’s baud rate 
  • operating mode should be set based on the table shown below taken from the Siemens information system 

Tips, Tricks, and Troubleshooting

Fun With Pointers 

When passing data to and from mb_query as shown above, the data is passed by a pointer. The function block then finds the start and the length of the data you pass in, meaning the data types passed in do not matter. For example, you don’t need to just have 16-bit integers used to read from input registers.

This is especially useful when: 

• Multiple statuses are bitmapped into a single register 
  • Can automatically splice it into 16 bools 
• A 32-bit datapoint is passed out over two registers 
  • For example, this can be passed into a single real

These can be handled with custom UDTs, like the one shown below. You must ensure proper alignment with the actual register indexes and account for byte-swapping as needed. 

Queries Less Than 16-Bit

If reading fewer than 16 bits (for example, discrete inputs or outputs), use mb_query_bits. While the standard mb_query may still work in some instances, this function is the recommended route to read smaller datasets. 

Troubleshooting Overview

The extended Modbus Library uses the Siemens communication blocks (TCON,  TDISCON, TSEND, TRECEIVE), meaning you can leverage their error codes for troubleshooting.  

Within your function block’s instance memory: 

• Navigate within your “ctrl” block and open “MB_CLIENT” to view error codes 
• You can dig into the individual T-blocks as needed 

Troubleshooting Queries 

It is important to note that each query is executed independently, and if a query fails from a configuration issue, an invalid register, or anything else, it will be skipped, and the next query will be executed.  

The error codes for that query will only be displayed until the next query is run. To debug: 

• Comment out all but one query at a time 
• Troubleshoot until no errors are present and the data is being populated or sent as expected 

Ready to take your automation project to the next level? Contact us today to learn more about our solutions and how we can help you achieve your goals. 

The post Using The Siemens Extended Modbus Library appeared first on DMC, Inc..

Learn more about DMC’s company culture and check out our open positions! 

The post DMC Quote Board – November 2025 appeared first on DMC, Inc..

Smooth Sailing Ahead

On the evening of our cruise, eight of us took the subway together from our office down to one of the piers on the west side of Manhattan. We climbed aboard a grand, 158-foot-long ship with Manhattan by Sail and settled into our spots on deck with a drink. 

In addition to the sound of the breeze and distant city noises, a live jazz performance was the soundtrack of our evening. The peaceful atmosphere was the perfect way to admire the impressive city skyline from the water.  

A Sailor’s Life

The team agreed that seeing the Manhattan skyline from the water was the highlight of the evening. It was unique to see the views looking uptown from the harbor. It was incredible admiring landmarks like the Statue of Liberty, Ellis Island, Governors Island, and the city’s bridges from this impressive perspective. The summer sunset glowing on the water only added to the impressive views. 

Our sailing experience was more than just pretty views; we got hands-on experience. The crew allowed passengers to hoist the square-rigged ship sails on the 120-foot-tall masts, and a few of us jumped at the opportunity. When we weren’t raising the sails, we were able to roam the deck and explore new views from every angle. 

Our team took turns raising the sails and pointing out NYC landmarks from the sailboat. The fun experience sparked conversations about other New York Harbor adventures we could plan in future summers. In addition to embodying our core value, “Have Fun,” our memorable cruise inspired us with new perspectives and even some sailing skills. 

Learn more about DMC’s company culture and check out our open positions. 

The post DMC NYC Sets Sail on a Sunset Cruise  appeared first on DMC, Inc..

Learn more about DMC’s company culture and check out our open positions! 

The post DMC Quote Board – October 2025 appeared first on DMC, Inc..

Learn more about DMC’s company culture and check out our open positions! 

The post DMC Quote Board – September 2025 appeared first on DMC, Inc..