Eview EV-07B registered as a MiniFinder 2 is not connecting

DAVIDCHANIN

Hello. It’s well established that the (GSM) EV-07S and (“3G”) EV-07W made by Shenzhen Eview follow the protocol for “MiniFinder” and can be registered here as such, but I’ve never used any server but Eview’s smart-tracking.com which they are shutting next month, making me search now for a tracking provider that can handle different types of units.

But the EV-07B is very different than the older units and it has a very different protocol with many more settings and alarms possible. Eview sales manager told me that besides their new smart-locator.com where I’ve had numerous problems, the only other place in the entire universe of pay-for-tracking-industry where this tracker can be registered is Wialon.

So I looked up the EV-07B at Wialaon and sure enough it had 23 units registered as “EV-07B” and 4 were online simultaneously. That’s quite a number for such a new device. Please forgive my error but I did not realize that creating a personal-use account for three devices at Ruhavik might be a very different thing than opening an account at Wialon.

You’re all under the same company, Gurtam. It really seems that you don’t support the Eview EV-07B through Ruhavik, because, well, there’s no mention of the EV-07B on this forum and also in trying to find out why Ruhavik tells me it’s been offline always, i’ve looked at the message trace and have created numerous alerts, and nothing is sent to, or nothing recognizable is sent to 193.193.165.166 port 21535 which is what it gave me for MiniFinder Zepto 2.0 and it seems to be a consensus at the Traccar forum that the EV-07B follows what they refer to there as the “minifinder2” protocol. And at Traccar forum they have several threads mentioning the EV-07B and how it differs from the older EV-07S and EV-07W.

Should I give up on Ruhavik and try to do it through Wialon as a Personal Account? Please advise.

DAVIDCHANIN

Here’s the thread at Traccar forum; and the ZIP file with the two protocols they found at gurtam.com was still at Google Drive a few days ago:

https://www.traccar.org/forums/topic/device-support-for-the-new-eview-units/

DAVIDCHANIN

OK. I don’t give up easy. I still don’t understand why GPS-TRACE might not support the Eview EV-07B when it’s fully supported at Wialon for paying customers. Why would they have different lists of supported hardware where the EV-07B at Wialon now has 16 registered units, down from 23 last week, but the EV-07B is not in the list of hardware at gps-trace, but if i click again there for second search it connects me instead with the Wialon hardware list. There is some progress and I’m getting closer to having it working. I’ve been using the IP for gps-trace, 193.193.165.166 but was using the port 21535 that gps-trace listed as the port to use for the MiniFinder Zeppo 2.0 (because the Traccar people and owner seemed to be in agreement that EV-07B would work if defined to be a “minifinder2″). And that’s the only MiniFinder in the GPS-TRACE hardware list with a version 2. Well, i kept IP the same but changed port to 21924 because that’s what Wialon is listing for the EV-07B.

The progress is that Ruhavik in attempting to connect with my EV-07B is no longer just offline and was never heard from, no events, no data. Now it’s getting something short of a full GPRS connection, or it’s using an incompatible protocol because now Ruhavik keeps looping telling me “Connecting” and then that’s replaced with “Something went wrong while connecting with device” and then “RECONNECTING” every 2-3 seconds or so, an apparent infinite loop maybe stopping only if I shut device to stop wasting data. It’s finding my device, which is sending GPRS data to port 21924 but then it’s detecting an error, maybe due to GPS-TRACE not having the exact protocol for the Eview EV-07B while Wialon pay customers do have available the exact protocol for their EV-07B.

Besides posting here about this, what do you do if a certain device is in the hardware list for Wialon paying customers of Gurtam, but it’s not on the hardware list for the Ruhavik server of the gps-trace of the same company, Wialon?

ashe

DAVIDCHANIN Hello!
Please try to identify your tracker on id.wialon.net as one of the devices EV-200, MiniFinder Atto, MiniFinder Zepto Plus, MiniFinder Atto Pro, MiniFinder Zepto, MiniFinder Nano, MiniFinder Pico, EV-07B.
If your tracker is determined, take a screenshot, write down the name of the model of the tracker and the identified ID (may coincide with the IMEI, may be part of it with zero or no)
After that, return to the application in the unit settings (unit menu - Settings - Common Settings), specify the determined model and ID. After that, configure the tracker on the defined server and port.
If you define the tracker as a type of device that is in our application, then please set up the tracker on it.
If, after being defined on id.wialon.net, the tracker will not be detected in the application (after setting on port and server in the application), write to us about it and please attach a screenshot where the tracker was identified on id.wialon.net.
If this type of device, as determined by your tracker, is not in our application, then please also write about this with the attachment of a screenshot where the tracker was identified as this type of device on id.wialon.net.

