I do have the Hino Bowie software and the nexis Usb link. That is what I used to read the code. The P141A code was there twice. One was active and the other was inactive. I did try doing the manual regen and it kept on giving an error. I did do a regen last week which took about 15 minutes.
Let's concentrate on the 2011 right now. The 2010 looks like it'll get injectors under warranty. That'll solve a lot of it, especially if the ITV and exhaust brake are adjusted at the same time.
Connect Hino Bowie. This is gonna be hard, I haven't used Hino Bowie in over a year.
Connect to the ECU, read codes, system fix. Look at system protection data. What's the DPF outlet temp? Write it down, then reset it. While you are in there, go to the customization screen and find the line that says "PM amount of piling up". Change it to 2.5
Disconnect from the ECU and connect to the BCU. Remove the atomizer nozzle. go to activation test, turn on the ignition coil. You should have spark across the ignitors. Watch it for three minutes. Turn off coil. Reinstall atomizer nozzle. Unplug the flame temp sensor (this will stop it from firing the burner during the next step). Unscrew the large braided line from the CAV. Start the engine. Turn combustion air valve on and off around 30 times. It helps if you have a helper here. Air should blow out when it's on and nothing when its off. If that's ok, shut the engine off, reconnect everything including flame temp sensor, turn key on.
While inside the BCU, go to data monitor. Monitor the following: Engine speed, engine torque, exhaust gas temp burner inlet, flame temp, exhaust gas temp burner outlet, target exhaust gas burner outlet, atomizer air pressure, atomizer fuel pressure, atomizer nozzle pressure, burner operation state (I think. Some names changed). Start the engine. Start data monitor. Press the regen button (the DPR graph should be at three or 4). It will do some ignitor cleaning, prepare for regen, etc. When you see target and actual exhaust gas temp match, it's about to fire off. When it does, flame temp should immediately climb and quickly go over a thousand. It'll eventually taper off at around 1500-1700 degrees and then very slowly climb. In the meantime, atomizer air pressure will go from around 100-120 as the air compressor kicks on and off. Atomizer fuel pressure should be between 80-100. Nozzle pressure (important!) should be between 40-50. It generally hangs out around 48, but even if it spikes up to 52 on occasion, that's ok. 55 will set a code. These higher pressures indicate that the nozzle is clogged or the tiny braided line is damaged.
When it's done, save it as a .txt file, then email it to me. I'll graph it, if it translates correctly.
As long as there's nozzle pressure, spark, and air from the CAV, it'll burn. If it doesn't know it's getting hot, it'll register a lost flame event (which will be in the burner event log, but I don't remember how to do that Using the old DX program. DXII is superior in every way.) The flame temp should go up quickly, but if it lags or starts going down, id suspect the flame temp sensor if you've confirmed that everything else is ok.
What I've described covers 80% of the problems you'll encounter.
Oh, since you have the computer, go back into the ECU, into customization, and find the line that says something like "rental car flag". Change the value from 0 to 1. Now you can do a manual regen despite the number of bars on the DPR graph. This is handy for times when you know you'll be sitting and the truck will want to regen, but it's not ready yet.
For codes that just won't go away, there's a line in either activation test (ECU) or in ECU customization that says something like "Release repeat offense". Select it or hit go or whatever. This will allow you to reset a code that won't go away. I guess they do this to keep generic scan tools from wiping way certain codes. After you've released the repeated offense, you can clear the codes. The BCU will have codes in it too, and they are separate from the ECU codes. Same with the DCU and VCS. It takes forever jumping back and forth between the modules like this, and that was addressed with DXII. DXII is very similar to Isuzu's IDSS diagnostic software, which is very good.