{"id":398,"date":"2016-03-03T19:47:59","date_gmt":"2016-03-03T19:47:59","guid":{"rendered":"\/?post_type=ht_kb&p=398"},"modified":"2018-03-10T20:07:49","modified_gmt":"2018-03-10T20:07:49","slug":"running-snip-for-the-very-first-time","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/running-snip-for-the-very-first-time\/","title":{"rendered":"Running SNIP for the very first time"},"content":{"rendered":"

When SNIP<\/strong><\/span> runs for the first time on a new machine, it presents the user with a large amount of log detail which may be confusing for the first time user.\u00a0 This entry serves to sort out the major sections of the log during the start up phase and give a new user a sense of context.\u00a0 At the end of this article are some key steps you will want to take to configure SNIP<\/strong><\/span> to meet your own unique needs.<\/p>\n

Once SNIP<\/strong><\/span> is set up, most of these messages become routine and can be filtered from view with SNIP<\/strong>‘<\/span><\/span>s extensive console filtering<\/a> controls.\u00a0 At a high level, blue messages are good, while red ones are bad.\u00a0 Green messages are generally informational or hints.\u00a0 As a first time new user, you are presented with a number of Hints\u00a0 regarding how you might want to control SNIP<\/strong><\/span>.\u00a0 These appear periodically when new controls are used, and there is some logic to reduce the rate they are repeated.<\/p>\n

On Start Up, License Check<\/h4>\n

Every time SNIP<\/strong><\/span> is started it seeks for the simpleNTRIP.ini<\/strong> file (where all your user settings are kept). If it does not find this file, it creates it and defaults to a new user start up sequence. It also seeks for the license.dat<\/strong> file (where your license rights are kept). If it does not find this file, it presumes a Basic<\/em> <\/strong>license level for product evaluation and allows one hour<\/span> of operational use. \u00a0It alerts the user of this as shown in the console fragment below. \u00a0You need a license file to use SNIP<\/strong><\/span> beyond the one hour period. License levels range from the free Lite<\/em> model with a core set of Caster Features to an Enterprise<\/em> level server with essentially unlimited connectivity features. The various license levels are described further on this<\/a> page. Registration is discussed further on this<\/a> page, evaluate then register.\u00a0 And please comment on how we can improve SNIP<\/strong><\/span> to meet your needs.<\/p>\n

\n
Was unable to find license file <\/span><\/b>at location: \/license.dat\r\n Running in UNREGISTERED<\/span><\/b> mode with an operating time limit of 59:59 minutes<\/b>\r\n If you have any questions while evaluating SNIP<\/span><\/b>, please see the KB at Support.Use-SNIP.com\/knowledge-base\/<\/span><\/u>\r\n Registration is easy and free and removes this time limit.\r\n See the menu item: Help -> Registration<\/b>.<\/span><\/pre>\n<\/blockquote>\n
First Time Use<\/h4>\n
In the next stage of the start up sequence, SNIP<\/strong><\/span> sets various filter controls for the log (showing all details) and alerts the new user to this. \u00a0Filter controls are covered further in this<\/a> article. \u00a0The current version of the SNIP<\/strong><\/span> is also checked; if a new download has been released the user will be alerted.\u00a0 A few lines are also added to the console to remind the user that further settings values are needed before SNIP<\/strong><\/span> can become a Caster on this machine. \u00a0[A short list of such steps is provided at the end of this article.]<\/p>\n
\n
Console log entries will not<\/u> <\/b>be filtered; all entries types will be shown.<\/span>\r\n  \u00a0 \u00a0This can become very cluttered, so use of filters and the level is recommended.<\/span>\r\n\r\nChecking for product updates...<\/span>\r\n\r\nNote:<\/span><\/b>\r\n This is the very first time simpleNTRIP<\/b> has been run on this machine.\r\n Details such as your server IP and port number need to be set up to allow automatic starting <\/span>\r\n\r\n\u00a0\u00a0Hint: <\/span><\/b>\r\n By convention, NTRIP Casters use port 2101<\/b> - but you my use any port you wish.\r\n You will probably want to enable Auto start<\/b> once you have things setup as well.\r\n Checkboxes on each major tab allow you to auto start the\r\n NTRIP Caster itself, the Serial Connections, the Remote Connections\r\n And in-bound PUSH data from NTRIP Servers\r\n\r\nAn initial set of connections to one of the SNIP open servers at ntrip.itsware.net\r\n has been started as an example to show the Caster working (see the Relay-Streams tab).\r\n Try the wizard (under the Control<\/i> menu) to set up a connection.\r\n\r\nYou also need to set the IP address for the server to use; valid choices are listed below.\r\n You can change these settings in the Caster and Clients<\/i> Tab.\r\n\r\nWhenever you close the program the prior settings will be saved and used the next time.\r\n\r\nWe welcome your feedback on how to make SNIP a better program to meet your needs.\r\n SNIPs on-line help can be found at: https:\/\/www.use-snip.com\/kb\/knowledge-base\/<\/u><\/b> If the KB does not serve, you can reach us by email at support@use-snip.com<\/pre>\n<\/blockquote>\n
Hello World<\/h4>\n
At this point the normal SNIP<\/strong><\/span> hello world welcome <\/em>details are presented listing the precise edition of SNIP<\/strong><\/span> used.<\/p>\n
\n
SNIP<\/span><\/b>, the simple NTRIP Caste<\/b><\/span>\r\nA Caster tool to connect DGPS Reference Stations to NTRIP Clients with multiple modes<\/span>\r\nSimple NTRIP supports gathering RTCM data streams in serial, tcp\/ip, and relay connection modes<\/span>\r\nAnd then transmitting these corrections streams to multiple end users (the NTRIP Clients)<\/span>\r\n- - -<\/span>\r\nPart of the DGPS tools collection, available at: \u00a0 www.Use-SNIP.com<\/b><\/span>\r\nUser's Guide and Knowledge Base is available at: \u00a0 support.Use-SNIP.com<\/b><\/span>\r\nCopyright 2010~2016 By SubCarrier Systems Corp. (SCSC), Patents Pending.<\/span>\r\nBuild:\u00a0\u00a0 0.9.2<\/b> \u00a0 of Jun 24 2016 at 14:06:33 <\/span>\r\nForked from the 'Row Jimmy<\/i>' development code base.<\/span>\r\nRegistered to:\u00a0\u00a0\u00a0 Un Registered<\/b><\/span>\r\nRegistered to:\u00a0\u00a0\u00a0  <\/b><\/span><\/pre>\n<\/blockquote>\n
The registration name above is replaced with the registered user’s name from the license file when that is present. The precise text shown will vary depending on the log threshold<\/a> setting when the tool is started.<\/p>\n
The startup Phase<\/h4>\n
At this point SNIP<\/strong><\/span> will load and start the various major functional sections as follows:<\/p>\n
    \n
  1. The User Accounts and Client Classes<\/li>\n
  2. The Serial Port Data Streams<\/li>\n
  3. The \u00a0Remote – Relay Data Streams<\/li>\n
  4. The PUSH-In NTRIP Caster Data streams<\/li>\n
  5. The PUSH-Out NTRIP Caster Data streams<\/li>\n
  6. The NEARest NTRIP Caster Data streams<\/li>\n
  7. Any Raw TCP\/IP Data Ports<\/li>\n
  8. The SNIP Caster Itself<\/li>\n<\/ol>\n
    Each of these makes several entries in the log and is considered in turn\u00a0below.\u00a0 When reviewing the log entries, keep in mind that on a server device many connections and reply events are occurring in odd orders, overlapping with other similar connections.\u00a0 The console events filter<\/a> can be very effective at displaying only the events of interest in a given context.<\/p>\n
    The User Accounts<\/strong><\/h4>\n
    The list of user accounts is loaded first.\u00a0 On the initial run there are no such account created to load, so a warning of this is presented. If you plan to run SNIP<\/strong><\/span> in an open mode, you will not need to create any accounts.\u00a0 The process of managing user accounts is discussed further here<\/a>.\u00a0 A number of minor settings for items such as how often new data log files will be written for each stream are also displayed. All of these can be changed in various preferences settings.<\/p>\n
    \n
    NOTE:<\/span><\/b> Cannot read client user file: ClientTable.txt:\u00a0 No such file or directory\r\n\u00a0\u00a0\u00a0 A file will be created when a new user is added.\r\n\u00a0\u00a0\u00a0 New users can be added under the Caster and Clients<\/i> tab.\r\n<\/span>NOTE:<\/span><\/b>\u00a0 The settings currently allow Anonymous access<\/b> to the caster at this time.\r\n\u00a0\u00a0\u00a0\u00a0 Hint: \u00a0\u00a0<\/span><\/b> You can change this in the 'Edit Users' dialog (under the Caster-Clients<\/i> tab)<\/span>\r\n\r\nAll filters for entry types reset to default state.\r\nConsole log entries are not <\/u><\/b>be filtered; all entry types will be shown.\r\n\u00a0\u00a0\u00a0 This can become very cluttered, so use of filters and the level is recommended.\r\n<\/span>\r\nOpening all prior streams and connections from saved settings...\r\n\u00a0\u00a0\u00a0 All Logs and Data saved to: C:\/Program Files (x86)\/SNIP_092\/SNIP\/bin\/data\/\r\n\u00a0\u00a0\u00a0 File change rate for data log files is set to every 24 hours<\/b>.\r\n\u00a0\u00a0\u00a0 Log file: C:\/Program Files (x86)\/SNIP_092\/SNIP\/bin\/data\/SNIPlogs\/WklyConnections_16_25.csv opened. <\/span>\r\n\r\nConsole Log word wrap mode changed.\r\nAdditional details about relay reconnection events will NOT<\/u> be shown<\/b> in the console.\r\nIf a remote-relay caster stream replies with its table, it will NOT<\/u> be shown<\/b> in the console.\r\n<\/span>NOTE:<\/span><\/b>\u00a0UDP Socket stream sender (for SAE J2735 DSRC RSU use) is disabled in this build.<\/span><\/pre>\n<\/blockquote>\n
    Starting Serial Port<\/strong> Data Streams<\/h4>\n
    Because there are no prior serial stream settings in the ini file, and “auto start” is not set, nothing is performed in this step.\u00a0 This<\/a> article discusses how to add a serial data stream to SNIP<\/strong><\/span>.\u00a0 Like the other data stream types to follow, the number of simultaneous connections which are allowed with the current license is also mentioned.<\/p>\n
    \n
    Establishing local serial UART slots for up to 15<\/u><\/b> local base stations...\r\n\u00a0\u00a0\u00a0 ...Done. Started No<\/strong> UART Serial streams from last run.<\/span><\/pre>\n<\/blockquote>\n
    Note:\u00a0<\/strong><\/span> Serial stream device setup is often the slowest type of connection to establish during the startup phase. This is because the sequence of setup commands are sent in a\u00a0single line at a time<\/em> fashion with delay for each line to allow the device to reply with various messages. A complex setup or tear down can take tens of seconds.<\/p>\n
    Starting Remote – Relay<\/strong> Data Streams<\/h4>\n
    In this initial run of SNIP<\/strong><\/span> there are no serial port connections yet, and incoming PUSH data\u00a0is disabled, but we do start up with some example remote connections to see it all work. \u00a0SNIP<\/strong><\/span> starts up on any new machine by connecting to three remote-relay sites, just to show it all working. \u00a0The initial sites are selected from the following list taken from the SCSC open caster<\/a>.\u00a0 This<\/a> article covers how to “read” a mountPt if the below is unfamiliar to you.<\/p>\n