DAVIDCHANIN

The full message screens at Ruhavik when trying to connect with device alternate between Reconnecting and Something went wrong while executing request, RETRY LOAD DATA (latter in blue).

DAVIDCHANIN

ashe
It says “you do not have permission to do that” in a red popup at bottom left when I try to add an imagge ussing the raphic icon in the icons to the right of Post Reply in black.

Here are Yandex Disk links to the screenshots you want. Or some or most of them,

https://yadi.sk/i/vsxK-P_9rz2okw
https://yadi.sk/i/Sz4ikECGDcB6Lg
https://yadi.sk/i/kzvgmtDcDKHvnQ
https://yadi.sk/i/FcGaIEogn_kLnA
https://yadi.sk/i/3vPaURsJKgIZ5w

https://yadi.sk/i/IjjCIkiGTw-yOA!

https://yadi.sk/i/3vPaURsJKgIZ5w

DAVIDCHANIN

ashe Did you delete the posts I wrote giving more information? It was in GPS devices section.

DAVIDCHANIN

If, after being defined on id.wialon.net, the tracker will not be detected in the application (after setting on port and server in the application), write to us about it and please attach a screenshot where the tracker was identified on id.wialon.net.
If this type of device, as determined by your tracker, is not in our application, then please also write about this with the attachment of a screenshot where the tracker was identified as this type of device on id.wialon.net.

YES YES YES YES YES YES that is what i’ve been saying all along. OK, you want some visual evidence. i’ll do that.

Just go to the hardware list for GPS-Trace and try to find EV-07B and then go to Wialon and find it. Easy peasy.

There are NO Eview traclkers listed for GPS-TRACE. NONE-WHATSOEVER. and certainly no EV-07B.

Read the thread i linked at Traccar, please. I didn’t want to quote that entire post. So you need to read it there. I won’t copy it here without permission from them.

It seems my easiest way to get tracking working is to request an account at Wialon and get a personal account there so this tracker ofmine, Eview EV-07B can be tracked. And then i’ll have proof showing that it works at Wiaalon but doesn’t work at GPS-TRACE.

ashe

DAVIDCHANIN Hello!
At the moment we have added EV-07B to the list of devices.
In the unit settings, you can choose:
Device Category - Legacy
Device Type - EV-07B

Previously, we wanted you to initially try to identify your tracker on id.wialon.net in order to be sure exactly that your tracker is detected and with which id.
If there is a problem when connecting the tracker according to the new setting, then please first try to define the tracker on id.wialon.net as one of the devices that we specified earlier.

On this forum https://forum.gps-trace.com/ we did not delete your posts, if you have queries about the forum of our other product, please try to clarify information about it there.
Since Wialon and GPS-Trace (Ruhavik) are different products, different people are currently involved in their support and unfortunately we cannot know for sure whether you left information on the forum of our other product.

We apologize for any inconvenience caused.

DAVIDCHANIN

Thank You for adding the EV-07B to your list of Legacy Hardware under the name EV-07B. Of the new GPS trackers from Shenzhen Eview the EV-07B is the most popular by far, with 28 of the EV-07B shown as enrolled at Wialon, with 9 of those now active and connected to the Wialon server. Wialon had a statement somewhere saying they’d support all models made by Eview so if you have a new and apparently unsupported model you’d best enquire if that model follows the protocol for a unit listed. There are four supported devices from Eview now listed at https://gurtam.com/en/gps-hardware, the EV-07B, EV-202, EV-09, and EV-04. http://www.eviewgps.com shows Eview now claims seven current models being sold: EV-201, EV-202, EV-05, EV-07B, EV-08, EV-09. and EV-04. Presumably, most of the others can be emulated as some type of Minifinder.

I’m very grateful for adding the EV-07B hardware protocol to Ruhavik and GPS-TRACE and I was considering what to post here because the initial list of Telemetry values does not include anything about battery level or signal strength but tonight I’m very glad to see that this was fixed without me mentioning the shortcoming. Right off the bat the very first thing to look at is battery strength and the phone signal strength can likewise be very important because I’ve had cats wearing a GPS go into the crawlspace under a neighbor’s house most probably to catch rodents. To make it clear, it still seems that ever since the EV-07BX was added it is not possible to request that the unit send current data on battery and signal strength because those are not included in the list of Telemetry values available under Settings, View Settings, Telemetry, shown below:

