vrm_portal:troubleshooting_ccgx_vrm_connectivity
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-05-26 21:10] mvader |
vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-06-05 03:37] guy_stewart |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Trouble shooting Remote Console on VRM ====== | ====== Trouble shooting Remote Console on VRM ====== | ||
| - | Looking for how to trouble shoot transmission of data logs to VRM? See chapter 5 in the [[ccgx:start|GX Product manual]]. | + | Looking for how to trouble shoot transmission of data logs to VRM? [[https://www.victronenergy.com/live/ccgx:start#vrm_portal|See chapter 5]] in the [[ccgx:start|GX Product manual]]. |
| Not using a CCGX but a Victron Global Remote or Victron Ethernet Remote? See [[https://www.victronenergy.com/upload/documents/Manual-Troubleshooting-VGR-connectivity-EN.pdf|this document]] instead. | Not using a CCGX but a Victron Global Remote or Victron Ethernet Remote? See [[https://www.victronenergy.com/upload/documents/Manual-Troubleshooting-VGR-connectivity-EN.pdf|this document]] instead. | ||
| Line 30: | Line 30: | ||
| Note that it is not necessary for the CCGX to be addressable itself, and/or have a public IP address. Worded differently: traversing NAT translation is no problem. | Note that it is not necessary for the CCGX to be addressable itself, and/or have a public IP address. Worded differently: traversing NAT translation is no problem. | ||
| - | ====== Further debugging VRM communication (advanced) ====== | ||
| - | |||
| - | === Debugging the connection (advanced) === | ||
| - | Data is sent to the VRM Portal using HTTP POST requests to http://ccgxlogging.victronenergy.com/log/log.php. In case all above checks have been done, internet connection is sure to work, and still 'Last contact' keeps showing dashes: try [[https://www.victronenergy.com/live/ccgx:root_access|logging into the CCGX with ssh]]. And do: <code>wget --quiet -O- http://ccgxlogging.victronenergy.com/log/log.php</code> | ||
| - | The output should be a line containing the text 'vrm: OK'. If it does not, or wget hangs, check your network. Apparently communication is blocked. | ||
| - | |||
| - | === Using HTTPS instead of HTTP (advanced) === | ||
| - | If your provider is blocking HTTP requests (e.g. the wget request above times out or fails), you can change the CCGX to log to the VRM portal via HTTPS: | ||
| - | |||
| - | <code>root@ccgx:~# dbus -y com.victronenergy.settings /Settings/Vrmlogger/Url SetValue https://ccgxlogging.victronenergy.com/log/log.php</code> | ||
| - | |||
| - | Verify that the setting has been changed: | ||
| - | <code>root@ccgx:~# dbus -y com.victronenergy.settings /Settings/Vrmlogger/Url GetValue | ||
| - | 'https://ccgxlogging.victronenergy.com/log/log.php'</code> | ||
| - | |||
| - | It is then recommended to reboot the CCGX to apply the changes. (Alternatively, you could manually restart the vrmlogging services, but it's easier just to restart) | ||
| - | |||
| - | After you reboot, you should see the buffer size decrease: | ||
| - | <code># before rebooting | ||
| - | root@ccgx:~# dbus -y com.victronenergy.logger /Buffer/Count GetValue | ||
| - | 375 | ||
| - | # after rebooting | ||
| - | root@ccgx:~# dbus -y com.victronenergy.logger /Buffer/Count GetValue | ||
| - | 362</code> | ||
| - | |||
| - | |||
| - | |||
| - | \\ | ||
| ===== DISQUS ===== | ===== DISQUS ===== | ||
| ~~DISQUS~~ | ~~DISQUS~~ | ||
| - | |||
vrm_portal/troubleshooting_ccgx_vrm_connectivity.txt · Last modified: 2019-06-25 10:22 by mvader
