Machine monitor connections

Manufacturers’ monitors (Rieter, Trützschler, Uster, Loepfe, Murata) expose shift production via API. Here you set where the server is, the token and which JSON key carries each log field. In the spinning log, "Pull from monitor" brings the last 7 days into the review — nothing is saved without your OK.

The Machine room tab shows every machine in spinning, knitting, weaving and dyeing by its current state — running, stopped, no program or under maintenance — with how long it has been like that, the stop reason the operator entered on the phone, how much it ran today and the production cell's OEE, when the machine has a cell. In dyeing it also shows the lot and color in the bath. Machines come from each department's register; the state comes from the readings the factory sends.

The suggested path and map per manufacturer are a starting point: the API changes by version and licence. Use "Test connection" — it says what is missing, the server error or how many records came back.

Import the spindle sensor file (machine; spindle; date; shift; breaks; hours). Nothing is saved before you check it: each rejected row says the row, the column and the reason, and can be downloaded. "Save the valid rows" is your decision.

Running: the machine is producing. Stopped: it stopped and is waiting for someone — the reason shows when the operator enters it on the phone or when the factory sends it. No program: it is free, with no style to make. Maintenance: maintenance has it. No signal: the last reading is older than the minutes-without-reading setting — the factory equipment went down or the machine left the network. No reading: the machine is registered but never sent a reading. The simulated tag marks demo readings.

Tenka does not connect directly to the machine: equipment at the factory (the maker's server or a data-collection program on the network) reads the machines and sends the readings to Tenka in the accepted format. 1) In Settings › Parameters, an administrator fills in the machine collector password (it is stored encrypted and never shown again). 2) Give whoever runs the factory network three things: Tenka's sending address (it is in the implementation guide), the company number and that password. 3) Use the machine name exactly as it is in Tenka's register. 4) Check here in the room: the machine moves from no reading to running or stopped. Repeated readings do not duplicate; wrong ones come back refused with the reason.

The tab shows kg per spindle per hour for each ring frame and yarn against the count reference (process and Ne range). Below 90% lights up. The yardstick comes as a starting point; your company’s range overrides it.

New, Manufacturer "CAD Audaces", "CAD Gerber AccuMark" or "CAD Lectra". For Audaces and Gerber, the path is the folder where the CAD exports the marker report, and the Tenka server must be able to see that folder. For Lectra, the credential goes in the password field (access user:password). The map is the mapping of style and fabric codes. The CAD connectors tab shows whether it is reading or stopped and has "Read now".

The token is stored encrypted and never comes back to the screen: the password field only saves a new one. To change it, paste the new token and save. Whoever sees the integration does not see the token.

Quando o monitor e uma pessoa apontam a mesma máquina e turno, o manual prevalece e a diferença fica registrada; o monitor preenche o que ninguém digitou. O token cifrado nunca é mostrado depois de salvo.

A bad spindle breaks at least twice the machine average in the last 7 days, with 3 or more breaks. "Create maintenance work order" opens one ticket per machine per week with the spindles and what to check (traveller, ring, spindle, tape).

"Simulate a reading" creates an example file that goes through the same importer, with EXEMPLO_ machines and the simulated badge. The real device has not yet been proven with Tenka.

O mapa de campos: cada fabricante nomeia produção, eficiência e rupturas do seu jeito. Confirme com o fabricante qual campo é qual e as unidades (kg ou g, por hora ou por turno). O token é secreto — se mudou no monitor, atualize aqui.

Because its last reading is older than the minutes in the Machine collector: minutes without reading setting (15 by default). It is almost always the factory equipment that went down, the machine's network, or the machine unplugged. Demo readings, with the simulated tag, never show no signal: they show the moment the demo was built.

If the equipment that reads the machines goes 24 hours without sending any reading, Tenkai opens a stopped-integration alert. The same applies to a trade bill sent to the registrar that goes 48 hours without an answer. Before that, the machine shows here as no signal.