I'm not trying to do anything fancy. Here's an example of what I'm trying to do: OPEN CP0006 UPLOAD auto UPLOAD CHECKPOINT 60 CLOSE OPEN CP0009 UPLOAD auto UPLOAD CHECKPOINT 60 CLOSE OPEN CP000A UPLOAD auto UPLOAD CHECKPOINT 60 CLOSE ... EXIT I am getting what appear to be random upload errors. Steve Shimp Maintenance & Systems Engineer ExxonMobil Paulsboro Lube Plant phone: 856.224.5059 cell: 609.820.8501 fax: 856.224.5030 email: steve.shimp@xxxxxxxxxxxxxx <BDONATOD@REPS OLYPF.COM> Sent by: To foxboro-bounce <foxboro@xxxxxxxxxxxxx> @freelists.org cc Subject 03/07/06 06:53 Re: [foxboro] iccdrvrtsk upload PM error Please respond to foxboro@freeli sts.org Steve, As when you make an Upload and exit the ICC a Checkpoint is made, I want to ask you if you are running another similar Upload script afterward such that you give no time to complete the Checkpoint before exit, trying to access the same CP. In that case you can set the time you delay the Checkpoint by using the "ICCchkpt" function, plus the delay time. Would you mind mailing the script you are runnig? I think that would help. If it does not bother you. Sorry if I misunderstood something. Regards, Bernardo. -----Mensaje original----- De: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] En nombre de Doucet, Terrence Enviado el: martes, 07 de marzo de 2006 15:27 Para: foxboro@xxxxxxxxxxxxx Asunto: Re: [foxboro] iccdrvrtsk upload error Steve, Assuming that the network is ok and the AW you are using has up to date configuration for all CP's and the AW has no big programs running from time to time, look at the CP loading. From station display Total CP Load, Compound Proc Ocerruns, OM Load, OM overruns Any relationship with these numbers and stations that you cannot complete an upload? Did you check the time / date on the work file to see if anything was written? Terry -----Message d'origine----- De=A0: foxboro-bounce@xxxxxxxxxxxxx = [mailto:foxboro-bounce@xxxxxxxxxxxxx] De la part de = steve.shimp@xxxxxxxxxxxxxx Envoy=E9=A0: March 7, 2006 1:05 PM =C0=A0: foxboro@xxxxxxxxxxxxx Objet=A0: Re: [foxboro] iccdrvrtsk upload error Thanks for the suggestions. The problem is very odd since I can successfully upload some stations but not others, and it seems inconsistent. I am running iccdrvr.tsk on an AW that does not host any stations, and again, some work fine and others fail. Steve Shimp Maintenance & Systems Engineer ExxonMobil Paulsboro Lube Plant phone: 856.224.5059 cell: 609.820.8501 fax: 856.224.5030 email: steve.shimp@xxxxxxxxxxxxxx foxboro-bounce@xxxxxxxxxxxxx wrote on 03/07/2006 11:36:22 AM: > Steve, > I would try to perform the upload first from the command line on the = =3D > host of your CP. Then you can be certain that you are not impeded by = =3D > network communications. =3D20 > > After you get it working on the command line, then build a script and = =3D > make it work. ( Batch file if host is Microsoft) =3D20 > > The following was recently tested on an AW70 with controls > > cd /opt/fox/ciocfg/api > > iccdrvr.tsk -o my_log.txt =3D20 > > (my_log.txt will contain success or error statements) > > open PWLBUG UPLOAD fox > > (insert your letterbug for PWLBUG) > > upload > > close > > exit > > Depending on the block load of your CP, this could take a long time. > Check the work file (PWLBUG.wf) date to see if it is refreshing to > the current time / date, then you know it is working. > On MS host there are some batch file restrictions that will cause you > to build two files, call them UL.bat and UL.dat > > UL.bat > ------- > > cd \opt\fox\ciocfg\api > call iccdrvr.tsk -o my_log.txt -i ul.dat > > > > ul.dat > ------- > > open PWLBUG UPLOAD fox > upload > close > exit > > > > I have not written code for a Unix host, but the same concept should = =3D > apply. > > Regards, > > Terry > > > -----Message d'origine----- > De=3DA0: foxboro-bounce@xxxxxxxxxxxxx =3D > [mailto:foxboro-bounce@xxxxxxxxxxxxx] De la part de =3D > steve.shimp@xxxxxxxxxxxxxx > Envoy=3DE9=3DA0: March 7, 2006 11:03 AM > =3DC0=3DA0: foxboro@xxxxxxxxxxxxx > Objet=3DA0: Re: [foxboro] iccdrvrtsk upload error > > I am simply feeding "upload" to the iccdrvr.tsk, not "upload all". > > Could the upload be failing because there is a change occurring - say = =3D > t=3D3D > o a > string variable - during the upload? > > > Steve Shimp > Maintenance & Systems Engineer > ExxonMobil Paulsboro Lube Plant > phone: 856.224.5059 cell: 609.820.8501 fax: 856.224.5030 > email: steve.shimp@xxxxxxxxxxxxxx > > foxboro-bounce@xxxxxxxxxxxxx wrote on 03/07/2006 10:20:32 AM: > > > Sascha Wildner wrote: > > > steve.shimp@xxxxxxxxxxxxxx wrote: > > > > > >>I am getting the following error when trying to automate a CP =3D > uploa=3D3D > d > with > > >>the iccdrvrtsk: > > >>"ICCupload error class =3D3D3D 20 error =3D3D3D 112 text =3D3D3D = =3D > ICCupload: err=3D3D > or -30 on > > >>upload all" > > > > > > > > > And damn right it is :) because you probably don't have a compound > > > called 'all'. Error -30 is EQEMPTY ("Change queue is empty", see > > > /usr/include/fox/om_ecode.h). > > > > > > iccdrvr.tsk documentation (B0193NE) will tell you that the UPLOAD > > > command will only work on a block or a compound but not on a CP. > > > > > > Known bug, I don't think it will ever be fixed. No, wait! It's > > > documented, hence it's a feature. :) > > > > > > > Oops, sorry for the noise. :) > > > > In fact, the documentation says just typing "upload" should be =3D > enough=3D3D > to > > upload all compounds in the station. Did you type "upload all" or > "upload"? > > > > -- > > Sascha Wildner > > erpicon Software Development GmbH > > Neusser Str. 724-726 > > 50737 K=3D3DF6ln > > Germany > > > > Phone: +49 221 9746069 > > Fax: +49 221 9746099 > > eMail: swildner@xxxxxxxxxx > > > > > > =3D > = _____________________________________________________________________=3D 3= D > __ > > This mailing list is neither sponsored nor endorsed by Invensys =3D > Proce=3D3D > ss > > Systems (formerly The Foxboro Company). Use the info you obtain here = =3D > =3D3D > at > > your own risks. Read =3D > http://www.thecassandraproject.org/disclaimer.ht=3D3D > ml > > > > foxboro mailing list: =3D > //www.freelists.org/list/foxbo=3D3D > ro > > to subscribe: =3D > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D=3D3D > join > > to unsubscribe: =3D > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dl=3D3D > eave > >=3D3D > > > =3D20 > =3D20 > = _______________________________________________________________________ > This mailing list is neither sponsored nor endorsed by Invensys = Process > Systems (formerly The Foxboro Company). Use the info you obtain here = at > your own risks. Read = http://www.thecassandraproject.org/disclaimer.html > =3D20 > foxboro mailing list: = //www.freelists.org/list/foxboro > to subscribe: =3D > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin > to unsubscribe: =3D > mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave > =3D20 > > > = _______________________________________________________________________ > This mailing list is neither sponsored nor endorsed by Invensys = Process > Systems (formerly The Foxboro Company). Use the info you obtain here = at > your own risks. Read = http://www.thecassandraproject.org/disclaimer.html > > foxboro mailing list: = //www.freelists.org/list/foxboro > to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin > to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave > =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave AVISO LEGAL: Esta informacion es privada y confidencial y esta dirigida unicamente a su destinatario. Si usted no es el destinatario original de este mensaje y por este medio pudo acceder a dicha informacion por favor elimine el mensaje. La distribucion o copia de este mensaje esta estrictamente prohibida. Esta comunicacion es solo para propositos de informacion y no debe ser considerada como propuesta, aceptacion ni como una declaracion de voluntad oficial de REPSOL YPF S.A. y/o subsidiarias y/o afiliadas. La transmision de e-mails no garantiza que el correo electronico sea seguro o libre de error. Por consiguiente, no manifestamos que esta informacion sea completa o precisa. Toda informacion esta sujeta a alterarse sin previo aviso. This information is private and confidential and intended for the recipient only. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and shall not be regarded neither as a proposal, acceptance nor as a statement of will or official statement from REPSOL YPF S.A. and/or subsidiaries and/or affiliates. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave