It could be that the device is damaged. I will summarize the unbricking operation here again but we may need to get the unit back here if the RS485 chip is damaged, possibly.
Once again:
You will need a copy of the firmware and the best place to find firmware is here on your hard disk. If you have been working with the firmware update in the past you probably have a copy of the firmware on your hard disk already. You can see this dialog when you navigate to T3000 → help → check for updates → update device firmware.
If you cannot find the firmware locally you can check around here on the website but this is not always the latest and greatest version:
https://temcocontrols.com/ftp/firmware/
Once you have located the firmware navigate to T3000 → tools → update firmware for a single device. This brings up our ‘ISPTool’ . Here you set up the IP address of the device if you are connected over Ethernet or the Modbus ID if you are connected over RS485. If the device is operating under bacnet that’s OK, the firmware update in the first few seconds after bootup is in Modbus. If you don’t know the ID then you can put 255 here
It is best to do all this with only one device connected in all cases, Ethernet or Modbus.
Cycle power to the device and it will blink the LCD backlight if it has a display, or if there is one, the heartbeat LED. One of these will blink with two short blips repeating every second or so. If you don’t get these two short blips during power up that could mean the device is damaged. Either way you can hit the flash button and give it a try to flash the firmware.
If you cannot revive a device using this tool and this cycle the power & flash method then we will need to get the device sent back here for a checkup.