a_ctivity
alarm_code
channel.id
command
description
mac
mileage
pedometer
position.altitude
position.direction
position.hdop
position.latitude
position.longitude
position.satellites
position.speed
seq
server.timestamp
status
timestamp

[end of Telemetry list for EV-07B]

In contrast, the Telemetry list for my EV-07S and EV-07W units registered as minifinder Legacy Hardware is as follows:

battery
battery_level
channel.id
fall_alarm
gps_module
gsm_csq
motion_alarm
move_alarm
over_speed
position.altitude
position.direction
position.latitude
position.longitude
position.satellites
position.speed
sats_in_view
server.timestamp
signal
timestamp_
[end of parameter list for minifinder]

DAVIDCHANIN

Sorry for the mistake, but the EV-07BX doesn’t report battery strength or GSM signal strength. The older units emulated as minifinder do in fact report both battery strength and phone signal strength.

dapi

DAVIDCHANIN Hello.
We would like to specify if your issue has been resolved or could you please describe it in more details. Probably you are using other tracker models and would like to add them?
In the Unit menu – Settings – View - Telemetry you can see a list of parameters. When you create a unit there are no parameters and they will appear when your tracker sends them and will not appear if it does not send.
To check the information your tracker is sending you can also choose Unit menu – Tools – Toolbox where below you can see messages section.

DAVIDCHANIN

dapi, the list of Telemetry values shown for the EV-07B by the Ruhavik software was given above. Every GPS tracker under the sun reports information about battery strength and every GPS tracker under the sun reports some information about cellular signal strength.
Neither of those value, neither battery strength or cellular signal strength, can be chosen from the Telemetry list that was made available after my request for such. It’s an obvious oversight and should be very easy to fix on your end.

Every time the tracker reports its location it ALWAYS sends back the back the current battery strength. Number of satellites in view and number of satellites used for position are indications of GPS signal strength.

If you could make just two parameters available, the vast majority of GPS users would like to see battery strength and cellular signal strength.

Neither of those is available for the EV-07B as it was initially set up here as a Legacy Device.

Neither battery strength or any indicator of cell signal strength are on the list from which four can be selected:
a_ctivity
alarm_code
channel.id
command
description
mac
mileage
pedometer
position.altitude
position.direction
position.hdop
position.latitude
position.longitude

DAVIDCHANIN

One “issue” was fixed, yes, by adding the EV-07B.

But another “issue” was created by having a new device, EV-07B, on your list, but with no possibility to have its battery strength or cell signal strength be selected from the menu of Telemetry values and reported by the tracking software.

That’s a problem. It was a problem created so to speak by solving the issue of the very popular new device being supported at Wialon but not supported by Ruhavik. Solving one problem led to another as is usually the case.

But not supporting the device in any way whatsoever was a far greater problem, both in impacts on those device owners who wish to track them, and also a greater problem for the maintainers of Ruhavik, because adding a whole new device is a much greater task than making those two very vital items of information visible to those using that type of device.

DAVIDCHANIN

Battery strength is usually reported as an integer percentage, value between 0 and 100 inclusive.

Signal strength could be reported in any number of ways, any of them much preferable to having no information at all.

But besides cell strength, there’s the use of different protocols and frequency bands with the device picking one versus another. It would be nice in my case to know if my EV-07BX-A (that’s the full designation on the box) … where the BX after the 07 stands for it being the 4G variant, and the -A suffix stands for frequency bands chosen for the American market.

I don’t know what Eview uses in their telemetry data to tell their server at smart-locator.com whether my 4G device is using the 2G band or if it’s using a 3G or 4G band. But if they have some kind of simple indicator, like 2G versus 3G versus 4G, that would be really good to know.

The EV-07B is sold both as 2G device and as “4G” devices. The one I’m using is designated

ashe

DAVIDCHANIN Hello!
We see that you do not fully understand how the telemetry data works in the application. We will try to explain.

The telemetry list displays for selection those parameters that have already been sent by your tracker at least once. These parameters are not related to the device type and cannot be added by us. They are automatically determined from the parameters that this particular tracker sent.

So for trackers of the same model, for different users, the given list of these parameters may not coincide. For example, because one tracker is configured by the user to send some data and the other is not.

According to the documentation (https://gurtam.com/ru/gps-hardware/personal/ev-07b#parameters) tracker of your model can send as part of the status, for example, such parameters as GSM signal strength and Battery level. However, these parameters are not sent from your device and therefore you cannot select them in the telemetry list.

You can check what data is received from your tracker in the unit menu - Tools - Toolbox - the section with messages at the botton. If you click on a message, a side panel will open and you can see all the parameters and their values that came in this particular message.

At the moment, your tracker does not send the parameters you need, so please try to check, in accordance with the instructions for your tracker, what settings are required for the tracker to send these parameters (data on its status).

DAVIDCHANIN

Ashe, Thank You for your explanation of the parameters available for Telemetry reporting, the four maximum which can be displayed as the last datum last received for up to four parameters the user can choose from the proffered Telemetry list.

re “At the moment, your tracker does not send the parameters you need, so please try to check, in accordance with the instructions for your tracker, what settings are required for the tracker to send these parameters (data on its status).”

Prior to you adding E7-07B to your list of supported Legacy hardware I had been using the manufacturer Shenzhen Eview’s tracker website and Android app, smart-locator.com view travel paths and the EV-07B most certainly sent constant reports of battery strength and cell signal strength because without any action whatsoever needed by the user at any point of adding a new device or choossing from settings and options avaailable those two parameters are constantly and always displayed whenever its position is reported on a map. Always and forever seemingly, and this goes back several generations of their manufactured trackers to the original Minifinder Pico made for Sweden, and it was also always the case for every tracker that Shenzhen Eview’s predecessor to smart-locator, at their defunct website smart-tracking.com.

So, given what you said: ?what happens to the tracker to make it stop sending battery and cellular strength when I changed the destination of the GPRS packets from its default of smart-locator.com at port 5050 to the IP and port for Ruhavik?

The data connection through the mobile carrier APN is constant, and the tracker was kept on during the changeover from smart-locator back and forth to Ruhavik. Why would it always and forever, no matter what, report battery and cellular strength to smart-locator but never, no matter how hard i might try, can it report those values to Ruhavik.

The only reason I could imagine would be that the tracker itself is told by the smart-locator server to report those data to the server. User option has nothing to do with it. The user can’t turn it off and can’t turn it on. It’s apparently worked out between the tracker and the server. This tracker was kept turned on and the mobile connection maintained and it went from sending battery strength and cell strength to smart-locator and it hasn’t sent that data to the Ruhavik servers.

Maybe the server is telling the tracker what data to send. Is there any other possible explanation? The tracker went from sending those data every single transmission to not sending them ever? What could explain that?

DAVIDCHANIN

P.S. Thank You for being patient and trying to explain. Prior to now i’ve only used tracking servers that were included as a package to buyers of trackers. I’ve figured out that in order to have thsi tracker use a new set of geofences that the simplest solution was to entirely delete the tracker from the server and lose the tracker history, and then add it as a new device of the same type and IMEI as before. This “reset” the geofences and got rid of the old ones so that a new set of fences could be defined. So that was done and deleting and re-adding the EV-07B didn’t do anything to reset the Telemetry data choices to include battery and cell strength.

That fix was only done once but there have been several times in which I went back and forth between smart-locator and the Ruhavik servers. Is that problematic? Why would data sent change when the IP and port is changed?

DAVIDCHANIN

Hmm. I don’t know what they might call the battery strength in that list or how it’s encoded. Could it be they call it activity?

But channel.id, seems like it could be a way to encode the frequency band and maybe strength as well. Mine says now
channel.id: 14432 but that changes. Also there’s activity: 137584

If everything the server needs to obtain from the device is on that list then the battery level and cell signal would have to be encoded somehow in one or more of these parameters:
activity, channel.id, ret_code
Telemetry values
Max 4 values
4 / 4
Labels for selected telemetry values
status
status
activity
activity
channel.id
channel.id
ret_code
ret_code
activity
alarm_code
channel.id
command
description
flag
mac
mileage
number
pedometer
position.altitude
position.direction
position.hdop
position.latitude
position.longitude
position.satellites
position.speed
ret_code
seq
server.timestamp
status
timestamp
user_id
wifi_mac

DAVIDCHANIN

Battery strength 0-100 could be encoded as a one-byte (8 bit) integer with room to spare for codes signifying various error conditions. So if say channel.id has both the frequency band, the “G” level, and the exact band # being used, it could all fit in one 32-bit integer that they might name channel.id .