Вы не вошли. Пожалуйста, войдите или зарегистрируйтесь.
ysv, glad to hear that, we'll be happy to know about you progress in this implementation, you are always welcome to share your experience with us!
Awesome
Hi ,
If one Depot has multiple Routes , is it possible to create a never expiring Nimbus locator link only for a specific route ?
What happens when one vehicle / unit is scheduled to run on different routes ?
Hi, Gabbar!
Yes, it is possible. After our latest update came out you can limit the number of routes available on the link by selecting a group of routes to be displayed. So you can create a group of routes containing only one route you want to see.
Speaking of the second question, the units that are moving in real time are displayed on the map. The locator link shows all the units assigned on the route anyhow. There shouldn't be any problems with that.
Thanks Suvi , we tested this . This looks great
Hi ,
We did a simple app using Nimbus Locator link which works fine 
At the same time we are in the process of creating an more advanced app using API, with this we need your advice on how to get vehicle's live movement , as we understood it is done using an additional service ? how can we get some help in this ?
ysv, glad to hear that, we'll be happy to know about you progress in this implementation, you are always welcome to share your experience with us!
Like to shear with you and application we develop in our company dedicated to school buses, we have 3 main fixtures: 1. the web application, 2. the user app 3. The driver app. It was designed for keep the control of the pickup and drop of the students, the parents can check were the child is moving all the time when he is on the bus, receive and alert when the bus is near his location and as well when the bus is dispatch from the school, we are looking forward if we can expand this through you NIMBUS app, to another level of services, such us corporate transportation, large company’s employs transportation, and more, adding fixture’s like final user app in which they can be alert of the proximity of the bus sending and SMS or an email to the cell app, a menu that can provide communication with the dispatch center and driver, as well and app to the driver that can see the rout he have to accomplish in his cell or table, with fixtures such as confirmation that the passenger has been pick up, or not, interconnected with hardware barcode readers that cap the ID of the user etc.
If you like to see what we have we can send a PowerPoint presentation to and email address that you can provide us.
David
Hi ,
We did a simple app using Nimbus Locator link which works fine
At the same time we are in the process of creating an more advanced app using API, with this we need your advice on how to get vehicle's live movement , as we understood it is done using an additional service ? how can we get some help in this ?
I suppose You may consume live location updates of buses from Nimbus via MQTT. The best way to investigate this possibility is to request Gurtam Labs via e-mail.
Where can i find more information about gurtam labs
Hi, siju!
Gurtam Labs is the name of the team responsible for web apps. What information are you interested in?
Hi, dkochk!
I have carefully reviewed the presentation that you sent to our support team, thank you very much for sharing your experience. First of all I'd like to point out that for now NimBus does not imply any kind of mobile applications. You can develop a mobile app which will use our locator link for providing end users or drivers with the information on the way of passing of depot routes, stops and the upcoming transport.
Also could you please specify some points for the better understanding?
final user app in which they can be alert of the proximity of the bus sending and SMS or an email to the cell app
Speaking of the SMS or email notifications, in the first place NimBus was developed for dispatchers so they can get notifications they need (hurry and delay of units, stops skipped, etc.) in the web interface online. And as I get it, you need notifications for passengers to be ready for boarding, right?
a menu that can provide communication with the dispatch center and driver
As we are talking about NimBus, it provides you with interface for dispatchers. In your case, who should be able to communicate with whom (dispatcher, driver, passenger)?
app to the driver that can see the rout he have to accomplish in his cell or table, with fixtures such as confirmation that the passenger has been pick up, or not, interconnected with hardware barcode readers that cap the ID of the user etc.
As well as the apps you mentioned above, this app can be developed on the base of NimBus using our API. Some of our partners have already had this experience. However, for now we are not developing any kind of mobile application. But we carefully consider all the ideas for extending our API in order to cover your clients' needs.
Hi Suvi,
thanks for your replay, and to answer your questions
1. Yes to get ready for boarding the unit, with and alert either in distance or time from the the pick up point.
2. The communication have to be in between the 3 elements; driver, dispatcher and passenger.
Now you can see user's current location in the Locator!
suvi, Please explain more
hhamedk, if positioning is allowed in your browser settings, clicking on the button centers the map on the user’s current location.
https://docs.wialon.com/en/hosting/nimb … _interface
Hello,
Is there any option to show ETA ( estimated time of arrival ). I noticed the StopPanel function in NimBus APIs return an ETA, but it's merely a counter that counts down current server time against the planned arrival time for the bus, which might not be necessarily accurate.
Do you have this implemented with real time ETAs?
Thanks.
Hi, karim!
For now ETA in the Locator is implemented as a simple algorithm. A unit is expected to arrive to the first stop-point on time according to the schedule, then after every visit of a stop the system uses time of the unit's last deviation from the schedule for calculating ETA for all the following stops. It is expected that they will be visited with the same deviation. Information is updated after every visit of the following stop.
