VBus Password / Authentication protocol

[Dave]

Hi guys,

I have started to play around with the vbus etc. I am using VB.Net
(V3.5 SP1 framework), and to begin with just experimenting in open the
comms paths and being able to read the data.

So far i have managed to read the continuous byte stream into my
application when directly connected through the serial port.

I am now trying to replicate the same thing by utilising the DL2
ethernet interface. Does anybody know the protocol of how the messages
regarding authentication are performed and the vbus password pushed
in, before the byte stream is accessible?

Cheers,
dave

[Daniel]

Hi Dave,

1. Connect to port 7053 on the DL2.
2. You receive: +HELLO
3. You send: PASS <insert remote password here>
4. You receive: +OK: Password accepted
5. You send: DATA

After that you receive the same data you would get using a serial
port.

Each of this received and sent message must be newline terminated.
Just try it with a telnet connection :)

You might get a "-ERROR: Password rejected" in step 4, which is quite
self-explanatory.

Good luck,
Daniel

[Dave]

Cheers Daniel,

I had already connected to the DL2 remotely and i say the bytes come
back at me, which i suspect where the +HELLO, but didn't note them
done to check and went and cleared my debugging info.

I have since found that the DL2 has stopped logging, and the live data
via the web interface has also stopped. Looks like i have managed to
lock up all the vbus traffic.

Now, does anybody know how to reboot the datalogger via th web
interface? i cannot see a command to do this anywhere (like routers
do!).

It is not easy when you are 120miles from the datalogger! i will get
the wife to power cycle it, but it would be good to be able to do this
via the web interface as i am sure it won't be the first time it will
need doing!

Cheers,
dave

[Daniel]

Hi Dave,

firmware version 1.4 fixes a bug causing the logging to freeze during
pending connections in authetication stage. Which firmware version is
installed on your DL2?

There is no direct link to restart the DL2, but if you change a
network setting you are asked to restart the DL2. After the
confirmation you are redirected to: http://<IP of your DL2>/dl2/
configuration/restart

Entering that URL directly has the same effect, without the need to
modify your settings.

Hope that information helps,
Daniel

[Dave]

Daniel

> firmware version 1.4 fixes a bug causing the logging to freeze during
> pending connections in authetication stage. Which firmware version is
> installed on your DL2?

The firmware is at version 1.4.

> There is no direct link to restart the DL2, but if you change a
> network setting you are asked to restart the DL2. After the
> confirmation you are redirected to:  http://<IP of your DL2>/dl2/
> configuration/restart
>
> Entering that URL directly has the same effect, without the need to
> modify your settings.

If i manage to lock it up again, i will try this.

> Hope that information helps,
> Daniel

Sure does!

Cheers,
dave

> On 14 Aug., 08:32, Dave <d...@dave-auld.net> wrote:
>
>
>
> > Cheers Daniel,
>
> > I had already connected to the DL2 remotely and i say the bytes come
> > back at me, which i suspect where the +HELLO, but didn't note them
> > done to check and went and cleared my debugging info.
>
> > I have since found that the DL2 has stopped logging, and the live data
> > via the web interface has also stopped. Looks like i have managed to
> > lock up all the vbus traffic.
>
> > Now, does anybody know how to reboot the datalogger via th web
> > interface? i cannot see a command to do this anywhere (like routers
> > do!).
>
> > It is not easy when you are 120miles from the datalogger! i will get
> > the wife to power cycle it, but it would be good to be able to do this
> > via the web interface as i am sure it won't be the first time it will
> > need doing!
>
> > Cheers,

> > dave- Hide quoted text -
>
> - Show quoted text -

[Dave]

Things are looking good!

I did manage to lock up the DL2 again and using the configuration/
restart url works.

I have also managed to now authenticate and stream the data over TCP/
IP into my custom app.

A couple of other message that can be handled as part of the
authentication protocol are;
-ERROR: Unknown command
-ERROR: Not Authorized to start data mode
+OK: Data incoming...

Another thing i have done is used fully Asynchronous comms, so there
is no application blocking on the UI. All the necessary comms are
contained in a re-usable class.

Also, i am able to close down the stream and underlying TCP socket
without locking the DL2. If i then try a reconnect it works!

I guess now i should be looking at some form of message parser from
the data stream.

For a first attempt into network comms.......i am one happy bunny.

Cheers,
dave