Resolve these inputs before equipment selection and quotation comparison.
Map every transformer, cabinet, branch, conductor transition and informal supply boundary. PLC planning begins with the real electrical route, not a simplified single-line drawing that ignores field changes.
Survey terrain, vegetation, mounting height, structures, interference and seasonal changes. A nominal LoRA distance is not the achieved route distance and should not replace pole-by-pole coverage review.
Define which poles, sensors and scenes belong to each CH-800 Gateway; document neighboring-zone coordination, storage limits, alarm routes and the exact boundary when one gateway is unavailable.
Separate ordinary telemetry, lighting commands, safety events, configuration updates and maintenance traffic. Priority rules should prevent bulk data or repeated nuisance events from delaying essential field actions.
Keep approved schedules, scenes and fallback rules at the appropriate field level. External-network loss should remove remote visibility only within declared boundaries, not erase essential local route behavior.
Where hybrid PLC and LoRA are supplied, commission each path independently before testing transfer and restoration. A second radio or conductor path has little value if both share an undocumented power or gateway dependency.
Synchronize timestamps and maintain stable asset addresses across poles, sensors, cabinets, gateways and the owner platform. Otherwise alarms, video events, energy data and maintenance closure cannot form a defensible evidence chain.
Test cable faults, radio interference, gateway restart, external-network loss and configuration restoration. Record visible lighting behavior, lost or retained events, transfer time and the controlled return to normal operation.
Document cloud, sovereign on-premises or closed-network deployment, user roles, remote access, update authority and third-party interfaces. Security review should follow the selected architecture rather than assume that one communication medium resolves every risk.
Specify the tools, diagnostic views and reference limits used to distinguish a field-device fault, power problem, PLC route issue, radio issue, gateway issue or external-network interruption before dispatch.
Record gateway, address, radio-airtime, storage and polling capacity for the installed stage and planned expansion. A route that works as a short pilot still needs a declared path to full corridor scale and future review.
Provide an owner-observed drill using the final route map, account roles, configuration backup and spare gateway or controller process. The result should show who recognizes the fault, who authorizes restoration, which local scenes remain active, how event history is reconciled and how the approved version is confirmed after service returns. Keep the signed drill record with the final topology, device list, firmware references and restoration checklist so later maintenance teams can repeat the process without relying on one original commissioning engineer.
Recommended direction: Choose PLC, LoRA or hybrid communication by feeder topology, conductor quality, terrain, radio conditions and recovery needs. Preserve approved route scenes in the CH-800 Gateway and field layer so external-network loss does not remove essential local operation.
Interconnected PLC and LoRA Bicycle Track Lighting Communication should be evaluated as an operating system, not as a collection of impressive devices. The proposal must connect every important claim to a route drawing, configuration, calculation, test method or owner-held record. Define responsibility between the owner, consultant, EPC, luminaire supplier, field-control provider and any video, power or communication partner before procurement.
| Decision | Recommended Basis | Evidence Before Award | Acceptance Outcome |
|---|---|---|---|
| Operating boundary | Define users, zones, speed policy and priority scenes. | Route plan, control narrative and responsibility matrix. | Correct zones respond in normal and abnormal scenarios. |
| Field layer | Select sensing, luminaires, controllers and mounting from site inputs. | Coverage, photometric and electrical documentation. | Installed behavior matches approved configuration. |
| Communication | Choose PLC, LoRA or hybrid from topology and survey evidence. | Route map, channel test and recovery logic. | Commands, alarms and records survive agreed faults. |
| Local continuity | Store approved schedules and fallback scenes locally. | Offline boundary and restoration procedure. | Safe local operation continues within declared limits. |
| Handover | Transfer accounts, maps, backups, logs and maintenance rules. | Handover index and owner access test. | Owner can inspect, export and restore the system. |
Communication media solve different physical problems. PLC uses the available powerline but is affected by feeder boundaries and noise; LoRA avoids those conductors but depends on radio planning. Hybrid design is valuable only when both paths and their recovery logic are commissioned.
Use this matrix during concept review, tender clarification and pilot planning. Values shown in a proposal remain design inputs until the selected hardware, route geometry and operating policy are verified.
| Zone / Condition | Primary Risk | Engineering Direction | Owner Evidence | Acceptance Focus |
|---|---|---|---|---|
| New feeder, controlled wiring | PLC conditions may be predictable and economical. | Measure conductor route, transformer boundaries and device density before finalizing PLC. | Feeder drawing and noise/attenuation survey. | Command success, response and representative load conditions. |
| Aging or mixed supply | Branches, residential taps and decades of wiring can disrupt PLC. | Evaluate LoRA or hybrid route after radio and topology survey. | Pole survey, power sources and interference record. | Each path separately, then combined recovery. |
| Mountain bends / terrain | Radio shadow and long route segmentation. | Gateway placement, relay design or PLC path where conductors are suitable. | Coverage model and physical survey. | Worst-point signal, response and fault restoration. |
| Cabinet or gateway zone | Single-zone failure may affect many poles. | Declare boundaries, local schedules, backups and restoration ownership. | Zone map, configuration version and spare strategy. | Gateway loss, replacement and configuration restore. |
| External network loss | Cloud commands and remote visibility unavailable. | Continue agreed scenes locally and retain records for later synchronization. | Offline policy and storage limits. | Disconnect, operate, recover and reconcile events. |
| Power outage | Both data paths may remain unavailable if devices lose power. | Separate communication redundancy from electrical reserve; define backed-up scope. | Power one-line, reserve calculation and priority loads. | Outage duration, restart order and data integrity. |
The matrix is deliberately route-based. Nominal ranges, wireless distances, battery capacities or analytic features should not be copied into a tender as achieved performance without the related design assumptions.
The bicycle track lighting and safety management system links motion detection with neighboring lighting zones. When an approved target enters a sensing area, the current segment and selected segments ahead rise to their agreed lighting scene. The occupied scene remains active while detections continue; brightness returns gradually to the approved standby scene after the hold period expires.
The system should be judged by safe scenes, local fallback, alarm traceability and owner-held records. A useful evidence chain includes CH-800 Gateway zones, FAT/SAT files, offline tests, communication-route records, alarm logs, maintenance closure and configuration backups. AI-assisted analysis becomes useful when these field records are dependable.
Sensor reports movement within the configured field of view.
Target direction, coverage, mounting height and nuisance sources are checked on the track.
Gateway or local group logic raises the selected segments ahead.
Neighbor map, response time and uninterrupted visibility are demonstrated in both directions.
Further detections renew the occupied scene and hold timer.
Continuous groups do not cause premature dimming or repeated brightness oscillation.
The zone returns to its approved background scene after the clear period.
Standby illumination and transition rate match the approved lighting design.
Events, commands, energy and faults are retained according to the project scope.
The owner can inspect source identity, timestamps and configuration version.
The objective is a readable corridor ahead of the user, with smooth transitions between occupied and background scenes. Advance lighting distance should be selected from route geometry, speed, pole spacing, detection range and total system response. A sensor range is not automatically the same as the distance over which neighboring luminaires can be commanded.
For initial planning, selected sensing arrangements may be evaluated around 50–100 m approaches where the chosen sensor and mounting geometry support that coverage. This remains a design assumption until measured on site. A long illuminated zone can be prepared by group control even when the initiating sensor sees a much shorter local area.
| Illustrative Speed | Travel Speed | Time to Travel the Stated Distance | Design Use |
|---|---|---|---|
| 30 km/h | 8.33 m/s | 50 m ≈ 6.0 s; 100 m ≈ 12.0 s | Use the available lead time to verify detection, command execution and visible brightness rise. |
| 40 km/h | 11.11 m/s | 50 m ≈ 4.5 s; 100 m ≈ 9.0 s | Include bends and cross-zone travel; confirm the next segment is ready before entry. |
| 50 km/h | 13.89 m/s | 50 m ≈ 3.6 s; 100 m ≈ 7.2 s | Check the fastest permitted service scenario, including delayed or repeated detections. |
An ordinary evening, a crowded training session and an organized race do not need identical dimming behavior. The operator should be able to select an approved scene with a clear scope, start time, end time and restoration rule. Event control should be available through authorized local operation as well as the agreed platform.
During a race, steady lighting through occupied competition segments may take priority over occupancy savings. During quieter periods, local detection can raise selected zones while the rest remain at the approved background level. Maintenance scenes should identify the working area and preserve visibility for approaching riders.
| Scene | Lighting Policy | Trigger or Authority | Acceptance Focus |
|---|---|---|---|
| Daily operation | Background lighting with occupied-zone uplift. | Sensor events, renewed hold time and gradual return. | Verify minimum scene and route continuity. |
| Dense training | Extended occupied scene over active zones. | Repeated detections keep the scene active. | Avoid premature dimming between groups. |
| Organized race | Stable event illumination through the approved route. | Authorized event schedule or local override. | Record selected zones, approval and return to normal. |
| Inspection or repair | Local working scene and approaching-route visibility. | Maintenance authorization and work-order reference. | Record operator, affected assets and closure. |
| Weather scene | Approved brightness and CCT for the weather condition. | Weather input or authorized manual selection. | Measure visibility, glare and scene recovery. |
| Communication interruption | Stored local schedule and approved sensing behavior. | External-network failure policy. | Demonstrate continuity and later record synchronization. |
The system connects sensing inputs, individual light controllers, cabinet or supply zones, CH-800 Gateway / Centralized Controller logic and the selected management platform. The owner receives a route map that relates a physical pole to its controller, circuit, gateway and operating scene.
Cloud access can support remote management where permitted. On-premises servers, Ethernet or fiber can support an owner-controlled management environment. The local field-control layer should retain the approved behavior when external connectivity is interrupted; loss of remote visibility should be distinguishable from loss of illumination.
| System Layer | Operating Role | Owner-Held Evidence |
|---|---|---|
| Sensor layer | Report approved movement or environmental inputs. | Coverage plan, mounting detail, settings and detection test record. |
| Optional radar-video unit | Provide supported target events / metadata and visual review at key access points through the specified integration. | Model and interface scope, time alignment, zone-event mapping, video-access roles and fallback test. |
| Status and broadcast layer | Provide approved four-color indications, recorded / live voice announcements, LED information and video guidance at selected locations. | Status dictionary, message and content library, priority map, zone linkage, operator roles and interruption behavior. |
| Lamp controller | Execute dimming, CCT scenes and selected local fallback. | Device identity, command feedback, scene limits and firmware reference. |
| Cabinet / supply zone | Organize power responsibility and local operating inputs. | Circuit map, isolation procedure, supply status and manual authority. |
| CH-800 Gateway | Coordinate route zones, stored rules and field records. | Zone map, configuration backup, event history and offline behavior. |
| Communication route | Carry field commands and status through the selected channels. | Coverage measurements, path records and measured recovery behavior. |
| Platform and owner files | Review alarms, energy, maintenance and configuration. | Account roles, exports, retention policy and handover package. |
Communication should be selected from the actual power layout and terrain. PLC can use suitable existing power conductors, while LoRA can provide a wireless route where the electrical network does not offer a reliable common communication path. A dual-channel design can provide an alternative route when one channel is degraded.
For selected STSYSTEMPLC hybrid configurations, 0.1 s channel takeover is a project performance target to demonstrate in the specified test conditions. Record direction of transfer, load, interference condition and end-to-end lighting behavior. A working communication backup also needs powered field devices; a backup data path does not restore power to an unpowered luminaire.
| Review Item | PLC | LoRA | HYBRID PLC & LoRA |
|---|---|---|---|
| Existing lighting conductors | Useful where feeder topology and noise permit reliable PLC. | Independent of a common conductor communication path. | Use each channel according to measured site quality. |
| Mixed or irregular supplies | Different transformers and feeder boundaries can complicate communication. | Useful where pole power originates from different circuits. | Survey feeder boundaries and provide wireless coverage where required. |
| Terrain and wireless shadowing | Does not depend on direct wireless visibility, but depends on conductors. | Coverage may need gateway placement or additional route planning. | Validate bends, cuttings and gateway overlap on both channels. |
| Cable interruption or strong electrical noise | Affected conductor route may become unavailable. | Alternative data path can continue where devices remain powered. | Demonstrate PLC-to-LoRA transfer under the agreed fault condition. |
| Wireless interference or lost coverage | A healthy conductor route can remain available. | Affected wireless route may become unavailable. | Demonstrate LoRA-to-PLC transfer under the agreed condition. |
| Single-route dependency | One principal field path. | One principal field path. | Alternative field paths with documented priority and recovery logic. |
| Commissioning scope | Measure conductor quality, feeder limits and device density. | Measure RF coverage, noise, terrain effects and local regulatory settings. | Test both routes separately, then fault transfer and recovery together. |
Long desert or remote tracks can face substantial civil works for a separate power route: trenching, cable protection, distribution equipment, route reinstatement and maintenance access. A grid-only proposal should show these installation costs explicitly rather than compare only luminaire purchase prices.
Hybrid solar-grid lighting can be considered where an accessible grid connection is available but supply continuity or energy cost is a concern. Where no grid exists, pure solar is a different design case. Compare battery reserve, solar exposure, temperature, dust, shading, event hours and inspection access for each segment before selecting the power model.
| Power Route | Cost or Operating Consideration | Evidence to Request |
|---|---|---|
| Separate grid cabling | Trenching, conduit, feeder equipment and reinstatement. | Route drawings, measured lengths, civil-work rates and supply responsibility. |
| Hybrid solar-grid | Solar contribution with agreed grid charging or backup behavior. | Available grid connection, battery reserve, charging policy and outage tests. |
| Pure solar | Useful where a grid connection is absent or costly to establish. | Seasonal solar model, autonomy target, cleaning access and battery replacement plan. |
| Mixed corridor | Different segments may justify different power arrangements. | Zone-based bill of quantities and consistent sensing / operator behavior across segments. |
| Control-power reserve | Communication and monitoring also consume energy. | Separate night-lighting energy from standby and daytime controller consumption. |
A long bicycle track can involve several contractors: civil works, poles, supply circuits, luminaires, communications, software and event operations. Define the interfaces early so a fault does not become an unresolved dispute between the lamp supplier, sensor supplier and network team.
STSYSTEMPLC can organize these responsibilities around the field-control chain and the owner’s operating scenes. The proposal should identify what is supplied, what is integrated, who tests each boundary and which records the owner receives. This makes the comparison concrete before the project is awarded.
| Owner Problem | Likely Coordination Gap | STSYSTEMPLC Project Response |
|---|---|---|
| Sensor detects, but next bend remains dim | Detection and neighboring-zone rules were specified separately. | Map each input to the current and advance zones, then demonstrate real traversal. |
| Track is occupied, but lights dim too early | Hold time or repeated-trigger behavior does not suit dense groups. | Test sustained groups and keep the occupied scene until the agreed clear period. |
| Remote screen shows offline | The operator cannot tell whether lamps are dark or only disconnected. | Separate supply faults, field communication faults and external-network status. |
| Different feeder supplies along the corridor | Communication design assumes one uniform electrical network. | Survey actual feeders and select PLC, LoRA or hybrid paths zone by zone. |
| Energy-saving statement cannot be checked | Baseline or measurement scope was not agreed. | Provide measured scene power, operating history and owner-accessible reports. |
| New maintenance contractor lacks files | Configuration remains with the original team. | Deliver asset maps, backups, interface notes and acceptance records. |
External network failure should not make an occupied track wait for a cloud command. Store the approved scene and schedule behavior in the selected local controllers and CH-800 Gateway configuration. Define how sensing, manual override and abnormal-condition scenes operate during an interruption.
The exact fallback depends on which part fails. Loss of the internet, loss of the gateway, loss of one field channel and loss of luminaire power are different events. Test them separately and record the visible lighting behavior, retained events and return-to-normal sequence.
| Interruption | Expected Local Behavior | Record and Recovery |
|---|---|---|
| Internet or cloud unavailable | Approved local schedule and field scenes continue within the configured architecture. | Remote visibility is unavailable; retain local records where supported. |
| One field communication channel unavailable | Use the tested alternative route where the hybrid configuration and power allow. | Record channel status, transfer result and failed devices. |
| Sensor uncertain or unavailable | Apply the approved default scene rather than an untested reduction. | Flag the sensor or zone for inspection and preserve a usable route scene. |
| Gateway unavailable | Lamp-level behavior follows the configured fallback capability. | Document the scene retained at each controller and the restoration procedure. |
| Grid supply interrupted | Only the agreed backed-up circuits or solar / battery units continue. | Measure reserve and restored status; do not treat communication redundancy as energy backup. |
AI-Driven review can help operators examine repeated faults, unusual energy patterns, zones with frequent nuisance triggers and maintenance trends. The useful input is a consistent field record, not an attractive dashboard alone. Each event should be associated with the correct sensor, pole, controller and zone.
AI analysis should support operating decisions while approved local lighting rules remain available independently. The owner should know which data is analyzed, how recommendations are reviewed and who can authorize configuration changes. Anonymous zone activity can support occupancy analysis without implying personal rider tracking.
Detection counts with weather and zone context.
Recommend a site inspection or settings review; preserve legitimate low-speed detection.
Scene history, input power and event schedules.
Check sustained occupancy, configuration changes or an electrical fault.
Alarm source, repair history and replacement records.
Identify patterns for maintenance planning and root-cause review.
Aggregated zone activity at the agreed reporting level.
Adjust future scheduling only after lighting and operator review.
Approved files compared with the active version.
Flag unapproved changes and support documented restoration.
Factory Acceptance Testing should prove configuration and integration before delivery. Site Acceptance Testing should prove the real route with its bends, slopes, vegetation, electrical supplies and permitted traffic. Both stages should produce records the owner can inspect and retain.
Agree test routes and pass criteria before installation. Include the slowest approved user, both directions, side entrances, continuous groups and service vehicles. Repeat representative tests with normal scenes, event scenes and the agreed interruption cases. A short straight-line demonstration is insufficient for a varied cycling corridor.
| Acceptance Item | FAT Before Delivery | SAT on the Track | Owner-Held File |
|---|---|---|---|
| Asset identity | Map sensor, pole, controller, cabinet and gateway identifiers. | Check random physical assets against route and platform records. | Asset list, route map and zone table. |
| Target coverage | Define supported targets and sensing settings. | Test pedestrians, bicycles, motorcycles and four-wheel vehicles. | Target-pass records and installed settings. |
| Bend and gradient | Prepare zone overlap and advance-lighting rules. | Traverse both directions at approved speeds and difficult approaches. | Route test, scene sequence and response timing. |
| Dense groups | Verify repeated-trigger and hold-timer logic. | Test sustained groups and simultaneous zone occupancy. | Detection history and no-premature-dimming result. |
| Radar-video linkage, where supplied | Confirm supported targets, analytics events, metadata interface and lighting-zone mapping. | Test entrance / junction activity, video and event alignment, scene commands, dimming limits and lost-input fallback. | Integration scope, event / command log, visual reference and recovery record. |
| Indicators and broadcast | Approve color meanings, messages, visual content, event priorities and zone mappings. | Test each indicator, recorded / live voice path, display content, lighting linkage, manual override and communication interruption. | Status matrix, message library, content approval, audibility / readability checks and event record. |
| Nuisance filtering | Prepare sensitivity, coverage and available filter settings. | Compare occupied and unoccupied periods with relevant nuisance sources. | Missed / unwanted trigger records and adjustments. |
| Photometric scenes | Validate luminaire configuration and approved scene limits. | Measure relevant light levels, uniformity and glare evaluation. | Photometric files and site measurement report. |
| PLC / LoRA routes | Verify both channels and fault-transfer logic where supplied. | Interrupt each channel and measure behavior under agreed conditions. | Route quality, transfer timing and recovery record. |
| Outside-network loss | Load local schedules, scenes and fallback rules. | Disconnect the external link and observe field operation. | Offline result, retained logs and restoration record. |
| Weather / dual CCT | Check selected 2700K ↔ 6000K rules and manual override. | Verify trigger, scene, recovery and measured output. | CCT scene file and weather-input test. |
| Power reserve | Agree backed-up scope and consumption assumptions. | Test selected outage and charging / reserve behavior. | Power test and reserve calculation. |
| Alarm closure | Prepare alarm dictionary and work-order fields. | Simulate a fault through dispatch, repair and closure. | Alarm log and maintenance closure report. |
| Owner handover | Prepare accounts, exports, backups and spare-part plan. | Confirm owner access and a practical restore demonstration. | Handover index, configuration backup and restoration result. |
A long track benefits from fault location at the physical asset level. The maintenance team should know whether the issue belongs to a sensor, luminaire, controller, power circuit, gateway or communication route. A generic offline icon leaves too much work for field inspection.
Close each job with the repair action, replaced part, configuration change and restored operating status. Keep the history accessible to the owner so a new contractor can understand recurring faults without rebuilding the project from memory.
Route segment, pole ID and affected device.
Asset map and fault source.
Fault type, current scene and route impact.
Alarm timestamp, severity and operator assessment.
Assigned team, access window and work scope.
Work-order reference and maintenance responsibility.
Part replacement, wiring action or configuration correction.
Part identity, settings version and service record.
Lighting and sensing return to the approved behavior.
Functional retest and status feedback.
Owner can review the completed action and future follow-up.
Closure time, confirmation and recurring-fault history.
Interconnected PLC and LoRA route communication requires disciplined claim control. Separate completed project facts, verified product capability, route-specific design proposals and assumptions that remain open. This protects the owner from treating a reference video, maximum rating or simulated result as proof of the complete installed outcome.
| Evidence Grade | Meaning | Required Wording |
|---|---|---|
| A — Project verified | Identifiable delivered scope supported by acceptance or owner records. | State the project, scope and verified result. |
| B — Product verified | Selected product capability supported by a current datasheet, certificate or controlled test. | State model, configuration and limits. |
| C — Design proposal | Route-specific calculation and control narrative awaiting site acceptance. | Use “proposed” or “subject to SAT”. |
| D — Validation required | An assumption materially affects cost, safety or performance. | Name the owner, due date and validation method. |
BANYIN Freeway: project reference for sensor-related coordinated field lighting. Transfer the engineering method and request the applicable scope; bicycle-lane targets, route scenes, response timing and operating outcomes remain subject to this project’s FAT/SAT.
Apply the same discipline to every major statement. Sensor configuration is not route permission; communication redundancy is not backup power; maximum efficacy is not maintained track performance; AI-assisted review is not personal rider tracking. Every conclusion must point to evidence the owner can retain after handover.
| Owner Question | Practical Answer |
|---|---|
| Can the system detect bicycles and service vehicles? | The sensing proposal includes pedestrians, bicycles, motorcycles and four-wheel service vehicles. Performance must be verified with those actual targets in the installed geometry. Movement detection alone should not be described as certified target classification. |
| Should the track be designed for 100 km/h vehicles? | No. The 1–100 km/h configurable sensing band is distinct from the track speed policy. This project context uses about 30–50 km/h for support or inspection vehicles, subject to owner rules and route conditions. |
| What happens when many bicycles pass continuously? | Detections refresh the occupied scene and hold time. Heavy training or race activity can use a stable event scene. Savings depend on actual occupancy and should be assessed separately from low-use nights. |
| Can the sensor ignore grass and small animals? | Available filtering, coverage and sensitivity settings can reduce unwanted events. Verify the result on site while retaining slow pedestrians and cyclists; document missed detections and nuisance events together. |
| Does smart lighting mean every lamp switches off when nobody is detected? | The approved background scene can remain active. Standby levels, transition rates and priority scenes should follow the track design and owner acceptance requirements. |
| Can lighting continue without the cloud? | The selected local controllers and CH-800 Gateway can retain agreed schedules and scenes. Test internet loss, gateway loss and field-channel loss separately because their fallback boundaries differ. |
| Is this a GPS race-tracking system? | The lighting system tracks asset status and zone events within its agreed scope. Individual participant location, race timing or identity tracking requires a separate system and explicitly defined interfaces. |
| Does 230 lm/W guarantee the best track lighting? | It is a complete-luminaire efficacy option that must be verified for the selected model. Compare optics, CCT, maintained illumination, uniformity and glare as well as input power. |
| Do PLC and LoRA provide backup power? | They provide data routes. Lighting during an outage needs an agreed power reserve or backed-up circuit. Field devices must remain powered for the communication backup to be useful. |
| Can the owner keep project data after changing maintenance teams? | Include owner access, exports, retention, route maps, configuration backups, interface notes and spare-part planning in the handover package and contract. |
Share the route length, bends and gradients, pole spacing, electricity access, user density, permitted service vehicles, weather exposure, communication conditions and owner acceptance requirements. STSYSTEMPLC can organize the architecture, zone plan and evidence package for technical review.
Discuss the ProjectOpen Video/PDF Download Hub
Adresse : F4,Bldg A, Hanzhong Industrial Park, No.67, North of Xinsha Ave, Xin Tang, Zeng Cheng, Guang Zhou, China
Tél : +86 20 8278 0427
E-mail : info@stsystemplc.com
E-mail : morrison426@163.com
