User Tools
users:dagnall53:node_programming
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
users:dagnall53:node_programming [2019/03/27 12:25] dagnall53 |
users:dagnall53:node_programming [2019/03/27 12:26] (current) dagnall53 |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| ---- | ---- | ||
| - | + | ===== Programming a Stationary Node ===== | |
| - | + | ||
| - | ==== Programming a Stationary Node ==== | + | |
| From WiRocS V 15, I have been saving the Sketch files with them setup for Stationary Nodes. | From WiRocS V 15, I have been saving the Sketch files with them setup for Stationary Nodes. | ||
| Line 44: | Line 42: | ||
| - ** Use (RocView, Programming, Rocnet)** | - ** Use (RocView, Programming, Rocnet)** | ||
| - | ==== Programming a LOCO decoder ==== | + | ===== Programming a LOCO decoder ===== |
| -To use the WiRocS Code for a "Mobile" (Loco) controller, you will need to use the Directive '#define _LOCO_SERVO_Driven_Port 1 | -To use the WiRocS Code for a "Mobile" (Loco) controller, you will need to use the Directive '#define _LOCO_SERVO_Driven_Port 1 | ||
| Line 57: | Line 55: | ||
| ---- | ---- | ||
| - | ==== Forcing compiler options if there are setup issues ==== | + | ===== Forcing compiler options if there are setup issues ===== |
| I have tried to make the code react sensibly when programmed to a blank board, but it is difficult to cover all eventualities. So, if you have any problems with the code repeatedly crashing after your upload, it may be that it is having trouble with internally set (wrongly or not at all) EEprom settings. If you are experiencing this issue, I have some "Force" defines to set internal variables. These are probably not required, but: | I have tried to make the code react sensibly when programmed to a blank board, but it is difficult to cover all eventualities. So, if you have any problems with the code repeatedly crashing after your upload, it may be that it is having trouble with internally set (wrongly or not at all) EEprom settings. If you are experiencing this issue, I have some "Force" defines to set internal variables. These are probably not required, but: | ||
| Line 102: | Line 100: | ||
| ---- | ---- | ||
| - | ==== Direct Write using Binary Files ==== | + | ===== Direct Write using Binary Files ===== |
| It is possible to directly write a compiled Binary file to an ESP 8266 without using Arduino. | It is possible to directly write a compiled Binary file to an ESP 8266 without using Arduino. | ||
| {{ :users:dagnall53:prog.jpg?200|}} For the ESP8266, you can use the NodeMCU Firmware Programmer. [[https://github.com/nodemcu/nodemcu-flasher]] | {{ :users:dagnall53:prog.jpg?200|}} For the ESP8266, you can use the NodeMCU Firmware Programmer. [[https://github.com/nodemcu/nodemcu-flasher]] | ||
users/dagnall53/node_programming.txt · Last modified: 2019/03/27 12:26 by dagnall53
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
