CN102664950B - Data communication method between welding power sources and computers - Google Patents
Data communication method between welding power sources and computers Download PDFInfo
- Publication number
- CN102664950B CN102664950B CN201210116783.0A CN201210116783A CN102664950B CN 102664950 B CN102664950 B CN 102664950B CN 201210116783 A CN201210116783 A CN 201210116783A CN 102664950 B CN102664950 B CN 102664950B
- Authority
- CN
- China
- Prior art keywords
- task
- source
- welding current
- computer
- record
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B23—MACHINE TOOLS; METAL-WORKING NOT OTHERWISE PROVIDED FOR
- B23K—SOLDERING OR UNSOLDERING; WELDING; CLADDING OR PLATING BY SOLDERING OR WELDING; CUTTING BY APPLYING HEAT LOCALLY, e.g. FLAME CUTTING; WORKING BY LASER BEAM
- B23K31/00—Processes relevant to this subclass, specially adapted for particular articles or purposes, but not covered by only one of the preceding main groups
- B23K31/02—Processes relevant to this subclass, specially adapted for particular articles or purposes, but not covered by only one of the preceding main groups relating to soldering or welding
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B23—MACHINE TOOLS; METAL-WORKING NOT OTHERWISE PROVIDED FOR
- B23K—SOLDERING OR UNSOLDERING; WELDING; CLADDING OR PLATING BY SOLDERING OR WELDING; CUTTING BY APPLYING HEAT LOCALLY, e.g. FLAME CUTTING; WORKING BY LASER BEAM
- B23K9/00—Arc welding or cutting
- B23K9/095—Monitoring or automatic control of welding parameters
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B23—MACHINE TOOLS; METAL-WORKING NOT OTHERWISE PROVIDED FOR
- B23K—SOLDERING OR UNSOLDERING; WELDING; CLADDING OR PLATING BY SOLDERING OR WELDING; CUTTING BY APPLYING HEAT LOCALLY, e.g. FLAME CUTTING; WORKING BY LASER BEAM
- B23K9/00—Arc welding or cutting
- B23K9/10—Other electric circuits therefor; Protective circuits; Remote controls
- B23K9/1006—Power supply
- B23K9/1043—Power supply characterised by the electric circuit
Landscapes
- Engineering & Computer Science (AREA)
- Mechanical Engineering (AREA)
- Physics & Mathematics (AREA)
- Plasma & Fusion (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Factory Administration (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a data communication method between welding power sources and computers, and belongs to the technical field of welding control. The method includes the steps that a welding power source makes a request to a computer for uploading files; the computer performs task registration based on uploaded requests and generates task records in a task list , and the task records comprise identification (ID) of the welding power source; the computer selects the current task to be executed from the task list, and issues an uploading permitted reply to the welding power source according to the ID of the welding power source in the current task records; the welding power source uploads files to the computer after receiving the reply; and the computer receives the files, determines whether the uploading is finished, logs off the current task records if the uploading is finished, and returns to wait for receiving files if the uploading is not finished. According to the data communication method, uploading requests from a large number of welding power source files are queued through the task list, and network congestion caused by the simultaneous uploading of a large number of files is avoided.
Description
Technical field
The present invention relates to a kind of method of carrying out data communication between source of welding current and computer, particularly relate to the source of welding current and Computer Data Communication method with higher transmission reliability, belong to welding control technology field.
Background technology
Along with the development of source of welding current Digital Control and Internet communication technology, there is the source of welding current with network savvy.The welding parameter that this source of welding current is obtained by network service is uploaded to computer.On this basis, occurred again that welding parameter is saved to the method for its memory by the source of welding current automatically.Welding parameter is saved to the storage mediums such as Flash, SD card of source of welding current inside in the mode of data file.In source of welding current use procedure, welding parameter forms data file in chronological order.Have after the source of welding current of network savvy and computer set up network service, just the data file in its memory can be uploaded to computer.
The source of welding current automatically can record welding data (real time data) in welding process, and uploads in real time and establish with it in the computer of communication connection.But in particular cases, the welding data that the source of welding current produces possibly cannot upload to computer in real time, will be saved in the memory in the source of welding current with the form of file data (file bag) in welding etc. in the wild.After the source of welding current is connected to computer, the source of welding current just needs the file data (history file) that these be have recorded the welding data before networking to upload in computer.While uploading these history files, these sources of welding current also may be in welding process, can produce the current file comprising real-time welding data in real time.Current file is the file data that the real-time welding data of the source of welding current within certain period is formed.
Therefore, create at source of welding current end and upload simultaneously, comprise the file data of history file and current file and the demand of real-time these two classes data of welding data.At computer terminal, under needing the prerequisite processing real-time welding data in real time in preferential guarantee, fast processing file data.But, if the source of welding current of up to a hundred be connected with computer is all working, a large amount of real-time welding data will produced, take most of resource of computer.If wherein also have the source of welding current of tens will ask upload file data, then computer can only process these file datas by a small amount of resource of remainder, easily causes network congestion.
In addition, computer can connect the multiple stage source of welding current simultaneously, from several to up to a hundred.When welding machine Interconnection Scale is less, aforementioned available data file stores and still can normally run with method for uploading.Larger at welding machine Interconnection Scale, such as up to a hundred when, if owing to not having for a long time and compunication, a large amount of history files can be stored in the memory of every platform source of welding current, these a large amount of history files are uploaded to computer by local area network (LAN), and the local net network between the source of welding current and computer can be caused to block.Meanwhile, be limited to Computing performance, the file of the part source of welding current normally cannot receive and processes.
Need a kind of data communications method that can improve between the source of welding current of the reliability of document backup and computer for this reason.
Summary of the invention
The present invention is intended to overcome above-mentioned the deficiencies in the prior art, provides a kind of source of welding current and the Computer Data Communication method that can improve document backup reliability.
Of the present inventionly also provide the welding system and welding manage computer that realize the above-mentioned source of welding current and Computer Data Communication method.
The technical solution adopted in the present invention is as follows:
A kind of source of welding current and Computer Data Communication method, this computer is connected by network with the multiple stage source of welding current, stores the file comprising welding data, it is characterized in that in this source of welding current:
Step 1: this source of welding current by upload request to this computer request upload file;
Step 2: this computer, according to described upload request, carries out task registration, produce task record in task list, and this task record comprises the ID of this source of welding current;
Step 3: the current task that will perform selected by this computer from task list, according to the ID of this source of welding current in this current task record, sends the reply allowing to upload to this source of welding current;
Step 4: after this source of welding current receives this reply, to described computer upload file;
Step 5: this computer receives file, and judge whether to upload complete, completely just enters step 6 if uploaded; Completely wait-receiving mode file is just returned if do not uploaded;
Step 6: nullify this current task record.
The present invention passes through task list, in computer database side, the files passe request from a large amount of source of welding current is ranked, by batch processing, avoid and upload due to heap file and the network congestion caused simultaneously, while raising transmits reliability, also can ensure the file of each source of welding current can be sent in high quality computer database side, there will not be the problems such as packet loss.And, because avoid network congestion, also just decrease hardware resource cost, time cost and human cost that network recovery brings.
Accompanying drawing explanation
Fig. 1 is welding system structural representation of the present invention;
Fig. 2 is task status transition diagram of the present invention;
Fig. 3 is the document backup overall flow figure of first embodiment of the invention;
Fig. 4 is the task registration flow chart of first embodiment of the invention;
Fig. 5 is that the duty cycle of first embodiment of the invention deletes flow chart;
Fig. 6 is the task list schematic diagram of the situation about normally uploading of first embodiment of the invention;
Fig. 7 is that the upload request of first embodiment of the invention is not by the task list schematic diagram of situation responded;
Fig. 8 is the task list schematic diagram of the situation of newly-increased request in the normal upload procedure of first embodiment of the invention;
Fig. 9 is the task list schematic diagram of the situation of the upload procedure appearance exception of first embodiment of the invention;
Figure 10 is the document backup overall flow figure of second embodiment of the invention;
Figure 11 is the task registration flow chart of third embodiment of the invention;
Figure 12 is the task list schematic diagram of the situation about normally uploading of third embodiment of the invention;
Figure 13 is the task registration flow chart of fourth embodiment of the invention;
Figure 14 is the task list schematic diagram that there is the situation of record under the same ID of fourth embodiment of the invention.
Embodiment
As shown in Figure 1, the present invention has been applied to multiple stage, and such as up to a hundred sources of welding current 50 are connected to the welding system of computer 60 and database 70.Every platform source of welding current 50 and computer 60 and can data communication be carried out between computer 60 and database 70.In the present embodiment, computer 60 have the sequence number for storage file sequence number memory 2a, for the file memory 2b of storage file and the task list memory 2c for storing described task list.
Every platform source of welding current 50 after being powered up, just and between computer 60 establishes a communications link, and such as TCP connects.Being no matter the real time data that produces in welding process of the source of welding current 50 or history file, is all connect by same TCP the transmission carrying out data.Computer 60 identifies real time data or history file by the packet header difference of packet.Real time data is then processed in real time, for history file then according to hereinafter described step, process of queuing up in task list.History file transmits with the form of history file or the such file of current file; Real time data is then transmit in the form of data.
When transmitting between the source of welding current 50 and computer 60, adopt 3 kinds of packet header.The first is the packet header (upload request packet header) that the source of welding current 50 asks to computer 60 to comprise in the upload request used during upload file.The second is that real time data uploads packet header.When the source of welding current 50 produces new real time data each second, this real time data can be uploaded to computer 60 in time.Practicality will be used packet header is uploaded when uploading real time data.The third is files passe packet header.The real time data that every 3 minutes of the source of welding current 50 will produce in during this period, passes to computer 60 with file bag (current file) in form.If current file is uploaded limited, such as, be the welding in failed cluster situation, or network interrupts suddenly, these current files will be stored in the source of welding current 50 as history file, are just again uploaded by the source of welding current 50 when network is normal.No matter upload file bag, be current file or history file, all use files passe packet header.By distinguishing the packet header of these three kinds of file bags, computer 60 just can know the instruction type of the source of welding current 50, is upload real time data, or request is uploaded, or upload file.Accordingly, computer 60 carries out the real-time process of real time data, or task registration process, or receives the process of file.
The welding data file of the source of welding current temporally forms document format data, within such as every three minutes, (file produces the cycle) generates the data file (file bag) of an xxx.dat form, be stored in the memory of welding machine inside, such as SD card or Flash chip.The no matter source of welding current and computer whether connected network communication, data file all temporally generates successively, and the file of each file is called its sequence number, the 00001A.dat of such as hexadecimal format.
Database 70 adopts the frequently-used data library softwares such as Oracle, SQL Server, MySQL.Computer 60 creates file task list in a database when bringing into operation data receiver software, stores in a database with the form of tables of data.Task list field comprises device id number, quantity of documents, task registration time, task execution time.As required, the field of task list also can comprise task status, and it acts on and hereinafter illustrates.If the resource of computer 60 is enough, the database that the present invention also can be independent, and is replaced the function of database by computer 60.
Device id number is the ID distributing to each source of welding current, and each source of welding current is assigned unique ID.
Quantity of documents represents the medium file number to be uploaded of this source of welding current, its value can be the sequence number of the current latest document bag (being called for short: current file) of the source of welding current, also can be the difference of the sequence number of the current file of this source of welding current and the sequence number of first non-upload file.What adopt in the present embodiment is the first scheme.Value due to " quantity of documents " is the sequence number (SR of current file
last), and computer 60 end all preserves the sequence number (SR) of the current file of the source of welding current received at every turn, such computer 60 can receive new file automatically from the file (sequence number is SR+1) after its file preserved (sequence number is SR), until receive current file, (sequence number is SR
last).
The task registration time is when the request that computer 60 receives the source of welding current 50 sends the request of file data, carries out the time of task registration.
Task execution time is that the last computer 60 receives and stores the time of the file bag from the source of welding current 50.When computer 60 receives the upload request from the source of welding current 50, the assignment of task execution time is equal with the value of hour of log-on.Afterwards, computer 60 often receives a file bag and just upgrades a task execution time, and keeps hour of log-on constant.In the present embodiment, if the task registration time is equal with task execution time, then illustrate that this task is not responded; If the time of implementation is greater than hour of log-on, then this task present is described.Certainly, if be provided with " task status " field in task list, then can show that this task is in states such as not responded, processing according to the value of this field.Certainly, if there is " task status " field in task list, then the value of " task status " can be utilized to show the treatment state of current task, do not responded, the state such as still process.
Source of welding current task status represents the state residing for source of welding current upload file process.As shown in Figure 2, source of welding current task status is divided three classes (being defined as A, B, C class herein).Category-A is the state (not by responsive state) do not secured permission temporarily after task application uploaded by the source of welding current 50, category-B is that computer 60 replys " allowing to send " but the state of the temporary non-uploading data file of the source of welding current 50 to the source of welding current 50, and C class is the state (processing) just at uploading data file after the source of welding current 50 receives license.The life cycle of each task will defer to the variation tendency of category-A-category-B-C class.After its all data file uploaded by the source of welding current, C generic task state revert to wait state.
< first embodiment >
Fig. 3 illustrates the overall flow figure of first embodiment of the invention.The method of carrying out data communication between the source of welding current of the first embodiment and computer comprises the following steps.
Step 1: source of welding current request sends file data (task requests).
In this enforcement, as long as the source of welding current 50 is connected to network, just periodically ask upload file data (file bag) to computer 60.It is identical that the file being set to RQ cycle produce with the source of welding current file in the present embodiment produces the cycle, is all 3 minutes.Be appreciated that and also according to actual conditions, RQ cycle can be set to the double-length that file produces the cycle.If in 3 minutes, have received computer 60 allow upload reply, then the source of welding current 50 starts to upload; If do not receive the response of computer 60 in 3 minutes, then the source of welding current 50 is just waited for, until 3 minutes send upload request at the expiration again always.
According to actual needs, may not be and periodically send upload request, but send upload request when meeting the trigger condition of setting in advance.Such as, just ask to upload when file size to be uploaded or quantity reach threshold value; Or just ask to upload when pressing a certain button; Or just ask to upload (being suitable for field bonding machine) when network connection establishment being detected.Such as, the source of welding current 50, before asking upload file data to computer 60, first judges whether to need request to send file data.If the file data size in the memory of the source of welding current 50 reaches threshold value, send upload request; If, do not send upload request.Also can be the sequence number of the current file judged in the memory of the source of welding current 50 whether be the file serial number having asked to upload, if it is do not send upload request; If not then sending upload request.
The source of welding current 50 is when asking to send file data, and upload request instruction comprises device id number and quantity of documents.The value of quantity of documents is the sequence number of the latest document (current file) of asking at that time.If the source of welding current 50 did not receive the response from computer 60 in 3 minutes, then again ask when within 3 minutes, expiring.When re-starting upload request, the source of welding current 50 recalculates the value of " quantity of documents " according to the sequence number of current file, to be included in file newly-increased in these 3 minutes.In other words, the value re-starting " quantity of documents " comprised in the upload request instruction of upload request increases by 1 than the value of " quantity of documents " of last upload request.If the source of welding current 50 have received the response from computer 60 in 3 minutes, then carry out files passe.If have current file to produce uploading in way, then the source of welding current produces a new upload request.
Step 2: computer carries out task registration (task registration).
After computer 60 receives the upload request of the source of welding current 50, in the task list of database, produce a task record.In this task record, the task registration time is the time that computer 60 receives this upload request; Task execution time is identical with hour of log-on.If there is " task status " field, then task status is set to A condition (not responded).Hereinafter composition graphs 4 is described in detail.
Step 3: task selected by computer, and allow to upload (select and upload the source of welding current).
After computer 60 task record that selected a collection of source of welding current ID is different in task list, the source of welding current 50 corresponding to this task record sends the reply allowing to upload, and indicates and upload from what sequence number in reply.Specifically, computer 60 is selected a collection of (according to the computing capability of computer 60 in task list, be set as 5 in the present embodiment) task record, computer 60 is according to the source of welding current ID in selected task record, search sequence memory, can know the file packet sequence number (sequence number is SR) of the corresponding source of welding current 50 received.In the instruction of replying to this source of welding current 50, just the notice source of welding current 50 is uploaded from next sequence number (sequence number is SR+1).
Computer 60 can carry out selected current task according to multiple principle.Such as, can select according to the hour of log-on of every bar record, first register and first process.Can certainly be set as, the posterior priority treatment of hour of log-on, namely post-registration first processes.
Also by setting specific field in task list, selected current task can be carried out according to the value of this field.Such as, setting " priority " field, the source of welding current 50 transmission need the file of priority treatment before, in upload request with regard to assigned priority be height; Computer 60, when receiving the high upload request of priority, is preferentially chosen to be current task and processes.This scheme is applicable to the source of welding current of specific demand, and such as the failed cluster source of welding current of long-term continuous firing, only has the of short duration time for upload file, so necessary priority treatment is from the file of these sources of welding current.
Also can set according to the IP address of the source of welding current or sequence number, such as from the task record priority treatment of particular ip address or specific weld power supply sequence number, priority treatment can be carried out like this, to meet the specific demand of these specific weld power supplys to the file of the specific source of welding current.
Also the file size (value of the quantity of documents comprised in upload request, with the difference of the sequence number corresponding with this source of welding current stored in the sequence number memory 2a of computer 60) can uploaded as required is selected.File is larger, more priority treatment.Can ensure that the too much source of welding current of file packet congestion obtains priority treatment like this.
Step 4: source of welding current upload file (files passe).
Step 5: computer judges whether selected task is uploaded complete (uploading complete judgement).
When computer 60 judges the sequence number of the file bag received from the source of welding current 50, time equal with the value of " quantity of documents " field in the current task record stored in its task list memory 2c, computer 60 will judge that task is uploaded complete, enters step 6.
Otherwise, if the value of " quantity of documents " field of the sequence number of the file bag received and current task record not etc., is not then judged as not uploading complete, present.Now, computer 60 notifies that the source of welding current 50 continues upload file bag.
According to the computing capability of the source of welding current, also can be designed as by the source of welding current whether equal with the file serial number uploaded according to its current file sequence number stored, judge whether file bag is uploaded complete thus.
Step 6: computer is nullified and uploaded complete current task record (cancellation task).
When computer 60 judges that the file bag of current task is uploaded complete, this current task record will be deleted from task list.
By step 1 to step 6, achieve without congested files passe between computer 60 and the source of welding current 50, improve speed and the reliability of document backup.
After step 6 nullifies current task record, circulation step can also be increased: judge whether also have task record in task list, if need the task record performed in task list, then return step 3, from task list, select the current task record needing to perform; If there is no pending task in task list, then terminate.Like this, computer 60 will be executed the task all task records in list one by one.
Be described below in conjunction with Fig. 4 task registration flow chart.Computer 60, after the upload request receiving the source of welding current 50, carries out task registration according to the following steps:
Step 21: whether inquiry has existed the task record of this source of welding current
According to the device id number in the upload request instruction of the source of welding current 50, the whether existing record (depositing record) from this source of welding current 50 inquired about by computer 60 in task list, namely the value of device id field be the ID of the source of welding current 50 deposit record.If do not have the task record of No. ID, identical device, then illustrate that computer 60 did not receive the upload request of this source of welding current 50, this is a new upload request, enters step 22.If there is the task record with No. ID, identical device in task list, then think and the upload request having received this source of welding current 50 entered step 23.
Step 22: new upload request is added in task list
For the upload request that computer 60 did not receive, computer 60 can be added to task list.Computer 60 is current time to " hour of log-on " assignment in this task record; Be current time to " time of implementation " assignment; To " task status " assignment A condition; According to the value of " quantity of documents " in the upload request from the source of welding current 50, to " quantity of documents " assignment.Which adds a new task record.
Step 23: judge whether deposited record is responded
In step 21, according to the device id in upload request inquire deposit record when, computer 60 judges that in step 23 whether this hour of log-on having deposited record equal with the time of implementation.
If hour of log-on is equal with the time of implementation, then illustrate that this deposits record, although this task is registered, responded by computer 60 not yet, be in the state waiting for that computer 60 processes always, enter step 24.
Certainly, if be provided with in task list " task status ", then whether the value of basis " task status " is A, just can judge whether this task is responded.
If hour of log-on and the time of implementation unequal, then illustrate that this has been deposited in record present (corresponding source of welding current state B or C), enter step 25.
Step 24: the content of depositing record that renewal etc. are pending
Record is not deposited by what respond for being judged as in step 23, computer 60 is according to the current content with the upload request of identical ID received, upgrade the content of having deposited record, instead of be that current upload request produces new record, can avoid like this producing many task records comprising duplicate contents.Upgrade content specifically: the value value of " quantity of documents " deposited in record being updated to " quantity of documents " in current upload request; " hour of log-on " and " time of implementation " deposited in record is updated to current time respectively.
Record of depositing after renewal is just queued up in task list, waits for the process of computer 60.If (being 6 minutes in the present embodiment, the length of two RQ cycles) is always untreated within a certain period of time, then automatically can be deleted by system.Then, when next RQ cycle arrives, the source of welding current 50 can send upload request again again, and computer 60 enters step 21.
But, one of ordinary skill in the art will appreciate that, the step of " content of depositing record that renewal etc. are pending ", also can be regenerate a record, keep two records within a deletion cycle simultaneously, until the difference that system time and Article 1 have been deposited in record between the time of implementation reaches 10 minutes (the deletion cycle of setting), just Article 1 is deposited record and deleted from task list.
Step 25: judge whether extremely to upload
Judge to have deposited record present in step 23, then further according to current time and time of implementation, judge whether the task process that this has deposited record occurs uploading exception.
If the difference of the time of implementation of the current time of system and current task record, be more than or equal to the normal time of implementation, then illustrate that the execution of this task occurs abnormal, no longer need to wait for, enter step 26; If be less than the normal time of implementation, then illustrate that this task is in normal transmission, enter step 27.
This normal time of implementation is according to setting the running time of computer 60, and the normal time of implementation is more than or equal to computer 60, and to process time needed for All Files bag of once uploading just passable.Be set as 5 seconds in the present embodiment.
Step 26: delete and deposit record, proceed to step 27
Since the task process of having judged to have deposited record in step 25 occurs abnormal, may interrupt, become " dead task ", just directly delete this so in step 26 and deposit record.Can avoid like this retaining " dead task " in task list.
Step 27: set up new task record
Since judged that in step 25 the task process of having deposited record is normal, just generate new task record according to " quantity of documents " (the latest document sequence number) in the current upload request received in step 21 so in step 27.
For having judged that in step 25 having deposited record occurs uploading abnormal situation, according to the current upload request received in step 21, computer 60 has generated new task record for this source of welding current 50 in task list.Like this, deposited the file do not uploaded due to exception in record although aforementioned, can have been uploaded by this new task record.Because the sequence number of the file uploaded preserved by computer 60, it can know according to " quantity of documents " (the latest document sequence number) in the current upload request in step 21 which file needs to upload automatically.Do not cause file to upload because of task abnormity.
Because after depositing the task normal process of record, computer 60 can preserve the sequence number of the file uploaded.It is when performing the new task record generated in step 27, automatically from the file after the file uploaded to receive new file, can not cause and repeat to upload.
Step 21 ~ 27 are utilized to achieve task registration in above-mentioned explanation.But be appreciated that, when not considering to upload appearance exception, step 25 is omissible steps to step 26, can in step 23, judge whether the task record of the described source of welding current is responded, if do not responded, then upgrade the content (refer step 24) of the task record of the described source of welding current; If responded, then set up the new task record (refer step 27) of the described source of welding current.Like this, in step 21 ~ 23, just task registration is completed.
Upper mask body describes the flow process of task registration.Computer 60 can also increase the step of cycle deletion, to avoid such situation: when there is tasks carrying exception, new upload request is not resend (owing to not having new upload request for a long time due to source of welding current catastrophic failure, computer also can not enter into step 21 ~ step 26 and delete), cause this abnormal task to take resource for a long time.Meanwhile, task list also can be avoided long.
The step that cycle deletes as shown in Figure 5.Computer 60 regularly deletes the task record that exceeds the time limit.Deleting cycle set is the cycle longer than the RQ cycle of source of welding current files passe, is set as 10 minutes in the present embodiment.
Within each deletion cycle, computer 60 performs the operation that a subtask is nullified.Computer 60 reads task list, and whether the difference of the time of implementation of comparison system current time and every bar record is greater than the deletion cycle.If be more than or equal to the deletion cycle, then this record is deleted; If be less than the deletion cycle, then retain this record.
Below in conjunction with Fig. 6 to Fig. 9, illustrate the content of task list in often kind of situation.In Fig. 6 to Fig. 9, by start normal cluster at the source of welding current 50 moment before, the file do not uploaded that the source of welding current 50 has stored, is expressed as history file; By the current file constantly produced in welding process after the normal cluster moment, be expressed as " new file ", with the history file before being different from normal cluster.Stricti jurise is said, in new file, except last file is except current file, remaining current file also belongs to history file.Fig. 6 to Fig. 9 represents it is to demonstrate visually like this, the file before networking, how to be sent in computer 60 together with the continuous current file produced.
Being appreciated that also can using last file in Fig. 6 to Fig. 9 as current file, and file is before all as history file.
Fig. 6 illustrates the situation that the source of welding current 50 normally transmits file.
In the case, the source of welding current 50 the initial time of the 1st RQ cycle (certainly, also can be in finish time), can send upload request (being expressed as in figure 6: 1. request uploads 101) to computer 60.This upload request comprises latest document sequence number 101, wherein supposes that 1 to 100 is history files, and 101 is represent the current file comprising real time data produced in a upper RQ cycle (that is, file produces the cycle, and duration is 3 minutes).
Computer 60 end produces new record after receiving the request (101) of the source of welding current 50 in task list, namely in figure 6 1. place that line item (hereinafter referred to as record 1.).Record the first field value is 1. the ID (being 1 in the present embodiment) of the source of welding current 50; Quantity of documents field value is the sequence number " 101 " of current file, hour of log-on field value is present system time " T10 ", time of implementation field value is similarly " T10 " (that is, hour of log-on is identical with the time of implementation, represents that this record is not responded).Then, computer 60 sends the reply (2. allowing to upload) allowing to upload to the source of welding current 50, tell that the source of welding current 50 is unwrapped the beginning from the file that sequence number is 1 and uploaded.
After the source of welding current 50 receives the reply allowing to upload, to computer 60 upload file.40 file bags (this determines according to the hardware configuration of the source of welding current and computer and serviceability) once can only be uploaded in this hypothesis.Therefore, the source of welding current 50 uploads to computer 60 the file bag (being expressed as in Fig. 6: 3. upload 1 ~ 40) that sequence number is 0 ~ 40.After computer 60 receives 1 ~ 40 file bag, more new record 1. in time of implementation be " T11 ", obtain recording 3..Then, the file bag (being expressed as in Fig. 6: 4. upload 41 ~ 80) of 41 ~ 80 uploaded again by the source of welding current 50, the corresponding more new record of computer 60 3. in time of implementation be " T12 ", obtain recording 4..Remaining file bag uploaded by the last source of welding current 50, and sequence number is the file bag (being expressed as in Fig. 6: 5. upload 81 ~ 101) of 81 ~ 101.The corresponding more new record of computer 60 4. in time of implementation be " T13 ", arrive record 5..
Now, computer 60 detects in the file bag received, and comprises the file bag that sequence number is 101, equal with the value of " quantity of documents " in task record, then nullify this task 101.
By the time the 2nd RQ cycle (second 3 minutes) starts, and the source of welding current 50 sends request, and the file bag that sequence number is 102 is uploaded in request.Similar, computer 60 can generate new record (being expressed as record in Fig. 6 6.), and replys: allow upload file bag 102.
After the source of welding current 50 receives reply, upload file bag 102.After computer 60 receives file bag 102, amendment record 6. in time of implementation be present system time " T14 ", obtain recording 8..Afterwards, computer 60 is according to the value of the quantity of documents recorded 6., and the sequence number of the file bag 102 received, and judges that file data is uploaded complete, so nullify task 102.Certainly, also can after receiving file bag 102, direct cancellation task 102, and do not need more new record 6. to obtain recording 8. this step.
Then, enter the 3rd RQ cycle, the source of welding current 50 and computer 60 carry out similar process.
Introduce the situation illustrating and again ask below.In the figure 7, the source of welding current 50 sends request (201), and 1. computer 60 produces record.In whole 1st RQ cycle, computer 60 does not send the reply allowing to upload to the source of welding current 50.Until enter the 2nd RQ cycle, the source of welding current 50 produces current file 202, as new file together with file 201, waits to be sent.
The source of welding current 50 sends upload request 202 at the 2nd RQ cycle.Now, computer 60 is after receiving upload request 202, inquire in task list the task record existed from the same source of welding current 50 (ID is 1) and 1. (deposit record), and judge to record the hour of log-on equal with the time of implementation (this represents that this task is not responded) 1..So computer 60 is new record content 1. more, quantity of documents is updated to the current file sequence number 202 comprised in upload request 202, hour of log-on and time of implementation is updated to present system time T20P respectively, becomes record 2..
Then, computer 60 sends the reply allowing to upload 151.After the source of welding current 50 receives reply, starting to upload sequence number is 151 ~ 190 file bags.After computer 60 receives 151 ~ 190 file bags, more new record 2. in time of implementation, become record 4..Then, the source of welding current 50 transmit Sequence Number be 191 ~ 202 file bag, after computer 60 receives, more the new record time of implementation 4., become record 5..Finally nullify task 202.
The situation of newly-increased request in normal upload procedure is described below in conjunction with Fig. 8.
In the 1st RQ cycle, the source of welding current 50 normally uploads file bag 251 ~ 290, and 3. computer 60 generates record.Now, due to cause specifics such as network disconnection, power-off or the faults of the source of welding current 50 own, upload and have ceased.Or owing to just entering the 2nd RQ cycle after the source of welding current 50 upload file bag 251 ~ 290, create the current file 302 in new file immediately, needs request is uploaded (sequence number 302 of current file).
After computer 60 receives upload request 302, in task list, inquire the record that there is identical ID, i.e. task 301 (record 3.).Judge that hour of log-on and the time of implementation of task 301 are inconsistent further, and both differences are less than 5 seconds normal times of implementation (the maximum processing time of the normal process task set in the present embodiment); Belong to processing of task.Now, computer 60 is according to upload request 302, and newly-increased one is recorded 302 (hour of log-on and time of implementation are present system time T30P), instead of upgrades task record 301.In other words, as the record in Fig. 8 4. shown in, now having two ID to be the task record of 1 in task list, is task record 301 and task record 302 respectively.
So known by search sequence memory 2a and receive the file bag that sequence number is 290, when running resource and allowing, computer 60 just sends the reply allowing to upload 291 to the source of welding current 50.After the source of welding current 50 receives reply, upload from 291.But, be now continue record 301 of executing the task, so it is file bag till 301 that the source of welding current 50 only uploads to sequence number, and do not upload the file bag that sequence number is 302.Computer 60 receives after sequence number is the file bag of 301, judges that task record 301 is uploaded complete, just nullifies task record 301.Then, computer 60 reselects current task in task list.If choose the task 302 of same ID (ID is 1), then send the reply allowing to upload 302 to the source of welding current 50.
The source of welding current 50 after uploading sequence number and being the file bag of 301, if receive computer 60 allow to upload 302 reply, then start to upload the file bag that sequence number is 302.After computer 60 receives file bag 302, nullify task 302.
Such ID be 1 task be disposed, computer 60 selects current task to process again from task list.
The process under abnormal conditions is there is below in conjunction with the transmission of Fig. 9 supporting paper bag.
At the 1st RQ cycle, normally transmit between the source of welding current 50 and computer 60, but just upload a part of file bag.That is, the file bag that sequence number is 301 is uploaded in request, and reality only uploads to the file bag that sequence number is 290.
Now, occur Network Abnormal, the source of welding current 50 is at the 2nd RQ cycle request upload file bag 302.Computer 60, according to flow process described in Fig. 8, increases task record 302 newly.Afterwards, the reply of computer 60 is not received at the whole 2nd RQ cycle source of welding current 50.
After entering the 3rd RQ cycle, the source of welding current 50 creates current file 303, and uploads 303 to computer 60 request.Computer 60 still just increases task record 303 newly in task list, does not send reply to the source of welding current 50.
At this moment delete period expires, in computer 60 pairs of task lists, all records scan, and find out the record of satisfied deletion condition, and delete these records.Deletion condition in the present embodiment is, present system time is greater than the deletion cycle with the difference of the value of the time of implementation in record.In the present embodiment, the setting deletion cycle is more than or equal to two RQ cycles, is namely more than or equal to 6 minutes, can certainly be set as different values according to actual conditions, such as 10 minutes, or 9 minutes.Therefore, in fig .9, the time of implementation of task record 301 remains T31 always, and the difference of present system time and T31 has reached 6 minutes deletion cycles, therefore, and computer 60 suppressing exception task 301.Task 302 and task 303 do not meet deletion condition, then retain.
When entering the 4th RQ cycle, the source of welding current 50 produces current file 304, please uploads 304 to computer 60 request.Computer 60 is newly-increased task record 304 (6. representing with record in fig .9) in task list.Because now network has recovered normal, the current task that computer 60 has processed having deposited from task list and having selected in record 302,303 and 304.
In the present embodiment, computer 60, according to the priority of hour of log-on, selects task 302 for current task from all tasks of task list.Computer 60 sends the reply allowing to upload 291 to the source of welding current 50.So the source of welding current 50 starts normally to upload 291 ~ 302.
It is after the file bag of 302 that computer 60 receives sequence number, judges that task 302 completes, and nullifies task 302.And then new task is selected from all tasks of task list, complete all tasks gradually, comprise task 303 and 304, and nullify.
In the first embodiment, in the task list of computer 60, many task records may be there are in same ID (the same source of welding current), the task record of the task record of these same ID with other ID mixes by computer 60, according to each bar task record hour of log-on successively or priority etc. sort and select current task, perform one by one.
Because each bar task record of same ID exists inclusion relation, namely register the value of the quantity of documents in posterior task record, be less than the value of the quantity of documents registering preceding task record scarcely.If adopt hour of log-on first to queue up afterwards, computer 60 preferentially can perform the preceding task record of registration, the task record that namely value of quantity of documents is less; Then computer 60 just can perform the larger task record of the posterior number of files value of registration.If computer 60 preferentially performs the posterior task record of registration of same ID, all task records of the same ID before the posterior task record of registration just disposablely can be completed.
Visible, in a first embodiment owing to selecting the mode of current task different, may cause: the task that originally can once be finished, is divided into twice and performs, thus reduce execution efficiency.
< second embodiment >
For simplicity's sake, below aspects different from the first embodiment in the second embodiment is only described.
As shown in Figure 10, after computer 60 carries out task registration as the step 2 of the first embodiment, judge to register posterior record all records of step 3a from same ID, select that this registration is posterior is recorded as current task, process.
As in the first embodiment, multiple record may be produced for same ID in the task registration of step 2.Computer 60 is when selecting current task, and the hour of log-on of each bar record of more same ID or quantity of documents, hour of log-on, at rear or that quantity of documents is maximum record, is chosen as current task by computer 60 and processes.
Meanwhile, contain the file serial number of the preceding record of hour of log-on owing to registering posterior record, computer 60 performs the posterior task of registration, just no longer needs to perform the preceding task of other hour of log-on.Therefore selected registration is posterior be recorded as current task after, other hour of log-on preceding task of computer 60 under step 3a deletes this ID.Or after the posterior task of this hour of log-on that is finished, all records (because the executed of hour of log-on posterior task is complete, also just together deleted) of this ID deleted by computer 60.
In a second embodiment, overstocking under task list can demonstrate a certain ID of task is how many, computer 60 is when selecting task record, ID can be selected according to the task record quantity overstock under each ID, and then from all tasks this ID, select that hour of log-on is posterior is recorded as current task.Like this, can the task of the more source of welding current of priority treatment backlog, or distribute more resource for the source of welding current that backlog is more.The source of welding current upload file that preferential permission backlog is more, can ensure that the History file data lacking the more source of welding current is preferentially uploaded to computer, ensures that history file form realizes the complete of data faster like this.
< the 3rd embodiment >
For simplicity's sake, only aspects different from the first embodiment in the 3rd embodiment is described below.
Figure 11 and Figure 12 illustrates, the registered task flow process 2a different from the registered task flow process 2 in the first embodiment.In step 25a, for by what respond, the record namely processed, judges whether to occur uploading exception.If there is exception, then delete already present record, and newly-increased current upload request is in task list.If not abnormal, then upgrade the content of this already present record, instead of newly-increased record.
Specifically as shown in figure 12, suppose in the task list of computer 60, to have there are two task records that ID is 1 and 2.Wherein, the quantity of documents of the task record of ID=1 is 300, and hour of log-on and time of implementation are respectively T30, are namely in not by responsive state.Now enter the 1st RQ cycle, computer 60 receives from the source of welding current 50 (ID=1) upload request 301.So the task record of ID=1 inquired about by computer 60 in task list.Because the task record (task record 300) of ID=1 is in not by responsive state, enter step 24, computer 60 upgrades the content of task record 300: quantity of documents is updated to 301, and hour of log-on and time of implementation are updated to T30P respectively.Like this, in task list, remain 2 records, wherein ID be 1 task record be updated to record 301.
When computer 60 receives 251 ~ 290 file bag that the source of welding current 50 uploads, the time of implementation of its more new record 301 is T31, represents that this record has been the state in process.Then enter the 2nd RQ cycle, computer 60 receives the upload request 302 from the source of welding current 50.Computer 60 is learnt according to the judgement in step 25a, the task record 301 of ID=1 is in normal delivery status (difference of present system time and time of implementation is less than the normal time of implementation), so upgrade the content of task record 301: quantity of documents is updated to 302, hour of log-on and time of implementation are updated to present system time T30Q respectively.
291 ~ 302 file bags uploaded by the source of welding current 50, finish the work 302.Task 302 nullified by computer 60.
As can be seen here, in the third embodiment, for not by responding of task and normally transmitting of task, being all when there is new upload request, upgrading the content not by the task record responded and the task record normally transmitted according to the content of new upload request.For transmitting abnormal task, being then when there is new upload request, deleting this and uploading abnormal task record, and carrying out a newly-increased task record according to the content of new upload request.A record is only had keep same ID thus in task list under.
Owing to only having a record under same ID, the 3rd embodiment is shorter than the task list of the first embodiment, and search efficiency is high.But, because also adopt the mode of renewal (instead of mode of newly-increased task record in the first embodiment) to the normal task record transmitted, the value of the quantity of documents upgrading task record in task processes can be caused.Compared with the first embodiment, the amount of information of the 3rd embodiment task list will be lacked, such as, in the first embodiment, the task number of the source of welding current of certain ID can embody this ID source of welding current and how long waited for after first time task registration, and this point cannot be embodied in the third embodiment, this can make the strategy of computer Activate Task List to lack.
< the 4th embodiment >
Illustrate the task registration flow process 2b being different from the first embodiment of the 4th embodiment in fig. 13.
In step 21, when computer 60 receives the new upload request of the source of welding current 50, whether computer 60 exists task record under judging same ID.Task record not under this ID is then the newly-increased task record (step 22) of this ID; If there is the task record of this ID, then upgrade the content (step 23b) of this already present task record.
By the task registration step 2b of the 4th embodiment, can be implemented in task list, same ID only has a task record all the time.Computer 60 select current task time, can according to the priority level of ID the task of the source of welding current (such as, the source of welding current of specific region) of some particular/special requirement of priority treatment; Also file bag minimum number to be uploaded or at most (such as can be selected according to the quantity of file bag to be uploaded, the difference of the paid-in file packet sequence number stored in the value of " quantity of documents " in task record and file packet memory, the quantity of the larger explanation of difference file to be uploaded bag is more) the task of the source of welding current.
Specifically as shown in figure 14, suppose in the task list of computer 60, to have there are two task records that ID is 1 and 2.Wherein, the quantity of documents of the task record of ID=1 is 300, and hour of log-on and time of implementation are respectively T30, are namely in not by responsive state.Now enter the 1st RQ cycle, computer 60 receives from the source of welding current 50 (ID=1) upload request 301.So the task record of ID=1 inquired about by computer 60 in task list.Because the task record (task record 300) of ID=1 is in not by responsive state, enter step 23b, computer 60 upgrades the content of task record 300: quantity of documents is updated to 301, and hour of log-on and time of implementation are updated to T30P respectively.Like this, in task list, remain 2 records, wherein ID be 1 task record be updated to task 301 (record 1.).
When computer 60 receives 251 ~ 290 file bag that the source of welding current 50 uploads, the time of implementation of its more new task 301 is T31, represents that this record has been the state in process.Then enter the 2nd RQ cycle, computer 60 receives the upload request 302 from the source of welding current 50.The task record of ID=1 inquired about by computer 60 in task list, so the content of more new task 301: quantity of documents is updated to 302, hour of log-on and time of implementation is updated to present system time T30Q respectively, obtains recording 4..
291 ~ 302 file bags uploaded by the source of welding current 50, finish the work 302.Task 302 nullified by computer 60.
As can be seen here, the difference of the 4th embodiment and the 3rd embodiment is, for not by responding of task, normal transmitting of task and the task of transmitting exception, being all when there is new upload request, upgrading the content of this record according to the content of new upload request.4th embodiment advantage is that the task record number in computer is equal with welding machine quantity, task record corresponding to existing ID only need be upgraded during the new task requests of each process, algorithm realization is simple, but because task record cannot embody the time of this source of welding current first application task registration, also cannot embody this source of welding current and whether shut down or network interruption.
Certainly, as the variation of the 4th embodiment, for not by responding of task, normal transmitting of task and the task of transmitting exception, also can be when there is new upload request, record under already present same ID is deleted, and sets up new record according to the content of new upload request.
Above, with reference to detailed or specific execution mode, describe the present invention, but those skilled in the art understand: various change and correction can be carried out under the prerequisite not departing from spirit of the present invention and scope.
Claims (10)
1. carry out a method for data communication between the source of welding current and computer, this computer is connected by network respectively with the multiple stage source of welding current, stores the file comprising welding data, said method comprising the steps of in this source of welding current:
Task requests step: this source of welding current by upload request to this computer request upload file;
Task registration step: this computer, according to this upload request, carries out task registration, produce task record in task list, and this task record comprises the ID of this source of welding current;
Select and upload source of welding current step: the current task record that will perform selected by this computer from this task list, according to the ID of this source of welding current in this current task record, sends the reply allowing to upload to this source of welding current;
Files passe step: this source of welding current is to this computer upload file;
Upload complete determining step: this computer receives this file, and judge whether to upload complete, completely just enter next step if uploaded; Completely just notify that this source of welding current continues to upload if do not uploaded;
Nullify task step: nullify this current task record.
2. carry out the method for data communication as claimed in claim 1 between the source of welding current and computer, it is characterized in that,
Described file has sequence number respectively, the sequence number of the current file of the described source of welding current is comprised in described upload request, also comprise the sequence number of this current file in described task record, the sequence number of this current file and the ID corresponding stored of the described source of welding current are in described task record.
3. carry out the method for data communication as claimed in claim 2 between the source of welding current and computer, it is characterized in that,
Upload in complete determining step described, the sequence number of the file that described computer receives, if identical with the sequence number of the current file in described current task record, be then judged as uploading complete; If be less than the sequence number of the current file in described current task record, be then judged as not uploading complete.
4. the source of welding current any one of claims 1 to 3 as described in claim and carry out the method for data communication between computer, is characterized in that,
Described task registration step comprises the following steps:
Step 21: inquire about the task record that whether there is the described source of welding current in described task list, if there is no the task record of the described source of welding current, then enter step 22; If there is the task record of the described source of welding current, enter step 23;
Step 22: described upload request is added in this task list;
Step 23: judge whether the task record of the described source of welding current is responded, if the task record of this source of welding current is not responded, then enters step 24, if the task record of this source of welding current is responded, then enters step 27;
Step 24: the content upgrading the task record of this source of welding current;
Step 27: described upload request is added in this task list.
5. carry out the method for data communication as claimed in claim 4 between the source of welding current and computer, it is characterized in that,
In described step 23, if judge to be responded, then enter step 25;
Step 25: judging whether the task record of the described source of welding current occurs uploading exception, if there is uploading exception, then enters step 26, if do not occur uploading exception, then entering step 27;
Step 26: the task record deleting this source of welding current, enters step 27 afterwards;
Step 27: this upload request is added in this task list.
6. carry out the method for data communication as claimed in claim 5 between the source of welding current and computer, it is characterized in that,
Hour of log-on field and time of implementation field is also comprised in described task record,
When registering, the value of this hour of log-on field is identical with the value of this time of implementation field;
When described computer receives file, be present system time with regard to upgrading the value of this time of implementation field;
Judge whether to occur in described step 25 to upload abnormal referring to, the value of the time of implementation field in present system time and described task record, if both differences are greater than the normal time of implementation, is then judged as occurring uploading exception; If be less than or equal to the normal time of implementation, be then judged as not occurring uploading exception.
7. the source of welding current any one of claims 1 to 3 as described in claim and carry out the method for data communication between computer, is characterized in that,
Described task registration step comprises the following steps:
Step 21: inquire about the task record that whether there is the described source of welding current in described task list, if do not had, then enter step 22, if there is the task record of this source of welding current, then enter step 23;
Step 22: described upload request is added in task list;
Step 23: judge whether the task record of the described source of welding current is responded, if the task record of this source of welding current is not responded, then enters step 24, if the task record of this source of welding current is responded, then enters step 25a;
Step 24: the content upgrading the task record of this source of welding current;
Step 25a: judge whether the task record of this source of welding current occurs uploading exception, if the task record of this source of welding current occurs uploading exception, then enters step 26, if the task record of this source of welding current does not occur uploading exception, then enter step 24;
Step 26: the task record deleting this source of welding current, enters step 27 afterwards;
Step 27: this upload request is added in task list.
8. the source of welding current any one of claims 1 to 3 as described in claim and carry out the method for data communication between computer, is characterized in that,
Described task registration step comprises the following steps:
Step 21: inquire about the task record that whether there is the described source of welding current in described task list, if there is no the task record of this source of welding current, then enter step 22, if there is the task record of this source of welding current, enters step 23b;
Step 22: described upload request is added in task list;
Step 23b: according to the content of this upload request, upgrades the content of the task record of this source of welding current.
9. carry out the method for data communication as claimed in claim 4 between the source of welding current and computer, it is characterized in that,
Selected upload in source of welding current step described, described computer, from all records of the same ID described task list, judges the posterior record of hour of log-on, selects that this hour of log-on is posterior is recorded as described current task record; And other records deleted under this same ID.
10. one kind realizes the welding system of the method for carrying out data communication between the source of welding current according to claim 1 and computer.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210116783.0A CN102664950B (en) | 2012-04-18 | 2012-04-18 | Data communication method between welding power sources and computers |
| PCT/CN2013/073688 WO2013155935A1 (en) | 2012-04-18 | 2013-04-03 | Method for performing data communication between welding power source and computer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210116783.0A CN102664950B (en) | 2012-04-18 | 2012-04-18 | Data communication method between welding power sources and computers |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102664950A CN102664950A (en) | 2012-09-12 |
| CN102664950B true CN102664950B (en) | 2015-01-07 |
Family
ID=46774359
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210116783.0A Active CN102664950B (en) | 2012-04-18 | 2012-04-18 | Data communication method between welding power sources and computers |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102664950B (en) |
| WO (1) | WO2013155935A1 (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102664950B (en) * | 2012-04-18 | 2015-01-07 | 唐山松下产业机器有限公司 | Data communication method between welding power sources and computers |
| CN103607473A (en) * | 2013-11-29 | 2014-02-26 | 深圳市航盛电子股份有限公司 | Vehicle-mounted terminal data transmitting and processing method and system |
| WO2015168855A1 (en) * | 2014-05-06 | 2015-11-12 | 唐山松下产业机器有限公司 | Welding power source management system and management method therefor |
| US10543554B2 (en) * | 2014-12-05 | 2020-01-28 | Lincoln Global, Inc. | Welding assembly for high-bandwidth data communication |
| US20160158868A1 (en) * | 2014-12-05 | 2016-06-09 | Lincoln Global, Inc. | Welding assembly for high-bandwidth data communication |
| CN110971533B (en) * | 2018-09-30 | 2023-02-03 | 京东方科技集团股份有限公司 | Method, server apparatus, client apparatus, and medium for data communication |
| CN111327406A (en) * | 2020-03-03 | 2020-06-23 | 深圳市麦格米特焊接技术有限公司 | Data communication method and device of welding power supply equipment and welding power supply equipment |
| CN112487282A (en) * | 2020-11-04 | 2021-03-12 | 山东中创软件商用中间件股份有限公司 | Business processing condition monitoring method and device, electronic equipment and storage medium |
| CN117773281B (en) * | 2024-02-18 | 2024-05-03 | 苏芯物联技术(南京)有限公司 | Welding state bidirectional sliding re-detection method based on historical data supplementary transmission |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1525896A (en) * | 2001-01-25 | 2004-09-01 | 林肯电气公司 | System and method providing distributed welding architecture |
| CN101299770A (en) * | 2008-03-05 | 2008-11-05 | 中科院嘉兴中心微系统所分中心 | Method for processing cooperation information of wireless sensor network |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6405340B1 (en) * | 1999-07-02 | 2002-06-11 | Ericsson Inc. | Flexible method of error protection in communications systems |
| US9138825B2 (en) * | 2005-10-07 | 2015-09-22 | Illinois Tool Works Inc. | Wireless communication system for welding-type devices |
| CN102371414A (en) * | 2010-08-20 | 2012-03-14 | 中国海洋石油总公司 | Network-based pipeline all-position welding control system |
| CN102664950B (en) * | 2012-04-18 | 2015-01-07 | 唐山松下产业机器有限公司 | Data communication method between welding power sources and computers |
-
2012
- 2012-04-18 CN CN201210116783.0A patent/CN102664950B/en active Active
-
2013
- 2013-04-03 WO PCT/CN2013/073688 patent/WO2013155935A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1525896A (en) * | 2001-01-25 | 2004-09-01 | 林肯电气公司 | System and method providing distributed welding architecture |
| CN101299770A (en) * | 2008-03-05 | 2008-11-05 | 中科院嘉兴中心微系统所分中心 | Method for processing cooperation information of wireless sensor network |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2013155935A1 (en) | 2013-10-24 |
| CN102664950A (en) | 2012-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102664950B (en) | Data communication method between welding power sources and computers | |
| CN103370917B (en) | Message treatment method and server | |
| CN105302676B (en) | Active and standby the mechanism data transmission method and device of a kind of distributed file system | |
| US20100262960A1 (en) | Communication Terminal | |
| CN102136941B (en) | Method, device and system for data backup of integrated access device | |
| JP2012221004A (en) | Parallel computer system and program | |
| US8898312B2 (en) | Element terminal and communication system | |
| US8458379B2 (en) | Information processing program, method, and transfer processing device | |
| CN111447248A (en) | File transmission method and device | |
| CN112532704A (en) | Data transmission method and device, electronic equipment and storage medium | |
| CN111400041A (en) | Server configuration file management method and device and computer readable storage medium | |
| CN104793981B (en) | A kind of online snapshot management method and device of cluster virtual machine | |
| CN103856511A (en) | Data packet upload method, client terminal, nodes, information server and system | |
| CN106339176B (en) | Intermediate file processing method, client, server and system | |
| CN103186536A (en) | Method and system for scheduling data shearing devices | |
| CN110417876A (en) | Node server and main control device in session method, distributed system | |
| CN104737505A (en) | Routing method based on cache and route node | |
| CN104243473A (en) | Data transmission method and device | |
| CN105119964A (en) | File storage via physical block addresses | |
| CN103795810A (en) | Data distribution system and method and central server of data distribution system | |
| CN105912477B (en) | A kind of method, apparatus and system that catalogue is read | |
| CN104735097A (en) | Information collecting method and system | |
| CN105591776B (en) | The active/standby link switchover method and apparatus of SDN network equipment | |
| CN113721938A (en) | Edge-edge cooperative task processing method, device and system suitable for power Internet of things | |
| CN109445717B (en) | Data storage method and device during dual-computer backup |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |