Hi Can you send your PCB as EasyEDA Source json file:https://easyeda.com/Doc/Tutorial/Export.htm#Exporting-EasyEDA-Source to support@easyeda.com? The local auto router is not good enough, it can't finish all the PCB nets,sometimes you'd better route some tracks manually.

@Tutorials Hi, Thanks for your reply. I did as you suggested and routed some tracks manually: after the third track the router did the job and finished automatically. However, I still got a lot of messages 'Wiring: read_net_id: String expected'. Is this the normal behaviour or is there still something wrong? I did check the nets and didn't find any discrepancies in the names, no strange characters or spaces, only A-Z, a-z, 0-9 and _. If this is the message that everything is ok then maybe you should change the wording and replace 'expected' with 'found'. Thanks for your help sofar and looking forward to your answer. BR//Willem.

@mijnmodelbaan Hi Can you send us your PCB as easyeda source? we need to find the reason. thank you.

@Tutorials Hi, Just send you the json file. BR//Willem.

@mijnmodelbaan Hi,Your PCB route by the local auto router is working for me.

@Tutorials Hi, Yes, after applying your suggestion of adding some routes manually, it's working, except for those messages I still get about 'String expected'. I would like to know if this is 'normal' behaviour, an error, or miswording. Thanks, Willem.

@mijnmodelbaan If your PCB has finished, please ignore this error message, this is only for the local router and editor communication. thanks.

@Tutorials Ok, will do so. Thanks for the help. BR//Willem.

I'm having the same issue - no joy from Support to resolve. I completely redesigned the PCB layout so it's now optimal. Still, the auto-router sticks at 99% complete and will not finish. It shows the same error as reported above. There needs to be a Component name listed whenever error messages are generated if users are to be able to resolve this without involving Support! https://easyeda.com/editor#id=1a22ba6837c447cc8cd75a56749e51f8|ea3ac15e358a405f89e50404b518cbd9|bc1c051a76334cb4a4a8ba0c30bccefb -------------Connection established----------- Start routing... Routing Wiring:read_net_id: String expected Wiring:read_net_id: String expected Wiring:read_net_id: String expected Wiring:read_net_id: String expected Routing Routing Routing Routing Routing Routing Routing Routing Routing Routing Routing Routing Routing Has anyone figured out what causes this and how to resolve?? Thanks Rick

It's obviously stuck in an endless loop...

Haven't been able to figure out what's causing this error message: Wiring:read_net_id: String expected

@rbraddy Per talk in the email, you need to route some tracks manually, because of the auto router can't deal with the two same pads track connection at the same footprint now. thanks

Manually routing a few tracks worked for me, just try it.