{"id":3187,"date":"2025-04-17T09:47:59","date_gmt":"2025-04-17T09:47:59","guid":{"rendered":"https:\/\/webprojects.cloud\/wordpress\/splatco\/?post_type=spl_knowledgebase&#038;p=3187"},"modified":"2025-05-07T11:31:28","modified_gmt":"2025-05-07T11:31:28","slug":"nvem0-directive-d15","status":"publish","type":"spl_knowledgebase","link":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/","title":{"rendered":"NVEM0 Directive [D>=15]"},"content":{"rendered":"\n<p>The NVEM0 directive is used to mark the boundary between executable code and NVEM0 memory space. SPLat\/PC uses it to recognise where to start looking for and processing data for pre-loading into the NVEM0 memory.<\/p>\n\n\n\n<p>There must be only one instance of the NVEM0 directive in your file and it must occur at the END of your program code.&nbsp; NVEM data using the NV0Byte, NV0Ptr, NVfNum directive can then be placed AFTER the NVEM0 directive.<\/p>\n\n\n\n<p>Here&#8217;s an example:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><br>   RTCPushDN<br>   NVSetPtr       NLpDays                             ;point to the string pointer table<br>   NVSetRecLen    2                                   ;load the pointer..<br>   NVPopRecNum<br>   NVReadToPtr    0                                   ;..to the string<br>   NVSetRecLen    3                                   ;there are 3 chars to print<br>   NVSetRecNum    0<br>   OBLCD_NVText   0                                   ;display them<br>   .. more code ..<br><br>   NVEM0                                              ;tell SPLat\/PC NVEM data follows<br>   ;you cannot have program instructions from here onwards<br><br>NLpMon            NV0Byte  \"Mon\"<br>NLpTue            NV0Byte  \"Tue\"<br>NLpWed            NV0Byte  \"Wed\"<br>NLpThr            NV0Byte  \"Thr\"<br>NLpFri            NV0Byte  \"Fri\"<br>NLpSat            NV0Byte  \"Sat\"<br>NLpSun            NV0Byte  \"Sun\"<br><br>NLpDays<br>                  NV0Ptr   NLpMon<br>                  NV0Ptr   NLpTue<br>                  NV0Ptr   NLpWed<br>                  NV0Ptr   NLpThr<br>                  NV0Ptr   NLpFri<br>                  NV0Ptr   NLpSat<br>                  NV0Ptr   NLpSun<br><\/pre>\n\n\n\n<p>\u00a0Using\u00a0<a href=\"https:\/\/webprojects.cloud\/wordpress\/splatco\/download\/splat-pc-32-bit\/\">SPLat\/PC Builder<\/a>\u00a0with multiple files, it&#8217;s no trouble to ensure you&#8217;ve got just one NVEM0 directive.\u00a0 Just put the NVEM0 directive in its own section and ask builder to include\u00a0<strong>ONLYONE<\/strong>.\u00a0 Here&#8217;s an example:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">-- In your builder.b1d file --<br>NVEM0DIR ONEONLY                                      ;Marker for the start of non-volatile memory<br>NVEM0MODBUSDATA                                       ;MODBUS NVEM data goes FIRST!<br>NVEM0DATA<br><br>-- in each of your.spt files --<br>;&lt;NVEM0DIR&gt;<br>   NVEM0                                              ;Start of non-volatile memory<br><br>;&lt;NVEM0DATA&gt;                                          ;Non-volatile memory data<br>pXwireMaster<br>   NV0Byte  0,M2SabBuffer,M2SkBufLen,0,0<br>   NV0Byte  255<br><\/pre>\n\n\n\n<p>Source in the&nbsp;<strong>NVEM0DIR<\/strong>&nbsp;section will occur just once, then everything in all&nbsp;<strong>NVEM0DATA<\/strong>&nbsp;will sections will follow.<\/p>\n\n\n\n<h6 class=\"wp-block-heading\">For SPLat\/PC versions after build 329<\/h6>\n\n\n\n<p>From this version of SPLat\/PC the NVEM0 directive has become optional.\u00a0 You may now have NVEM page 0 data directives such as\u00a0<code>NV0Byte, NV0Ptr, NV0fNUM<\/code>\u00a0anywhere in your program. This is particularly handy for supporting a modular style of programming, say with multiple files using\u00a0<a href=\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/include-hash-command\/\">#Include<\/a>.<\/p>\n\n\n\n<p><strong>However there is one restriction:<\/strong>&nbsp;The line label for a NVEM page 0 data line must be on the same line &#8211; you can&#8217;t have the label on one line and the NVEM0 data (or whatever) on the lines below.<\/p>\n\n\n\n<p>Note that from SPLat\/PC build 329 you may place NVEM directives anywhere in your code.&nbsp; If you do this, then the line label for an NV0Byte directive must be on the same line. The following is not allowed:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><br>MyTable:    **** ILLEGAL!!! *****<br>            NV0Byte 45<br>            NV0Byte 12<\/pre>\n\n\n\n<p>Instead, you must say this<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><br> MyTable:   NV0Byte 45<br>            NV0Byte 12<br><\/pre>\n\n\n\n<p>Please refer to the\u00a0<a href=\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/tutorials-application-notes-and-white-papers\/non-volatile-extended-memory-nvem-users-guide\/nvem-type-specific-information\/nvem0-documentation\/\">NVEM0 documentation<\/a>\u00a0for more details.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The NVEM0 directive is used to mark the boundary between executable code and NVEM0 memory space. SPLat\/PC uses it to recognise where to start looking&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":3171,"menu_order":15,"template":"","class_list":["post-3187","spl_knowledgebase","type-spl_knowledgebase","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>NVEM0 Directive [D&gt;=15] - SPLat Controls<\/title>\n<meta name=\"robots\" content=\"noindex, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"NVEM0 Directive [D&gt;=15] - SPLat Controls\" \/>\n<meta property=\"og:description\" content=\"The NVEM0 directive is used to mark the boundary between executable code and NVEM0 memory space. SPLat\/PC uses it to recognise where to start looking...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/\" \/>\n<meta property=\"og:site_name\" content=\"SPLat Controls\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-07T11:31:28+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/\",\"url\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/\",\"name\":\"NVEM0 Directive [D>=15] - SPLat Controls\",\"isPartOf\":{\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#website\"},\"datePublished\":\"2025-04-17T09:47:59+00:00\",\"dateModified\":\"2025-05-07T11:31:28+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Programming reference\",\"item\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Directives\",\"item\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"NVEM0 Directive [D>=15]\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#website\",\"url\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/\",\"name\":\"SPLat Controls\",\"description\":\"OEM Embedded Machine Controllers\",\"publisher\":{\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#organization\",\"name\":\"SPLat Controls\",\"url\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-content\/uploads\/2024\/10\/logo.svg\",\"contentUrl\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-content\/uploads\/2024\/10\/logo.svg\",\"caption\":\"SPLat Controls\"},\"image\":{\"@id\":\"https:\/\/webprojects.cloud\/wordpress\/splatco\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"NVEM0 Directive [D>=15] - SPLat Controls","robots":{"index":"noindex","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"og_locale":"en_US","og_type":"article","og_title":"NVEM0 Directive [D>=15] - SPLat Controls","og_description":"The NVEM0 directive is used to mark the boundary between executable code and NVEM0 memory space. SPLat\/PC uses it to recognise where to start looking...","og_url":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/","og_site_name":"SPLat Controls","article_modified_time":"2025-05-07T11:31:28+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/","url":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/","name":"NVEM0 Directive [D>=15] - SPLat Controls","isPartOf":{"@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#website"},"datePublished":"2025-04-17T09:47:59+00:00","dateModified":"2025-05-07T11:31:28+00:00","breadcrumb":{"@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/nvem0-directive-d15\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/webprojects.cloud\/wordpress\/splatco\/"},{"@type":"ListItem","position":2,"name":"Programming reference","item":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/"},{"@type":"ListItem","position":3,"name":"Directives","item":"https:\/\/webprojects.cloud\/wordpress\/splatco\/knowledgebase\/programming-reference\/directives\/"},{"@type":"ListItem","position":4,"name":"NVEM0 Directive [D>=15]"}]},{"@type":"WebSite","@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#website","url":"https:\/\/webprojects.cloud\/wordpress\/splatco\/","name":"SPLat Controls","description":"OEM Embedded Machine Controllers","publisher":{"@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/webprojects.cloud\/wordpress\/splatco\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#organization","name":"SPLat Controls","url":"https:\/\/webprojects.cloud\/wordpress\/splatco\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#\/schema\/logo\/image\/","url":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-content\/uploads\/2024\/10\/logo.svg","contentUrl":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-content\/uploads\/2024\/10\/logo.svg","caption":"SPLat Controls"},"image":{"@id":"https:\/\/webprojects.cloud\/wordpress\/splatco\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/spl_knowledgebase\/3187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/spl_knowledgebase"}],"about":[{"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/types\/spl_knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/users\/1"}],"up":[{"embeddable":true,"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/spl_knowledgebase\/3171"}],"wp:attachment":[{"href":"https:\/\/webprojects.cloud\/wordpress\/splatco\/wp-json\/wp\/v2\/media?parent=3187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}