feat: GeViScope SDK integration with C# Bridge and Flutter app

- Add GeViScope Bridge (C# .NET 8.0) on port 7720
  - Full SDK wrapper for camera control, PTZ, actions/events
  - 17 REST API endpoints for GeViScope server interaction
  - Support for MCS (Media Channel Simulator) with 16 test channels
  - Real-time action/event streaming via PLC callbacks

- Add GeViServer Bridge (C# .NET 8.0) on port 7710
  - Integration with GeViSoft orchestration layer
  - Input/output control and event management

- Update Python API with new routers
  - /api/geviscope/* - Proxy to GeViScope Bridge
  - /api/geviserver/* - Proxy to GeViServer Bridge
  - /api/excel/* - Excel import functionality

- Add Flutter app GeViScope integration
  - GeViScopeRemoteDataSource with 17 API methods
  - GeViScopeBloc for state management
  - GeViScopeScreen with PTZ controls
  - App drawer navigation to GeViScope

- Add SDK documentation (extracted from PDFs)
  - GeViScope SDK docs (7 parts + action reference)
  - GeViSoft SDK docs (12 chunks)

- Add .mcp.json for Claude Code MCP server config

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

GeViSoft_SDK_Docs/chunk_005_pages_41-50.txt

@@ -0,0 +1,172 @@
+
+================================================================================
+PAGE 41
+================================================================================
+
+Example ofanEvent
+2.TheactionsforStartby,Onstart,andOnstopare:
+a)Startby:Contact3closed->InputContact (3,true)
+
+================================================================================
+PAGE 42
+================================================================================
+
+b)Onstart:RoutevideoIn3toVideoout2->CrossSwitch (3,2,0)
+c) Onstop:Clearvideooutput2->ClearVideoOutput (2)
+3.AfterthesetuphasbeensenttotheGeViServer, theeventcanbetestedwiththe
+GeViAPITestClient
+4.Ifyouleftclickinputcontact3theeventisstarted.Youwillseethatvideoinputstream
+3isroutedtovideooutput2.After5secondstheoutputisclearedagain.Youcanalso
+seetheeventbeingstartedinthecommunication log.
+5.Theeventcanberetriggered. Ifyouleftclickinput3againwhiletheeventisrunning,
+the5secondautostoptimestartsoveragain.
+6.YoucanalsostarttheeventbysendingaStartEvent message(StartEvent (ID,
+"MessageName") ).
+
+================================================================================
+PAGE 43
+================================================================================
+
+Alarms(optional)
+Duetothelargeamountofvideocamerasconnected tomodernvideosurveillance systems,
+operatorscannotobserveallthestreamsatthesametime.Moreover, onlycertainincidents
+areofinterestorneedaction.Therefore, itishelpfulthatapreselection ofthevideomaterial
+showntotheuseriscarriedoutbythesystem.Oftenspecialactionshavetobetakenifapar-
+ticularsituationishappening. Asanexampleassumethataparkinglotwithabarrieratthe
+entranceisbeingmonitored. Theoperatorissupposed toopenthebarrieraftermakingsure
+thatawaitingvehicleisallowedtoenter.Normally, theoperatorwouldhavetowatchthe
+streamofthecamerapermanently andactonit.IncaseslikethisGeutebrück systemscan
+assistbyprovidingalarms.Alarmsareverysimilartoevents,butoffermoreversatileoptions
+forcustomizing anddefiningrequireduserinteraction.
+AlarmOptions
+GeViSetoffersseveraloptionsforalarms.
+Option Description
+Name Alarmname–canbeusedinactions
+Description Fieldforthedescription ofanalarm
+AlarmID Alarmidentifier --canbeusedinactions
+Active Alarmscanonlybetriggered ifmarked Active
+Priority Alarmscanhaveapriority from1(high)to10(low).Ahigherpriority
+alarmwilldisplace alowerpriority oneifconfigured tobeshownon
+thesamemonitor group
+Monitor Group Several monitors thatareaddressed asagroupforeasieradmin-
+istration
+Cameras Listofcameras thatarerelevant forthealarm.Theirpictures are
+shownonthemonitor groupincaseanalarmoccurs
+Retriggerable Ifchecked, thealarmcanberetriggered byitsinitialactivator.
+Popup(Retrigger)
+
+================================================================================
+PAGE 44
+================================================================================
+
+Option Description
+Undoacknowledge
+(Retrigger)Ifset,thealarmhasalready beenacknowledged andthealarmis
+retriggered, thestatewillberesettonotacknowledged.
+Userspecific (Retrigger) Ifchecked, acustom listofactions canbeaddedwhichwillbe
+executed onaretrigger eventofthealarm
+StartbyAction Listofactions. Anyoftheactions willstartthealarm(logical OR)
+OnstartAction Listofactions. Alloftheactions willbesentonstart(logical AND)
+Acknowledge byAction Listofactions. Anyoftheactions willacknowledge thealarm(logical
+OR)
+Onacknowledge Action Listofactions. Alloftheactions willbesentonacknowledge (logical
+AND)
+QuitbyAction Listofactions. Anyoftheactions willquitthealarm(logical OR)
+OnquitAction Listofactions. Alloftheactions willbesentonquit(logical AND)
+Configuring anAlarm
+Configure analarmfortheparkinglotscenarioasdescribed above.Assumethatthedetec-
+tionofavehicleisdonebyasensorondigitalinput1(vehicleisdetectedonclose).After
+checkingifthevehiclemayentertheoperatormustopenthebarrier.Todosoheacknowl-
+edgesthealarmbypushingabuttonconnected todigitalinput2.Asthebarrieriscontrolled
+bydigitaloutput1theOnacknowledge actionmustopenthiscontact.Afterthevehiclehas
+passed,theoperatormustquitthealarmbypushingabuttonconnected todigitalinput3.On
+quitthebarriermustbeclosedbyclosingdigitaloutput1.Theparkinglotissurveilledbytwo
+camerasoninputs4and7.Duringthealarm,thesemustberoutedtooutputs1and2.
+1.AlarmsaredisplayedinMonitorGroups.FirstdefineoneInGeViSet.
+a)Server->Monitorgroups->Add
+b)Setthegroup’sNameandDescription toMonitorGroup1
+c)Addvideooutputs1and2tothegroup
+
+================================================================================
+PAGE 45
+================================================================================
+
+d) Leavetherestofthesettingsastheyare
+2.AddanewalarminGeViSet: Server->Alarms->Add
+a)IntheGeneraltab,setNameandDescription toParkingLot
+b)PresstheMonitorgroupbuttonandaddMonitorGroup1
+c)AddVideoinput4andVideoinput7toCameras
+
+================================================================================
+PAGE 46
+================================================================================
+
+AlarmSettings 1
+
+================================================================================
+PAGE 47
+================================================================================
+
+d)IntheActionstab,settheStartbyactiontoInputContact ,theGlobalContactID to
+1andChangedTo totrue.AddtheCaptionvehicledetected
+e)SettheAcknowledge byactiontoInputContact ,theGlobalContactID to2and
+ChangedTo totrue.AddtheCaptionbuttonacknowledged pressed
+f) SettheOnacknowledge actiontoOpenContact ,andtheGlobalContactID to1.
+AddtheCaptionopeningbarrier
+g)SettheQuitbyactiontoInputContact ,theGlobalContactID to3andChangedTo
+totrue.AddtheCaptionbuttonquitpressed
+h)SettheOnquitactiontoCloseContact ,andtheGlobalContactID to1.Addthe
+Captionclosingbarrier
+
+================================================================================
+PAGE 48
+================================================================================
+
+AlarmSettings 2
+
+================================================================================
+PAGE 49
+================================================================================
+
+3.Sendthesetuptotheserver
+4.TestthenewalarminGeViAPITestClient
+a)Clearvideooutputs1and2byright-clickingonthem.
+b)Simulatethearrivalofthevehiclebyleft-clickinginput1.
+c)Checkifthealarmistriggeredbyverifyingthatstreams4and7aredisplayedon
+monitors1and2.Notethattheoutputs’colorchangedtoredwhichindicatesan
+alarmfeed.YoushouldalsofindtheAlarmStarted ()actionintheCommunication
+log
+d)Acknowledge thealarmandopenthebarrierbyleft-clickinginputcontact2.Make
+surethatthisleadstotheopeningofoutput1andanAlarmAcked ()actionappearing
+inthelog.
+e)Quitthealarmbyleft-clickinginputcontact3.Thevideooutputs’colorshould
+changetogreenasthealarmhasfinished.Thebarrier(output1)shouldhaveclosed.
+
+================================================================================
+PAGE 50
+================================================================================
+
+Switching Video
+Thoughmonitorgroupsdatebacktoanaloguevideorecording, theideabehindthemcomesin
+handywhencomplexsituations aretobepresented tooperators. InmodernCCTVsystems
+mostofthesourcesaredigitalonesandtheviewersrunassoftwareondedicated consoles.
+Nevertheless theconceptofmonitorgroupscanstillbereproduced withGeutebrück’s sys-
+tems.Thestandardviewer--GscView--canberemotecontrolled toshowpredefined scene
+setupsinawaysimilartomonitorgroups.
+InthischapteryouwilllearnhowtoswitchbetweentwouserdefinedGscViewscenesbytrig-
+geringaGeViSoftalarm.Youwillhaveanormal4-by-4scenedisplaying 16channelsoflive
+footagefromaGeViScope. OntriggeringanalarminGeViSoft, GscViewwillbeswitchedtoa
+2-by-2scenedisplaying predetermined videochannels.
+Scenario
+Assumethefollowingsituation,whichiscloselyrelatedtoConfiguring anAlarminchapter
+Alarms:
+Configure analarmfortheparkinglotscenario.Assumethatthedetectionofavehicleisdone
+byasensorondigitalinput1(vehicleisdetectedonclose).Aftercheckingifthevehiclemay
+enter,theoperatormustopenthebarrier.Thishappensonacknowledging thealarmbypush-
+ingabuttonconnected todigitalinput2.Asthebarrieriscontrolled bydigitaloutput1,theOn
+acknowledge actionmustopenthiscontact.Afterthevehiclehaspassed,theoperatormust
+quitthealarmbypushingabuttonconnected todigitalinput3.Onquitthebarrierhavetobe
+closedbyclosingdigitaloutput1.Theparkinglotissurveilledbytwocamerasoninputs4and
+7.Duringthealarm,thesemustberoutedtooutputs1and2ofa2-by-2sceneMyScenein
+GscView. Beforeandafterthealarm,all16GeViScope channelsshouldbedisplayedina4-
+by-4sceneMyStartScene inGscView.