SBS Transit's iris system

last SG · 2018-02-06T07:01:10+00:00

Hmm... I don't mind that though... as long as it shows the next bus arrival (or next few buses) and show if the last bus has gone. And yes, make it availabl...

sbst275 SG

Has anyone tried for Sv 39 & 85? Laughing

At Yishun, whole day put "No Current Prediction"

^tamago^ SG

sometimes it happens. anyway they made some modifications to the system, cannot auto-refresh. have to debug again. Mad

sbst275 SG

So far now, can try Sv 191

These 2 svs confirm can show you "No Current Prediction" once it hits abv 60 mins...

At night can try 90... Laughing

For this, it's normal

carbikebus SG

Maybe due to the fact that Yishun are not SBST area?

ignoramus2006 SG

It was predicting fine when I tried last week. No such message. Dont know about accuracy though.

stooper SG

Should be the same what... Use GPRS...

^tamago^ SG

same here. trying for 2 weeks since the day it came out. 39 and 85 was working well.

khk SG

tested it on kent ridge terminal for 151
bus late by ard 5 min
n tt was at the terminal... prob the driver dilly dally b4 setting off

^tamago^ SG

i tested at central library before, show arriving until become no current prediction, then the bus comes. i think got something to do with the fact that sbst drivers like to leave a few mins late. Laughing

khk SG

but i tink the syst is gd… useful for those with super long waiting times like 151 etc. at least got some idea when the bus will come… better than waiting like 15-20 min for a bloody bus. a few min of delay is still fine w me

SBS9806J SG

OLE DB provider 'MSDAORA' reported an error. input stop sn 11 direcion 2 @v_headway_max:16 @v_headway_min:15 @v_svc_no_bst:005 loop svc flag N trip_day_type WEEKDAY run time 21.10 vehicle id 851 go to next bus vehicle id 1916 further checking tp_id or next_tp_id tp_id 0 Next_tp_id 106 go to next bus 2 - no avms updating by checking distance vehicle id 2595 loc_x 103.841423000 loc_y 1.317013000 stop_sn 16 stop_code 50061 vehicle id 2645 loc_x 103.830368000 loc_y 1.303373000 stop_sn 11 stop_code 13191 check angle vehicle id 2712 further checking tp_id or next_tp_id tp_id 106 Next_tp_id 68 loc_x 103.824348000 loc_y 1.283133000 stop_sn 3 stop_code 10371 check angle vehicle id 2743 go to next bus vehicle id 3657 go to next bus vehicle id 3662 go to next bus first Stop sn 3 first Stop code 10371 first Vehicle ID 2712 second Stop sn 0 second Stop code null second Vehicle ID null @From_Stop_eta:Apr 4 2007 1:37PM @To_Stop_eta:Apr 4 2007 1:54PM @P_Run_Time:16.15 @v_first_stop_date_time Apr 13 2007 1:42PM @v_timedelay 0.82 dir 2 pre stop 10089 sn 2 to stop 10371 sn 3 day type WEEKDAY app run time 2.180000000 @a 0.062195759 @b 0.301384211 @distance 0.400000000 @v_time_apportion 0.339 @v_runtime 15.67 *********compute AVMS off service (half way start) schd time************* @v_sched_version - off svc:51 ***********compute through SCS ************ @v_vehicle_id_list,*851*,*1916*,*2595*,*2645*,*2712*,*2743*,*3657*,*3662* @v_temp_str:*656* go to next bus - scs - bus id checked with avms @v_temp_str:*2743* go to next bus - scs - bus id checked @v_temp_str:*851* go to next bus - scs - bus id checked @v_temp_str:*3657* go to next bus - scs - bus id checked @v_temp_str:*3662* go to next bus - scs - bus id checked @v_temp_str:*2595* go to next bus - scs - bus id checked @v_temp_str:*2645* go to next bus - scs - bus id checked @v_temp_str:*2712* go to next bus - scs - bus id checked *********compute SCS schd************* [OLE/DB provider returned message: ORA-12500: TNS:listener failed to start a dedicated server process ] OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].

This is what happened when I tried for Service 5

chickenlittle2 SG

Actually can the GPRS check bus arrival frm the int/terminal? no rite?

carbikebus SG

New services are likely like that,Try again after 2 mths time when they start to reschedule the timings

ZYX2005 SG

i love it when that happens. get to see what rego r on that svc at that time

ZYX

SBS9806J SG

Like that also can find perm buses Laughing

off_service SG

The problem lies with the server programming or it's settings. New services or not, will kena.. 161 got it that day...

Zilchster SG

Is there anyway to get tat screen (those info with all the bus nos)? As in not by chance, but being able to access it regularly?

lemon1974 SG

sorry to dug out this thread..

today was at YCK Terminal.

saw 7425 of SV 76 leaving.. and 7481A just arriving. No other SV 76 bus at terminal.

So use mobile phone Iris to test, and it show that the next bus will depart in 10 mins (but does not indicate WAB), and the following bus will depart in 21 mins. by right the next bus leaving should be 7481A which is a WAB, but it was not show..

5 mins later, i try again and it show that it will depart in 5 mins and 16 mins but both are not show as WAB, as by the time, the next B9 on SV 76 have just reach YCK Terminal.

3 more mins later, i try again, and now it show the next bus departing is WAB... but the following bus is still not..

Something weird with the system? or have to wait till driver scan, then can update as WAB?

off_service SG

Same issue as 161. Somehow the system only register WAB only when the bus was about to leave.

I tried once the first stop after WRI showed "3 mins, 5 mins (WAB)". The system lagged as the first bus is long gone and the next bus is actually a WAB.

« Previous Page