[version en cours de rédaction] | [version en cours de rédaction] |
(Page créée avec « {{Tuto Details |Description=<translate>Recovering the bar queue to match the number of bars on transfer table following a crash on winMulti</translate> |Categories=Operati... ») |
|||
Ligne 8 : | Ligne 8 : | ||
}} | }} | ||
{{Introduction | {{Introduction | ||
− | |Introduction=<translate>There have been cases of software crashing on the Stuga front end | + | |Introduction=<translate>There have been cases of software crashing on the Stuga front end software, but the machine will continue to cut the holes and slots on the bar and eject it to the transfer table. |
− | + | This creates the situation that the bar is physically finished, but the software has not registered it as finished. | |
This can lead to confusion for the operator and put the bar queue out of sync, which can lead to wasted profile</translate> | This can lead to confusion for the operator and put the bar queue out of sync, which can lead to wasted profile</translate> | ||
Ligne 18 : | Ligne 18 : | ||
{{Tuto Step | {{Tuto Step | ||
|Step_Title=<translate>Check the bar queue on the saw screen</translate> | |Step_Title=<translate>Check the bar queue on the saw screen</translate> | ||
+ | |Step_Content=<translate>First you need to check out the bar queue to see if it is the same as the actual bars on the transfer table | ||
+ | |||
+ | # Restart winMulti | ||
+ | # Count the total number of bars on the saw infeed and transfer table | ||
+ | # Compare with the number of bars on the saw queue | ||
+ | {{Idea|...If you have some offcuts on the screen, this can help identify the queue position by looking at the length of the offcut}} | ||
+ | |||
+ | If there are more bars actually on the table than on the bar queue screen, follow the process below to add the missing bar to the queue</translate> | ||
+ | }} | ||
+ | {{Tuto Step | ||
+ | |Step_Title=<translate>Open the Bar Edit Screen</translate> | ||
+ | |Step_Content=<translate></translate> | ||
+ | }} | ||
+ | {{Tuto Step | ||
+ | |Step_Title=<translate>Select the Bar Detail Tab</translate> | ||
+ | |Step_Content=<translate></translate> | ||
+ | }} | ||
+ | {{Tuto Step | ||
+ | |Step_Title=<translate>Click "Queue"</translate> | ||
+ | |Step_Content=<translate></translate> | ||
+ | }} | ||
+ | {{Tuto Step | ||
+ | |Step_Title=<translate>Click Yes to confirm you want to create the bar</translate> | ||
|Step_Content=<translate></translate> | |Step_Content=<translate></translate> | ||
}} | }} | ||
{{Notes}} | {{Notes}} | ||
{{PageLang | {{PageLang | ||
+ | |Language=en | ||
|SourceLanguage=none | |SourceLanguage=none | ||
|IsTranslation=0 | |IsTranslation=0 | ||
− | |||
}} | }} | ||
{{Tuto Status | {{Tuto Status | ||
|Complete=Draft | |Complete=Draft | ||
}} | }} |
Recovering the bar queue to match the number of bars on transfer table following a crash on winMulti
Auteur Gareth Green | Dernière modification 23/09/2019 par Gareth Green en cours de rédaction ⧼frevu-button-review-label⧽
Pas encore d'image
Recovering the bar queue to match the number of bars on transfer table following a crash on winMulti
winMulti, Crash, bar queue
There have been cases of software crashing on the Stuga front end software, but the machine will continue to cut the holes and slots on the bar and eject it to the transfer table.
This creates the situation that the bar is physically finished, but the software has not registered it as finished.
This can lead to confusion for the operator and put the bar queue out of sync, which can lead to wasted profileFirst you need to check out the bar queue to see if it is the same as the actual bars on the transfer table
If there are more bars actually on the table than on the bar queue screen, follow the process below to add the missing bar to the queue
en none 0 Draft
Vous avez entré un nom de page invalide, avec un ou plusieurs caractères suivants :
< > @ ~ : * € £ ` + = / \ | [ ] { } ; ? #