DELAY IN DELIVERY STATE

Similar Questions

• Problem when setting the option of delay in delivery on JMS

  Hi, I am trying to set the option of delay in delivery over JMS, but it does not work. For this I used the following code:
  
  Private Sub queuing (message from InterfaceMessage, int priority, Boolean isLog) {}
  QueueConnection queueConnection = null;
  WLQueueSession wlQueueSession = null;
  WLMessageProducer wlMessageProducer = null;
  ObjectMessage, objectMessage = null;
  delay = 5000;
  try int = 5;
  try {}
  queueConnection = connectionFactory.createConnection () (QueueConnection);
  wlQueueSession = (WLQueueSession) queueConnection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
  
  Logger.info ("\tMessageManager.queuing--> FRONT RedeliveryDelay: {} - delay: {}", wlQueueSession.getRedeliveryDelay (), delay); * //Here the newspaper prints 0 - 5000 *.
  wlQueueSession.setRedeliveryDelay (delay);
  Logger.info ("\tMessageManager.queuing--> AFTER RedeliveryDelay: {} - delay: {}", wlQueueSession.getRedeliveryDelay (), delay); * //But here, the newspaper prints still 0 - 5000, instead of 5000-5000 then why is the value set is not respected? *
  
  wlMessageProducer = wlQueueSession.createProducer (interfaceEXPRESSMessage) (WLMessageProducer);
  wlMessageProducer.setRedeliveryLimit (attempts);
  objectMessage = wlQueueSession.createObjectMessage (message);
  wlMessageProducer.send (objectMessage);
  } catch (Exception exception) {}
  Logger.Error ("MessageManager.queuing-> Exception - msg: {}", objectMessage, exception);
  } {Finally
  try {}
  wlMessageProducer.close ();
  wlQueueSession.close ();
  queueConnection.close ();
  } catch (Exception exception) {}
  Logger.Error ("MessageManager.queuing-> Exception - msg: {}", objectMessage, exception);
  }
  }
  }
  
  Could someone advise on how to fix this?
  
  Thanks in advance!
  
  Published by: cbustamante on April 29, 2011 10:54

  Configuration of the period of delivery and return limit can also be set programmatically (using WLST script or java mbeans), so if these settings change infrequently – say once a day – then mbeans could be a good approach...

  Can you explain more about what you are looking for? Your original question was late redelivery, no delivery deadline. It looks like delivery limits can be set for producers - as directed by the javadoc I mentioned above, and delays can be set on the sessions of consumers (no effect on the producers from the same session).

  An MDB does not provide users with access to the session of the container used to create internal consumption.

  Tom

