|
|
Post by Gareth on Jul 19, 2013 5:09:52 GMT
I have been unable to produce a working motor or function decoder. I realise that the fault must lay at my end as other people get them to work ok.
My DCC system is a DIY (POWS) system which works 100% with commercial decoders, it is only the DIY's that are a problem and not just Pauls decoders.
Do the Motor/Function decoders produce the ack signal as I can't seem the read it when I'm trying to program the decoder?
Gareth
|
|
|
|
Post by Paul Harman on Jul 22, 2013 11:23:59 GMT
Gareth
The ack pulse is only required if you want to read the contents of the decoder CVs so you should be able to get the decoder to function OK without getting an ack pulse.
The motor decoder does generate an ack pulse as long as a load is connected to the motor terminals that will draw more than 60mA. Similarly the function and accessory decoders will ack when suitable loads are attached, but you might need to load up more than one output to get 60mA.
I have measured the timing of the ack pulse on a scope and it looks to be OK, and the SPROG and Lenz LZV100 are happy with it. If your system is a bit more fussy about the length of the ack pulse it is quite easy to adjust it in the source code if you want to play with it, it is set near the beginning.
Newer commercial decoders are being introduced now with integrated ack loads so that there is no need to attach any load to read them.
Not getting an ack while programming might give you an error message, but programming should still proceed OK unless you are using page mode when programming might halt before the CV is changed if there is no ack following the page register write.
|
|
