SBS Transit's iris system
-
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 -
Actually can the GPRS check bus arrival frm the int/terminal? no rite?
-
New services are likely like that,Try again after 2 mths time when they start to reschedule the timingsOriginally posted by SBS9806J:This is what happened when I tried for Service 5 -
i love it when that happens. get to see what rego r on that svc at that timeOriginally posted by SBS9806J:This is what happened when I tried for Service 5
ZYX -
Like that also can find perm busesOriginally posted by ZYX2005:i love it when that happens. get to see what rego r on that svc at that time
ZYX
-
The problem lies with the server programming or it's settings. New services or not, will kena.. 161 got it that day...Originally posted by carbikebus:New services are likely like that,Try again after 2 mths time when they start to reschedule the timings -
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?Originally posted by SBS9806J:This is what happened when I tried for Service 5 -
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? -
Same issue as 161. Somehow the system only register WAB only when the bus was about to leave.Originally posted by lemon1974: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?
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.