Archive for June, 2009

Pasting from Word into WordPress (Paste from Word)

Published by cpascu June 26th, 2009 in Site and Web. 1 Comment

There is a common issue when posting from Word into the WordPress editor which causes problems when trying to view the article using the Internet Explorer browser (it simply won’t display).

The reason behind this is because Word uses some unstandardized tags for its formatting, and those tags are not recognized by IE.

Quick Fix (and a really bad way to do it):

To quickly fix an article where the issue occurs, follow these steps:

  • Go back and edit the article.
  • Switch from Visual view to HTML view.
  • Remove any text occuring before the tag, including the tag itself.
  • Switch back to Visual view and see if the article was fixed.
  • Update the article.

Currently a few different plugins for WordPress are being developed which should stop the issue from occuring. I haven’t found a working one yet. If anyone does please comment away!

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Node Offline Responses

Published by skapoor June 1st, 2009 in FieldServer and Uncategorized. 0 Comments

When a Client Node on the FieldServer goes offline the corresponding data objects on the FieldServer are also marked offline. If a client polls a virtual FieldServer node for this particular data, an offline response will be returned by the FieldServer. If the client then requests the FieldServer to identify itself, a valid response will be provided in spite of the data being offline. This results in status toggle, with the Server side Client receiving no replies to data requests and marking the Node offline and then again marking the node online after a successful identification poll, then again receiving no replies to data requests and marking the node offline and so on.

The Server Node must therefore be capable of deciding the nature of its response based on the status of relevant Client Nodes. This can be accomplished using responsible Map Descriptors (RDBC, WRBX, and WRBC). In case no acknowledgement of these functions is received, the device is identified as offline and a flag is placed at the data array offset. The virtual FieldServer can be configured using the Offline_Method option to respond to identification requests in one of the following ways:

  1. Ignore_Clients/No Setting (default) – The kernel ignores the status of Client side Nodes and uses only the online/offline status of relevant data objects to decide on the type of response.
  2. Any_Offline – If any relevant Client Node is offline the Server Node will respond with a node offline message as defined by the Server protocol. This option is available for selected drivers only.
  3. All_Offline – If all relevant Client Nodes are offline the Server Node will respond with a node offline message as defined by the Server protocol. This option is available for selected drivers only.
  4. Always_Respond – A response with data currently in the FieldServer is always sent, without considering the online/offline status of the relevant Client Nodes. This option is available for all drivers.

Offline Server Nodes are treated differently by different protocols. Some protocols will have an explicit offline response, while others will simply not respond.

If configured, the node offline response will take priority over the data offline response.<-->

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Timing Parameters

Published by skapoor June 1st, 2009 in FieldServer. 0 Comments

Normally a FieldServer sends a poll request to a Server device and that device gives a response back to the FieldServer.

Following are the timing parameters considered important in the fieldserver’s operation:

 

Scan_interval: It is the amount of time between successive poll requests. Its default value is 2 seconds and it belongs to Map descriptors, nodes and connections.

 

Poll_delay:  It is the time between receiving a response from a server device and the next poll request. Its default value is 0.05 seconds and it belongs to Connections only.

 

Timeout: If the FieldServer sends a poll request, and the Server device does not send a response, it is considered a timeout. The time for which the FieldServer waits before declaring a timeout can be adjusted by the timeout parameter. Its default value is 2 seconds and it belongs to Map descriptors, nodes and connections.

 

ic_timeout:  This parameter monitors the time between characters in a response. If the time exceeds the ic_timeout, the response is discarded and is considered a timeout. Its default value is 0.5 seconds and it belongs to Map descriptors, nodes and connections.

 

 

Retries: If a timeout occurs, then the FieldServer will retry the poll request a few more times. Number of times tried is specified by the retries parameter. Its default value is 3 times and belongs to nodes only.

 

Retry_interval: The interval between retries is specified by the retry_interval. The Fieldserver will send poll requests at the end of each retry_interval. Once the specified numbers of retries have been sent, the FieldServer will mark the node offline. Its default value is 10 seconds and belongs to nodes only.

 

Recovery_interval: Once a node has been marked offline, it will wait for a period specified by recovery_interval before sending another poll request. Its default value is 30 seconds and it belongs to nodes only.

 

Probation_delay: Once the communications have been re-established, the FieldServer will wait for a period called probation_delay, before marking the node as online. Its default value is 1 minute and it belongs to nodes only.

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Tags v/s Categories

Published by skapoor June 1st, 2009 in Uncategorized. 0 Comments

Earlier, WordPress.com used only categories and no tags. A tag is a new breed of search engine optimization i.e. SEO. Tags are fundamentally keywords for each page or article created by us. It is a non-hierarchical keyword or term assigned to a piece of information such as an internet bookmark, digital image, or computer file. This type of metadata helps depict an item and facilitates it to be found again by browsing or searching. Tags are chosen easily and personally by the item’s creator or by its viewer, depending on the system. Tags are “free-form” words means there is no formal restriction on tags we attach.

Long tag lists should be generally avoided. Tag pages are somewhat like category pages.  We can assign related posts the same tag, and then all those posts appear on the same tag page. During the design stages of the site, make a list on a piece of paper of all the tags we want to use on our site.  These will be the most important keywords for the niche, but they should be keywords that are different to the categories which we have setup for the site.  Tags can be considered as additional pages that WordPress will create offering us a secondary way of filing our posts.

Although, usage of tags made broad grouping of post topics possible yet to describe a post in more specific terms, more categories are needed. A category is an exclusively defined division in a system of classification. A system of classification here refers to a highly structured, possibly hierarchical system. For example, to borrow from the classification system for living things, we have a tree like “Animals -> Vertebrates -> Mammals -> Horses”. Any of these terms can be considered to be a category, and they fall into a strict structure.

The basic difference between categories and tags is that categories are structured and tags are unstructured. Categories organize, hierarchically. Tags need not. Tags provide meta-information, Categories need not. Tags cross-connect, Categories do not. <–>

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Pages