How to Troubleshoot Common DILAX Issues

How to Troubleshoot Common DILAX Issues

Symptom: DILAX ERR lights is blinking red.

Solution: This indicates an issue with the DILAX. The blinks are actually Morris Code and have a specific issue associated with them. Consult pages 66-68 in the DILAX Product Manual for details about each error.

Symptom: DILAX only counting passenger boards or only counting passenger de-boards.

Solution: Retest the unit by slowly performing at least 5 full ins and outs. If the counts are not coming up correctly, use a 1.5 mm Allen wrench to manually adjust the sensor. The instructions on how to properly adjust the sensor are on Page 3 on the DILAX Data Sheet.

Symptom: Passengers that should be counted as boards are being counted as deboards and vice versa.

Solution: The sensor count needs to be inverted. Log in to the DILAX following the information found in How to Log In To DILAX KB Article.

Navigate to Configuration > Doors.
Select the affected door from the dropdown (1 for front, 2 for back)
Change the “Invert Counting Direction” to the opposite of what it is now
Navigate to Configuration > Load/Save and click “Save Configuration to Device”
Retest the door count and ensure that the change solved the issue

Symptom: Rear Sensor not active, therefore not counting rear boards.

Solution: The Bus was most likely not properly configured to have a rear door. Log in to the DILAX following the information found in How to Log In To DILAX KB Article.

Navigate to Configuration > Doors
Click “New” button
Under Identifier type “Back Door”
Leave the Defaults for “Door Contact”
Tick “Sensor Bar” checkbox
Under First sensor SSL position put “3”
Change “Minimum Stay” to “200”
Change “Maximum Coverage to “1”
Under “Sensor” click “New” button
Navigate to Configuration > Load/Save and click “Save Configuration to Device”
Retest the rear door count and ensure that the change solved the issue

Symptom: DILAX showing no signs of power.

Solution: Tell Maintenance about the issue and have them test the power. If Maintenance states that the power is working correctly, you will have to record the serial number of the DILAX and what bus it’s on. Then reach out to Consalvo@dilax.ca at DILAX for warranty information and next steps.

Symptom: Neither of the two sensor LEDs are lighting up when an object is below them.

Solution: Have Maintenance ensure that the cabling is correct and connected.

Symptom: Davisweb continues to show no data from vehicle however PCU indicates a successful FTP test.

Solution: Complete data review on PCU’s local FTP Server to determine if Dilax hardware is in fact counting passengers but left un-transmitted to the MVTA FTP server.

Log into PCU – Use “How to Log In to the Dilax” KB article for specific details
Enable FTP Server – Navigate to configuration then communication tab
Select FTP Server Configuration
Select FTP Server Configuration checkbox
Add Username “root” and Password “admin”
Click Load/Save and select “Save Configuration to Device”
Use Filezilla FTP Client - https://filezilla-project.org/
Using the same login method in step 1, configure Filezilla to access the FTP server on the PCU
Determine if files exist on the FTP and the file dates (screenshot and save)
MVTA Staff – Review the FTP Server to determine last available files
In-Vehicle Transit IT – Remove local FTP Server configuration from PCU

Symptom: Select vehicles continue to show no data in daily reporting section in DavisWeb

Solution: Complete networking test on the PCU.

Make sure the physical network connections are in correct ports on the Cradle Point and Ethernet switch (consult documentation as needed)
If Step 1 doesn’t provide expected results - determine if the PCU can reach the FTP server successfully:
1. Log into PCU – Use “How to Log In to the Dilax” KB article for specific details
2. Navigate to configuration then communication tab
3. Confirm if the FTP Client Configuration is correct – See screenshot

if FTP Client Configuration is correct then select “Start FTP Transmission Now”
Record test results

If Step 2 doesn’t provide expected results - determine if the PCU can reach the internet successfully:
1. Mimic the PCU with laptop (port 2 on CP should be available with DHCP) to determine if device able to reach the default gateway via (192.168.23.1) and/or internet;
2. Record and report results