• problems with the implementation of MPC with system delays

  Hello

  I have Aproblem to implement a MPC controller for a system with significant delays. The final control system will be used with a RT PXI on an engine test bench, but for now, I'm running a few previous simulations to solve problems.

  The attached vi shows a simplified system for MIMO 2 x 2. When I run it with the default settings (initial window = 0; = 5 prediction horizon and horizon of control = 2; no delay of system, or delay of prediction model) everything works fine.

  However, if I understand a delay of the plant (time factory example = 10) the CPC shows a behaviour that is not clear to me:

  * If I put 'integral action?' false: MPC operates in open loop, and the MPC calculates (and apply) the same control in the system not delayed action. Of course, it cannot compensate for errors in modeling, is not really for me.

  * If I put 'integral action?' to true: System is not stable. for fixing it, I change the initial window at 10 (and therefore the forecast at 15 horizon). Although the system is now stable, the performance of the control is not really good, because significant overruns exist

  Then I try to include in my prediction model of the delay (through a block 'CD Set delays to the (State-Space) model'), but it seems that the PPC is not sensitive about the time defined in the model.

  Hepatitis could me?

  Thank you very much in advance,

  Carlos (Adama)

  (Note, in the attached example, in what I scored blue settings that I'm changing)

  Don't worry, I solved the problem myself including delays in the model defining additional States that aceted as souvenirs.

  I can confirm that the CPC does not takes into account the deadlines defined in the model of the SS.

• How to delay identification of the appellant on SPA8000

  Is there a way to delay the delivery of the identification of the appellant on the SPA8000?  I need it to be delivered between the 1st and 2nd ring.  I can listen to it delivered before my rings of the telephone system.  He made a strange ring (instead of beep) and the identification of the appellant, then my system starts ringing.

  In my view, it is impossible to delay identification of the appellant, although I do not know if the latest firmware can do. I suggest you contact the technology support Cisco greater focus on your concerns. In my view, that this unit is part of serial company Cisco devices now supports. Try going to this link for other devices of the series business and the site where you can get your hands on Cisco for support:

  http://www.Cisco.com/Web/products/Linksys/index.html

• For blackBerry Smartphones mail delivery failure

  Hello. I'm not a blackberry user, but I email blackberry a customer regularly to my e-mail from PC. This morning I sent him an e-mail and everything went through fine. However, I went to send a second e-mail him not even an hour later and I got this back from the Postmaster:

  has not been delivered to BlackBerry Handheld sound.
  Final-recipient: RFC822; (E-mail to user BB)
  Action: failure
  Status: 5.0.0

  I thought maybe it was my e-mail (Gmail), but it is the same of the other email addresses that I would send.

  What is the cause of this? Service provider is Verizon and they say they have not experienced failures or problems in our region, but said if the phone is off or out of reach, he could do that. Any help?

  He wouldn't do that if the BlackBerry was powered off the coast or on a signal box.

  This type of error can occur from the receiving server or the sending server. The server send NDR (NDR) of your server to the sender. The NDR is an opinion of delay in delivery, not a full bounce.

  Thus, the problem could the recipients mail server, if they are on a BlackBerry Enterprise service, that she might even lie with the Exchange Server, or even if the personal messaging service, it could be a problem with the ISP.

• The message delay

  I use GlassFish 2.1 with the built-in JMS. I have a need to delay the delivery of some messages by a variable of time amount (most zero messages, some up to one hour).
  
  Y at - it a while I can put it on the message or is there a method in the implementing class of message that I could call to delay delivery?

  Message in that queue does not support that this would mean are do not conform to the JMS specification on the semantics of message command. You can file a feature request to
  http://Java.NET/jira/browse/MQ

• New area 51 - late delivery

  Anyone heard of the new area 51 are delayed.

  I ordered my Area 51 at 09:05 on 28-10-14.

  It's 5 minutes after they went on sale.

  I gave an on 25-11-14 delivery date and it has been shown that in production.

  Now, Alienware declare my production was cancelled and the new delivery date is 12/10/2014.

  This is my 5th PC Alienware - and I like them a lot - but the time to build and delivery needs improving.

  Does anyone else have a delay in delivery?

  There is a delay of 24 days for sorting GTX years 980.

  My estimated for the Canada delivery date is January 14, 2015!

  Intel Core i7-5960 X

  DDR4 Quad Channel 16 GB to 2133 MHz

  SSD 256 GB + 4 TB SATA 6.0 K

  Drive Blu - ray dual layer slot loading

  Triple NVIDIA GTX 980

  Windows 8.1 (64-bit) English

  Complete care of 4 years

  Price: $4 821,09 HT

• Problem loading 7 IPhone

  It's the road that has taken so far my new iPhone:

  Bryan, TX, United States	10/04/2016	08:50	A processing UPS error delayed the delivery. We are setting plans as quickly as possible. / Delivery will be postponed.
  	10/04/2016	08:45	Scan destination
  	10/04/2016	08:27	Analysis of arrival
  Houston, TX, United States	10/04/2016	06:27	Departure scan
  	10/04/2016	05:42	Analysis of arrival
  Louisville, KY, United States	10/04/2016	04:43	Departure scan
  	10/04/2016	02:34	Import Scan
  	10/04/2016	01:05	Analysis of arrival
  Houston, TX, United States	10/03/2016	22:03	Departure scan
  	10/03/2016	21:21	Analysis of arrival
  	10/03/2016	20:53	Departure scan
  Houston, TX, United States	10/02/2016	23:37	Analysis of arrival
  Shreveport, LA, United States	10/02/2016	19:10	Departure scan
  	10/02/2016	18:21	Analysis of arrival
  Louisville, KY, United States	10/02/2016	17:44	Departure scan
  	10/02/2016	10:39	Import Scan
  Louisville, KY, United States	10/01/2016	03:51	Analysis of arrival
  Anchorage, AK, United States	30/09/2016	17:51	Departure scan
  	30/09/2016	16:43	Analysis of arrival
  Incheon, Korea, Republic of	10/01/2016	01:42	Departure scan
  Incheon, Korea, Republic of	30/09/2016	15:11	Your package is in transit. We're updating of plans to schedule your delivery. / The package will be sent to a UPS facility in the destination city.
  	30/09/2016	04:35	Your package is in transit. We're updating of plans to schedule your delivery.
  Incheon, Korea, Republic of	29/09/2016	20:06	Analysis of arrival
  ZhengZhou, China	29/09/2016	17:13	Departure scan
  	29/09/2016	01:00	Analysis of arrival
  ZhengZhou, China	09/28/2016	23:57	Departure scan
  	09/28/2016	21:26	Analysis of the situation
  	09/28/2016	20:48	The origin analysis
  China	29/09/2016	12:17	Order processed: ready for UPS

  Has anyone else seen a problem like this using UPS?  I have reported the inverter problem, don't know if Apple cares.

  I had this problem too, but my problem is my phone bouncing from ZhengZhou to Incheon and then shipment of ZhengZhou again. After contacting UPS they said that the cause of this is that they have logic of expedition of the paths they update your account with. So that could be a problem where it should be at this place so it is actively update your shipping with these data, even if it is physically still in the starting location. Honestly their response sounded completely senseless and seemed to be counterproductive to the concept of making happy customers, but that's what they have stuck with even after poking me holes in the logic. Trying to rationalize why this might be, I guess that with apple ship as much different iPhones at the same time, the shipping information are only an unreliable, they are trying to give the promise of a tracking number, but the number is more than one way to make the customers happy with knowing their phone is on the right track, but UPS could actually cope with the amount of shipments from a single source and using an algorithm based on the how they are usually able to ship items but having to deal with customs international, is initially for a pain and a little fear to many of us who patiently await the arrival of their iPhone. My only thought is that better, I get my phone until they start having their walk in buyers of their target of 10/8.

  If a TL; DR: the phone is probably not physically in one of these locations, those are estimates by UPS where your phone has to be now.

• Death in unicast and multicast mode detection algorithm

  Hello

  Today, I tried to check - how does detection of death in multicast and unicast. To my understanding - that, in two modes, consistency has following algorithm:

  1. All members in unicast cluster heartbeat messages send with 2 other members, using the TCP connection via the port UDP cluster.
  2. Senior member (senior for that service?) send heartbeat broadcast messages.

  In both modes (Unicast and Multicast) - consistency is using TcpRing mode, am I right?

  My questions are:

  1. How each Member of the cluster detects - so that others of 2 nodes, it must send the message of heartbeat?
  2. If the node 1 is down - how nodes, which sent the message drive to this node change heartbeat for message impulse unicast address? And how long will it take?
  3. If the node that declined-joins the cluster - node will send heartbeat messages to this node and works with her consistency?
  4. How can I see in the newspapers, the heart beats (I changed the level of logging at 9, but it does not show the heartbeat messages)?
  5. What is a full role of the upper limb in multicast (perhaps new members connect to the upper limbs, and then it sends the notification to all members via broadcast/multicast or something else?)? And what is the difference between the WKA and senior member unicast? What is a member additional features WKA performs?

  Thank you!

  There is only one difference between unicast and multicast dead detection variants so we will cover only the first.  In a multicast are grouped the cluster senior (member of the cluster of longer life) emits a blink of an eye a multicast times per second.  That heartbeat contains the IDS of all the cluster members.  A non-superieur member receives the multicast heartbeat if heart rate is its main known, and does not contain the Member of reception in all of the known members of the recipient will deduct that it was for a reason any declared as dead and so now does not not to be part of the cluster.  At this point, the receiving Member stops his grouping and wait for an external stimulus to try to join the cluster.  This stimulus would be basically any user code that attempted to use a cluster resource.  Note that this is not exactly detection of death, but rather of detection that you have been declared dead.  In a cluster of unicast only the realization even happen by non primary member by train to learn that other members refuse to ack, any of her communications.  It should be noted that in both cases, we take on a undead member of learning that he was falsely declared dead and this is an extremely rare event.

  Next move common aspects of the detection of death which are used by multicast and unicast based clusters.  All other forms use only unicast i.e. point to point networks.  In fact, we have three separate death detection mechanisms:

  The first is TcpRing, which monitors deaths in the form of suspension of processing of other members.  Basically, we create a 'ring' of TCP connections which includes all members of the cluster, for example 3-> 2-> 1-> 3.  On the side of the destination of the connection will never close the connection, so the side origin knows that if the connection is closed, it means that the Remote OS kernel has detected that the process is dead and this nucleus has cleaned the connection and to inform the other side that it is closed.  This form of detection of death is deterministic, that there is essentially no such thing as a false positive, and that if the connection is detected as closed the remote member must be dead.  One of the advantages of this is that it allows a very fast detection because it involves no waiting times, only the time that necessary for the nucleus remote to send a packet to the original machine, so we don't talk detection of millisecond under processes completed that.  Most of the deaths are detected through this mechanism.  Unfortunately, this mechanism is not infallible because it is based on a working network connection between the origin of the Member and the machine target.  Thus, it cannot detect a failed computer or network.

  This is where IpMon comes.  IpMon is a component within coherence where each Member once a second "pings" one machine in the cluster.  If the ping fails he follows it with additional pings (two by default).  If none of these pings work and there had been no acknowledgements of all members on the target during the ping cycle machine failed the remote machine is considered be failed and all the members who were running on it are reported as dead.  Note that the pings are not against members remote but the remote machines and therefore should succeed even if the remote member was temporarily unavailable due to a GC.  Time-out based means it is not deterministic, and we must set a relatively high time and try the County to try to avoid false positives.  The default value is three five second ping attempts.  So basically if you put a machine out of service or disconnect it from the IpMon network must withdraw all its members fifteen seconds approximately.  It is quite a long time from the time of detection under "millisecond" of TcpRing, but it is still fast enough.  Failure also produces far less often then suspension of treatment so it ends not accounting for most of the detections, but it does not fill in the void left by TcpRing.

  The final mechanism used is a delay of delivery of packets.  Each packet by coherence should get ack was within a few hundred milliseconds.  If it's not it gets broadcast automatically every few hundred milliseconds.  If this condition persists for an extended period (five minutes by default) then a fault is declared and one on both sides of the operation in the end must be removed from the cluster.  The original Member will consult with the other two members of the cluster and at least another agrees that the Member does not meet the destination member is declared as dead.  If both consulted members indicate that the destination seems to work very well then the author assumes local failure and ends.  In addition to the traffic normal cluster consistency will automatically send a heartbeat from point to point to a few other members once per second with an algorithm that ensures that every Member will be issued a heartbeat or some other communication within 2/3 of the timeout that is 2/3, 5 m.  And even in an inactive cluster sure us we would still have minimum transmissions both detect the inability of the acknowledgement, and also to have enough current stats to answer another Member of query asking if some third-party member building.  This type of detection of death only comes into play for a strange type of death.  The faulty Member machine and the process are detected as living, but the Member is inadmissible.  Basically it watches just for bugs in the transport of coherence itself.  It can also be caused by the target process receives no time CPU for a long time, I.E. CTRL-Z, GC, or Exchange and as such almost never occurs because failure would need to last five minutes.

  Regarding forestry, we do not have an option to save the package-level operations, but there will be if a member is declared as death and why he stated as being deceased.

  I hope that answers your questions.

  Thank you

  Mark

  The Oracle coherence

• 7 iPhone and shipping nightmare

  SProgresswhat is?

  Location	Date	Local time	Activity
  Incheon, Korea, Republic of	23/09/2016	05:54	Harsh weather have delayed the delivery.
  Incheon, Korea, Republic of	21/09/2016	20:01	Analysis of arrival
  ZhengZhou, China	21/09/2016	16:36	Departure scan
  	21/09/2016	15:58	Your package is in transit. We're updating of plans to schedule your delivery. / The package will be sent to a UPS facility in the destination city.
  	21/09/2016	14:41	Your package is in transit. We're updating of plans to schedule your delivery.
  ZhengZhou, China	19/09/2016	23:30	Analysis of arrival
  	19/09/2016	22:57	Departure scan
  	19/09/2016	18:52	Analysis of the situation
  	19/09/2016	16:24	The origin analysis
  China	19/09/2016	10:16

  Apple said that it would be delivered on 23

• E-mail failure

  Hello.

  I've just set up my HP 8600.

  This notion of eprinting is new to me, but I have everything connected via connected HP

  I tried sending emails to my printer, but each time it fails, and I receive this message: this is an automatically generated delivery State Notification.  Delivery to the following recipients failed.

  I inserted the "approved" e-mail addresses

  I send it to the address @hpe.com

  Obviously, something is still missing.

  Can anyone help?

  Thank you!

  Hello
  
  The correct address should be: [email protected].

• cleaning multithreaded DLL

  Hi all

  I'm building a small DLL (for use from matlab) for acquisition of data. One of the functions may take several hours: streaming over 1 million samples in a file. So for this particular function, I want (read: I'm trying) to run it as a background operation in a separate thread. After reading a quick guide OR the multi-threading I selected the following:

  -Start streaming function

  * start a new async timer, which calls every second ProcessSystemEvents all detached CVI callbacks are executed

  * start the new pool of threads for maximum 1 wire and the highest (but not time critical) priority

  * Schedule streaming function for this pool (once again with a priority higher but non-emergency)

  specification of the cleaning function to be run in the current thread after completing the function continuous

  -reminder async-timer run ProcessSystemEvents every second post CVI callbacks are executed

  -cleaning function

  * Release the function ID from thread pool

  * Throw the thread pool

  * Take async-timer

  -State function which can be used from the main thread (still available at the matlab prompt) to check the status of the streaming

  The beginning of the broadcast (simulated with a countdown of the meter) goes well

  I can retrieve the status that goes from kCmtThreadFunctionExecuting to kCmtThreadFunctionComplete.

  However, the function of cleaning - as specified in the service scheduling - is never started.

  Q1: what did I wrong that prevents the scheduled cleaning?

  Q2: are there different approaches/examples that don't just want I want?

  Thanks in advance, Jos

  Use: Labwindows/CVI 8.0.1

  / * some administrative global variables * /.

  public static int PoolHandle = - 1;
  public static int ThreadHandle = - 1;
  public static int ThreadSamples = 60;
  public static int ThreadStatus = 0;
  public static int ThreadTimer = - 1;
  / * cleanup function * /.

  void CVICALLBACK FBGLAB_ThreadCleanup (int poolHandle, int functionID, unsigned int, int value event, void * callbackData)

  {
  int counter = 0;
  int Status = - 1;
   
  Delay (0.2); / * short wait so function thread can close * /.
  printf ("starting pool clean up\n");
  CmtGetThreadPoolFunctionAttribute (PoolHandle, ThreadHandle, ATTR_TP_FUNCTION_EXECUTION_STATUS, & status);
  While ((status< kcmtthreadfunctioncomplete)="" &&="" (counter=""><>
  {
  Counter += 1;
  Delay (1.0);
  }
  If (status<>
  {
  / * finish the thread after timeout * /.
  CmtTerminateThreadPoolThread (PoolHandle, ThreadHandle, 0);
  Delay (1.0);
  }
  CmtReleaseThreadPoolFunctionID (PoolHandle, ThreadHandle);
  CmtDiscardThreadPool (PoolHandle);
  DiscardAsyncTimer (ThreadTimer);
  ThreadHandle = - 1;
  ThreadTimer = - 1;
  PoolHandle = - 1;
  }
  / * simulated stream * /.

  int CVICALLBACK FBGLAB_ThreadStreamingWavelength(void *functionData)
  {
  ThreadStatus = ThreadSamples;
  While (ThreadStatus > 0)
  {
  Delay (1.0);
  ThreadStatus-= 1;
  }
  ThreadStatus = 0;
  Return (0);
  }
  / * async-timer callback * /.

  int CVICALLBACK FBGLAB_Timer(int reserved, int timerId, int event, void *callbackData, int eventData1, int eventData2)
  {
  If (event is EVENT_TIMER_TICK)
  {
  printf ("State of Thread is %0d\n", ThreadStatus);
  ProcessSystemEvents();
  }
  Return (0);
  }
  / * part of the function to retrieve the status of streaming * /.

  long __stdcall FBGLAB_GetStreamingStatus (long lDevice, char * response, long BufferSize)
  {

  int Status, FunctionStatus;
  Status = CmtGetThreadPoolFunctionAttribute (PoolHandle, ThreadHandle,
  ATTR_TP_FUNCTION_EXECUTION_STATUS,
  (& FunctionStatus);
  }

  / * Start simulated stream * /.

  long __stdcall FBGLAB_StartTest (long Nsamples, double SampleInterval)
  {
  int Status = 0;
  If (PoolHandle > = 0) return (FBGLAB_ERROR_MULTIPOOLEXIST);
  If (ThreadHandle > = 0) return (FBGLAB_ERROR_MULTITHREADEXIST);
   
  If (status > = 0)
  ThreadTimer = NewAsyncTimer (1,0, -1, 1, FBGLAB_Timer, 0);
  If (status > = 0)
  Status = CmtNewThreadPool (1, & PoolHandle);
  If (status > = 0)
  Status = CmtSetThreadPoolAttribute (PoolHandle, ATTR_TP_THREAD_PRIORITY, THREAD_PRIORITY_HIGHEST);
  If (status > = 0)
  Status = CmtScheduleThreadPoolFunctionAdv (PoolHandle,
  FBGLAB_ThreadStreamingWavelength, NULL,
  THREAD_PRIORITY_HIGHEST,
  FBGLAB_ThreadCleanup,
  EVENT_TP_THREAD_FUNCTION_END, NULL,
  CmtGetCurrentThreadID(),
  (& ThreadHandle);
  Return ((long) Status);
  }

  Hello again,

  It seems that the solution is as simple as the cause.

  -J' I create a pool of threads of high priority and program a priority acquisition function. Planning is done with CmtScheduleThreadPoolFunctionAdv. I do not use the option for a reminder at the end of this threadfunction.

  -A second more later (or in the service of acquiring) I schedule a cleaning of normal priority in DEFAULT_THREAD_POOL_HANDLE. Planning is done with CmtScheduleThreadPoolFunction. Inside this function, I wait until the acquisition thread is finished: CmtWaitForThreadPoolFunctionCompletion

  -Because all these functions are to 'demand' the original calling function returns. I get the prompt matlab for other tasks.

  I have to check what expectation-statement requires less processing for example power CmtWaitForThreadPoolFunctionCompletion or delay with the State Audit.

  But I have already seen that this combination:

  -start the acquisition in a high priority thread pool

  -then release the assignment of function and removes the high priority pool

  -During this time I had the back guest matlab and can run another task

  Thanks to everyone for their contribution, Jos

• default transition in vision Builder

  Hello

  I am a new user of Vision Builder AI 2011 and have a question about the transitions between States (default).

  In a testapplication I build for different features of Vision builder I want to create 3 States, each consisting of a series of tests. It works without problem.

  But the problem starts when I want to put an end to the test during one of the inspectstates does not pass. To do this, I added 3 (fault) specifies in which I put an overlay so that the reason for the "failure" becomes visible. The transition to these States 'fault' is changed so that the transition is only used when the above report fails. Each of the 'fail' states has a transition directly to the outcome.

  The problem I encounter is that, even when any of the tests fail, the program works always true all the other tests.

  Reason (I think), it's that I can't change the default transitions (ranging from inspectstate to inspectstate). And seeing that you cannot delete or change the default reports I can't find the solution to this problem.

  I've considered adding another transition between the inspectstates and to change this transition, but what to do with default transitions?

  Contribution to this issue would be greatly appreciated. I only started working with Vision Builder, but I see endless possibilities, if this problem is solved.

  Thank you

  Tom

  Hello

  After having a quick glance at your program, it seems that everything is OK, (as you did not provide the images, I just looked after the transitions).

  Your transitions are good, so if an error occurs in a processing status, go to the final State, and other States will not work.

  But what make you think that other States are good that the program doesn't run?

  You can run your sript in Setup mode after adding a delay in all States. You will then be able to see in schema view that pass are valid or not.

  Concerning

• SL400 gone yet?

  AGAIN, the SL400 has disappeared. What is originally the SL300 to disappear and the SL400 to suffer the same fate?

  usually they take it down when the stock is insufficient, and it would be only conditioned it again if they can group enough inventory for the expected demand, that the last thing manufacturers want is there a shortage of stock or a delay in delivery. Everything else something that Lenovo have experiences.

• run a while loop in separate vi, minimize the window flashing

  My apologies in advance for not including a VI; I cannot give it, cannot even provide screenshots.

  I have a state machine base with a cluster of Boolean values that are analyzed in the 'default' State, the scan index = true determining the next State. All other States to return to the default state. The State of 'stop' stop the loop with a Boolean constant = True, located inside the structure case wired to the time entry conditional loop (all States have a Boolean constant False wired to it). Apart from the cases

  statement, the wire connected to the conditional entry is connected to a Boolean indicator, ' Stop, in really. The time delay within the State of the machine while loop is currently set at 100 ms.

  In addition to the 'State' shift register, the state machine has a "boolean" shift register. All States, except one, feeds the value passed the Boolean value through to the next State (i.e. wired directly from left to right the structure of the case). The exception is the State which inverts the Boolean value, with the output of the inverter transferred to the State following and also connected to a Boolean flag, 'Show the State', the

  indicator outside the case statement but inside the while loop. All other States wire just the previous state of the Boolean value through the following State, unchanged.

  In addition to the State of the machine while loop, I have a parallel while loop (scourge of the LV forums). All entered conditional loop is connected to a local variable to 'stop, really. " A True/False case in this while loop structure contains a Subvi in the case of True value. The Boolean value of entry to the case statement is connected to a local variable for 'Show status'. The Subvi, which is in the real case is to display the State of the

  user.

  The Subvi which provides status through its frontage runs a script in python via a 'comand prompt"vi. The necessary update to the python command send is ~ 1/second. Within the Sub - VI is a 1 second delay time after execution of the code.

  It works but I'm doing some improvements with minimal impact on what I have.

  Two cases of VI properties that relate to the conduct of the State Subvi (floating or default, modal does not at all):

  1. with "Firm when previously closed" selected, the window switches VI (via the main switch VI) open and closed but when it is open there is the a second window flash that could cause seizures in some users.

  2. with "closes when previously closed" deselected, the window remains open and it is difficult to tell the difference between the running state and is not running. In addition, the Subvi window will not be reduced for this option.

  Is there a little invasive change, I have the code in force to stop a second flash described in #1 above and activate / deactivate the Subvi status window?

  Thank you

  Jeff