Acceedo - Industrial IoT Solution

You enter a server address, port and machine number on a DWIN touch display, power it off, and everything is gone. That happens because values typed on a DWIN HMI live in its VP (RAM) variables, which are cleared on every restart. This guide shows how to save those values permanently in the display's NOR Flash memory with a single UART command, and how to read them back after power-up. It covers the DGUS screen setup, the command frame byte by byte, and a real test with Docklight. The example screen: Server address, Port no and Machine no, designed in DGUS. What you need Display: DWIN DMG32240C035_03WTC (3.5", DGUS II). The same method works on other DGUS II displays. Software: DWIN DGUS tool, and Docklight (or any serial terminal) for testing. Hardware: USB-to-UART (TTL) converter, micro SD card and card reader. Serial settings used here: 115200 baud, 8 data bits, no parity, 1 stop bit (115200 8N1). VP (RAM) vs NOR Flash: why data disappears Mem...

Temperature controllers, energy meters, VFDs, weighing indicators and PLCs: almost every device in a factory has a small RS485 port, and most of them speak Modbus. That one port is how you get data out of existing machines without replacing them. This guide explains RS485 and Modbus RTU in plain terms, with the wiring rules and troubleshooting tips we use on real shop floors. RS485 and Modbus: what is the difference? RS485 is the physical layer : the two-wire cable and the electrical signal that carry bits between devices. Modbus RTU is the protocol : the language of the messages sent over that cable ("device 5, give me register 3"). Think of RS485 as the road and Modbus as the rules for the vehicles on it. Modbus can also run over Ethernet (Modbus TCP), but on most older equipment you will find Modbus RTU over RS485. RS485 wiring rules Two signal wires, A and B (sometimes marked D+ and D−). RS485 is differential, which is why it resists electrical noise...

Ask a production manager how much time a CNC or press stood idle last week and the usual answer is a guess. The shift report says "machine running", but small stops of five or ten minutes (waiting for material, a tool change, an operator away) never get written down. Added up over a month, they are often the biggest loss in the plant. This guide explains how to track machine downtime properly and turn it into action. What counts as downtime? Downtime is any time a machine was planned to run but did not produce. It usually falls into two groups: Planned downtime: scheduled maintenance, planned setups, breaks. You expect it, but you still want to measure it. Unplanned downtime: breakdowns, waiting for material, waiting for an operator, quality holds, tool breakage, power cuts. Unplanned downtime is where the money is, because most of it can be reduced once you can see it. Why manual downtime registers do not work Short stops are missed. Nobody writes down...

"Where is part 1014?" If your stores team answers that question by walking the aisles, you are losing time on every pick. In many factories, finished goods are placed wherever there is space, FIFO depends on the storekeeper's memory, and the ERP only finds out what was dispatched at the end of the day. This post explains how warehouse stores software fixes that, from the floor layout to the confirmed dispatch. The rack drawn as it really stands: every bin in every bay, coloured by bin type. Six steps, in the order the floor actually works Acceedo's Warehouse Stores system follows the real flow of material: Build the floor: place racks, pillars and the entrance on a grid. Map items: give each part the rack cells it lives in. Inspected batches: passed stock arrives with its inspection time. Move to rack: fill a bin, follow the route, drop it in the mapped cell. Pick from rack: load a pick slip and work the FIFO plan. Dispatch: confirm, ...

In most foundries, the charge mix is still worked out on a calculator, the crane operator's loads are written on paper, and the alloy addition after the lab result is a guess that someone corrects on the second sample. Every extra correction costs time, power and alloy. This post explains how foundry melting software can plan the charge, track every heat live and help you get the chemistry right first time . Furnace dashboard: the charge mix filling from the crane, live panel readings and the kg each element still needs. One heat, from the plan to the pour Acceedo's Melting software follows every heat through six steps, as they happen rather than at the end of the shift: Plan: heats are queued against a drawing's chemistry bands and charge rules. Charge plan: two suggestions are worked out in the background, one for the fewest additions and one for the lowest cost. Charge: the crane's loads land on the charge mix automatically, and stock is drawn o...

Payroll day in a factory often means three spreadsheets, a pile of punch exports and a lot of arguments about overtime. Shifts that cross midnight, workers on daily, weekly and monthly wages, contractor labour, canteen tokens and loan EMIs all have to come together into one correct salary. One wrong formula and the whole month has to be checked again. Acceedo's Attendance & Payroll system was built for exactly this: from the first punch to the payslip, in one system. One employee's month: shift, hours, overtime and pay for every day, totalled to the amount to pay. How it works Set up the rules: shifts, grace time, overtime and wage types are set once, on the role. Punches arrive: from biometric readers, QR scans or permitted manual entry. Pair and classify: every IN is matched with its OUT and each day gets a status. Review the month: supervisors check and correct the month on a calendar or month sheet. Add the money: allowances, incentives, de...

Still writing furnace temperatures on paper every 30 minutes? Many heat treatment shops do. It works until a customer asks for the full temperature curve of a batch from three months ago, or an operator misses a reading during the soak. This guide explains how IoT furnace monitoring solves both problems and what it takes to get started. Live dashboard: every furnace, its batch, temperatures and trend chart on one screen. Why manual furnace logging falls short Gaps in the data: A reading every 30 minutes misses overshoots and dips that happen in between. No proof for customers: Automotive and engineering buyers increasingly want batch-wise temperature records, not handwritten sheets. Late problem detection: A thermocouple fault or a slow ramp is often noticed only after the batch has failed hardness tests. Time spent on paperwork: Supervisors spend hours compiling reports that a system can create in seconds. What IoT furnace monitoring actually does An IoT fur...